Corridors

A road body — an assembly swept along an alignment and profile, sampled into cross-sections, then turned into a 3D solid, surfaces and feature lines.

How a corridor is built

A corridor combines a horizontal alignment (path), a vertical profile (elevation), and an assembly (cross-section). At each sampled station it:

1. finds the centreline point, bearing and elevation,
2. bakes the assembly there — applying superelevation and widening for that station,
3. places each section point at centreline + offset × right-perpendicular, lifted to the profile elevation.

Stitching consecutive stations together produces the 3D ribbon, the corridor surface and the feature lines.

Plan display

Every corridor draws its footprint in the Plan tab: a filled pavement strip between the section's outer pavement edges, plus — when zoomed in — the feature lines of every assembly point code, coloured by family (lane edges blue-grey, kerbs yellow, daylight green, sidewalks warm grey, medians orange). Regions bound to a project assembly resolve exactly as in 3D, so what the assembly defines is what plan shows. Corridors are hoverable/selectable in plan like alignments.

Regions

A corridor is divided into regions along its length. Each region binds its own assembly — and optionally its own horizontal/vertical baseline — so the section can change along the road (a normal section, then a bridge approach, then an intersection). Where two regions meet, a transition (blend) length tapers their shared edges (matched by point name) smoothly instead of stepping. Set the blend with the Transition (m) field; 0 = a hard switch.

Corridor Properties dialog

Right-click a corridor in the Object Browser → Properties…. Five tabs:

Information

Read-only: name, region count, baseline length.

Parameters

Multi-baseline (Civil-3D Baseline 1..N). One corridor can carry several reference alignments — the primary road, a crossing road, and the curb returns of an intersection all in one object. Add Baseline… picks a reference alignment (+ an assembly) and appends it; Remove Baseline drops the last extra (the primary always stays). The Baseline drop-down chooses which baseline the region table below edits — each baseline has its own regions, assemblies, frequencies and width targets. All baselines rebuild + render as one corridor, and the whole set saves and undoes together.

A baseline → region tree. The top row has Add Region / Remove Region, the Transition (m) field, a Target surface drop-down (the ground the daylight subassemblies tie to), and the corridor's width / elevation reference: Target alignment (the alignment a section measures its offset to) and Target profile (the profile it ties its elevation to — e.g. a curb return reaching the primary centreline and its design profile). Each region row (“RG - n”) has:

Codes

A read-only listing of every point, link and shape code the corridor produces, each with its style colour swatch and a count. Use it to see which codes the Surfaces tab can build from.

Surfaces

A checkable list of codes. Tick the codes that should contribute data to the corridor surface (none ticked = every feature line). Press Apply & Build Corridor Surface to create/refresh the TIN. See Surfaces & volumes.

Boundaries

Use corridor extents as outer boundary clips the corridor surface to the leftmost and rightmost section edges along the baseline, so the triangulation doesn't fan past the road edges.

Pipe Targets

Subassemblies that dig to a pipe — Trench Pipe 2 and Trench Pipe 3 in the stock library — declare a pipe target instead of a fixed trench depth. This tab lists every pipe target the corridor's assemblies declare and binds each one to a real network from the Utilities module.

Pick the Network, then either a single Pipe or <whole network>. With the whole network bound, each station digs to whichever pipe crosses the section closest to the centreline. The trench floor follows the pipe's real invert, so it rises and falls with the pipe rather than with the road. Where no pipe crosses — before the run starts, after it ends, or with nothing bound — the subassembly falls back to its no-pipe branch and digs nothing.

The tab is empty when no subassembly in the corridor targets a pipe.

Parameter transitions

The Transitions tab of Corridor Properties overrides a named assembly parameter across a station band — for example narrowing LaneWidth from 3.50 to 3.00 m between two stations — without authoring a target alignment or a custom subassembly. The value interpolates linearly across the band (tick Smooth for an eased ramp); a record acts only inside its band, so add a second record with equal values to hold the new width beyond it. Later rows win where records overlap. Anything the assembly derives from the parameter (variables, expressions) follows the transitioned value automatically, in both classic and flowchart assemblies. Tables can be exchanged as CSV (param,station_from,station_to,value_from,value_to,smooth).

Sampling frequency

Cross-sections are taken at a frequency (interval). Curves and spirals need closer sampling than tangents to stay smooth, so each gets its own value on the Parameters tab. Add manual stations at specific points (a culvert, a driveway) to force a section exactly there. A frequency of 0 falls back to the region default.

Outputs

• 3D ribbon in the 3D tab — link strips, shape solids, point feature lines, coloured by code.
• Corridor surface for display and volumes.
• Feature lines extractable back into alignments (Deriving alignments).
• Sections at any station (Sections).

Rail corridors & cant

A corridor whose baseline is a Rail-category alignment banks its rails automatically: the applied cant is the equilibrium cant G·V²/(127·R) capped at the design standard’s maximum, signed by curve direction and ramping naturally through spirals. The section’s Cant.* expression identifiers (used by imported Civil 3D rail subassemblies and the built-in rail parts) then track the alignment station by station — the outer rail rises through every curve in the 3D view with no manual setup. The standard and design speed come from the project settings (Design standards).