Understanding Nodes, Members and Coordinates in STAAD.Pro

Every STAAD.Pro result sits on geometry. Nodes (joints) have coordinates. Members connect two joints. If those joints are 10 mm apart when they should be coincident, the member is a stub, the mesh is dirty, and CAD export will look like a cracked drawing. Geometry is not a preamble to engineering. It is engineering.

Coordinates only mean something with units and a global axis. A model that “looks” like a portal frame in the renderer can still have Z as the plan axis, or millimetres typed into an inch file. Those errors survive into AutoCAD conversion and into support reactions that civil will use. Catch them at the node table.

This article is about reading and checking the geometric skeleton: joints, incidences, duplicate nodes, member splits, offsets and the mapping to grids. Property assignment is a sister topic in member properties. Checking the whole file is in the model checking checklist.

Nodes are the only places the structure exists

STAAD does not store a “column” as an architectural object. It stores joints and a member between them. If you need a splice, you need a joint (or you accept that the member is continuous in analysis). If you need a support, you need a joint at the base, not a nearby joint that looks close in a zoomed-out view. Precision is a setting and a habit.

Duplicate joints are the classic disease. Copy-paste, CAD import, and GUI snaps create two nodes where one should be. Members then fail to connect, stability warnings appear, or a support sits on the unused twin. Merge coincident nodes on purpose, after checking that they really are the same point in the intended structure.

Members are incidences plus behaviour, not just lines

A member’s identity is its start and end joint. Reverse the incidence and you reverse some local-axis conventions. Split a column at every girt and you have many members where drawings show one piece — which is fine if you meant to, and a property nightmare if you did not. Releases, truss specs and beta angles live on the member and will not show as a kink in the renderer.

Start and end

Be consistent: columns bottom to top, rafters left to right or eave to ridge. Consistency makes local-axis checks and connection orientation easier.

Beta angle and local axes

A channel or a rafter with a sloped top flange can be locally rotated. Wrong beta is a property error that looks like a geometry error in results. Confirm on a sample member before you clone.

Units, global axes and the architectural grid

Decide units before the first joint. Mixing millimetres of architecture with metres in STAAD is a silent disaster. Decide which global axis is vertical and keep it for the job. Then map architectural grids to coordinates with a written origin. “Grid A is X = 0” belongs in the file notes and on the drawing that will later be produced via Staad2CAD or by hand.

Common geometry errors that survive a pretty 3D view

The renderer is a poor inspector. It will hide a 2 mm gap. It will not tell you a brace is a truss member. It will not tell you an offset moved the load path. Use tables: joint coordinates, member incidences, duplicate-node reports, and a walk of supports.

• Duplicate nodes at bases so the support is on the unloaded twin.
• Members sharing a view but not a joint — the “almost connected” portal.
• Zero-length members from snapping a joint to itself.
• Unintended slope from a 5 mm coordinate typo on a long purlin line.
• Imported CAD arcs faceted into dozens of members nobody will design.
• Offsets used to model haunches without documenting them on drawings.
• Two grids of nodes: architectural and “analysis” that drifted.

How coordinates become CAD — and why identity must travel

When you convert to AutoCAD, you are exporting this skeleton. If joints do not match the architectural grid, the drawing will fight every xref. If member numbers are the only identity, the CAD team will invent marks. Create a mark map while the node table is still clean. The conversion guide assumes this work is already done.

For PEB tapers, coordinates of eave, ridge and taper change-points should match the portal frame elevations you intend to issue. A STAAD prismatic stand-in with different joint locations is not a check model; it is a different frame.

Building a clean STAAD geometry skeleton

Do this before properties and loads; dirty geometry contaminates both.

1. Set units and vertical axis; write them down.
2. Set origin versus architectural grids.
3. Create primary joints: bases, eaves, ridges, brace work-points.
4. Create members with a consistent incidence convention.
5. Run duplicate-node and orphan-node reports; fix with inspection.
6. Add supports only on the intended base joints.
7. Spot-measure overall width, height and a bay against the input register.
8. Only then assign properties, releases and loads.

Engineering tips

• Name or group joints at grids so a coordinate dump is readable.
• If you import DXF, treat it as a trace, not as finished incidences.
• Keep a printed joint table for the first bay; it is faster than orbiting.
• When a member should be continuous, do not split it “for CAD” unless you have a rule for properties at the split.
• Beta-angle mistakes cluster on sloping rafters — check those first.
• If Staad2CAD shows a zigzag column, look for stacked joints before you blame the converter.

Geometry mistakes that analysis will not shout about

Using GUI copy on a bay and creating a 1 mm grid creep

After ten bays the building is 10 mm long and every purlin is skewed. Copy with exact coordinates or a spreadsheet of joints.

Supporting both coincident nodes “to be safe”

You just split the reaction and created a mysterious double column for civil.

Modelling a haunch only as an offset with no drawing note

Results include an eccentricity nobody will fabricate. Either model the haunch geometry or document the idealisation.

Letting plate meshing create nodes that break beam incidences

A floor plate can split columns unintentionally. Control mesh connectivity or use coincident constraints on purpose.

STAAD geometry checklist

Run before the first load case is taken seriously.

• Units match the project.
• Vertical axis is as intended; gravity sign makes sense.
• Origin mapped to architectural grids.
• No unexpected duplicate joints at supports.
• No orphan joints.
• No zero-length members.
• Member incidences follow a stated convention.
• Overall dimensions match the freeze.
• Brace work-points exist at the intended intersections.
• Offsets and releases are listed, not only visible as “a line.”
• Mark map from members to drawings is possible (numbering is stable).

Frequently asked questions

What is the difference between a node and a support in STAAD.Pro?

A node is a point in space. A support is a restraint applied to a node. You can have many nodes with no supports. You cannot have a support without a node. Putting the support on a duplicate node next to the column is a common miss.

Should every drawing grid intersection be a STAAD node?

Only if a member or support needs it. Extra nodes without members are clutter. Missing nodes at work-points are errors. Use the structural work-points, then map them to architectural grids in documentation.

Why did two members not connect even though they touch on screen?

They do not share a joint. Zoom is not connectivity. Check incidences and coordinates, then merge if they were meant to be the same point.

Can I build STAAD geometry from AutoCAD instead of the other way around?

Some teams import CAD lines. It often brings duplicate vertices and architectural clutter. If you do it, clean in CAD first, import as a trace, and still run the geometry checklist. Going STAAD to CAD after a clean model is usually safer for analysis-driven jobs.

If the joints are wrong, nothing downstream is right

STAAD.Pro results, reactions and CAD exports all inherit the node table. Units, axes, coincident joints and member incidences are therefore not setup trivia. They are the structure. Clean them before you discuss utilisation ratios.

Continue with member properties and model checking. Geometry advice in this article is educational. Command names and default axes can vary by software version; confirm in the current documentation and with the project’s reviewer.