Civil 3D corridors: assemblies, targets, surfaces and intersections, without fighting the model

At a minimum, a corridor needs:

• An alignment, which sets where the centerline runs.
• A design profile on that alignment, which sets its elevation. How to build it is in Civil 3D profiles and profile views.
• An assembly, which defines the section on each side of the centerline.

The alignment and profile make up the corridor's baseline. A single corridor can have several baselines: one per street, per ramp, or per edge of an intersection.

Each baseline is divided into regions: station ranges that use one assembly. If the section changes, say from a hillside cut to an urban stretch with curbs, you add another region with another assembly.

You build the assembly in plan, at any point in the drawing, by attaching subassemblies on each side of a baseline marker. Civil 3D ships a tool palette with dozens of ready-made subassemblies. The most used:

Cut and fill, each with its own slope: the conditional assembly. With ConditionalCutOrFill, the assembly can have one branch for cut, with a ditch and its slope, and another for fill, with a flatter slope. At each station, Civil 3D uses whichever branch matches where the ground is.

If the typical section isn't on the palette, you build it in Subassembly Composer, the program that ships with Civil 3D for designing your own subassemblies with a flowchart, no code required. You export a .pkt file and import it into Civil 3D. It's the route for special ditches, retaining walls or a Civil 3D duct bank.

Frequency. Civil 3D doesn't model the corridor continuously: it applies the typical section at stations, at a set spacing along tangents, curves and spirals, plus at the points where the alignment and profile geometry changes. Between one station and the next, it joins the points with straight lines. That's why:

• With low frequency on curves, edges look faceted and volumes are approximate.
• With very high frequency everywhere, the corridor takes longer to rebuild and the drawing gets heavier.

A common practice is to use more stations on curves than on tangents, and always include the geometry points.

Targets. A subassembly can follow something in the drawing instead of using a fixed value. You assign them in the corridor properties, in Target Mapping, and there are three kinds:

An example: a widening ahead of a bridge is modeled with an offset edge alignment. The lane follows that edge and the width changes on its own, with no extra region.

The corridor surface is the finished project. You create it in the corridor properties, on the Surfaces tab:

• Add link codes: Top for finished grade or Datum for subgrade, depending on what it's for.
• If needed, add feature lines as breaklines, so the triangulation respects edges and gutters.
• Define the boundary, so the triangulation doesn't bridge the gaps between ramps or cross outside the slopes.

The automatic boundary is added on the Boundaries tab, using the daylight feature line. It only works if daylight exists on both sides of the corridor along the whole range. If one side has no slope, say next to a retaining wall, draw the boundary as a polyline and add it instead.

With the corridor surface you compare volumes against existing ground, draw the project's contour lines and take the design into other programs, as in moving Civil 3D topography into Revit.

At an intersection, the crown, edges, curbs and curb returns all change at once. Civil 3D includes the Create Intersection wizard, which takes two alignments with their profiles and creates:

• The intersection object.
• The offset alignments for the edges and the curb-return alignments, with their profiles.
• The assemblies and corridor regions in the intersection area.

What the wizard doesn't decide is the design criteria: which road holds its crown, how the corner drains, what radius to use. That's still engineering. And every radius or profile change means reviewing the intersection again.

• The corridor is out of date. You changed the profile or a target and the corridor didn't change. Prospector flags it as out of date: rebuild it, or turn on Rebuild Automatic, which makes every change slow in large drawings.
• The side slope doesn't reach the ground. The surface target isn't assigned, the existing surface doesn't cover that area, or the slope has a maximum width that falls short.
• Holes or spikes in the surface. Regions that don't meet, too few stations on curves, or no boundary: the triangulation connects points it shouldn't.
• The corridor surface isn't showing. It was created without link codes, so it's empty; the boundary clips all of it; or its style displays nothing.
• The width doesn't change at the widening. The width target is assigned to a different subassembly, or the edge alignment doesn't cover the whole region.
• The section jumps between regions. Switching assemblies without a transition leaves steps. Model the transition with width and elevation targets.
• The sections don't show the corridor. The corridor isn't among the sample line sources. We explain it in Civil 3D cross sections.
• The corridor is very slow. Too many regions, too many stations everywhere, or a very dense surface as a target. Splitting the project into several corridors by segment helps.

Volumes come out of the corridor in two ways:

• From sections: sample lines, materials and a volume table, by the average end area method. Step by step in Civil 3D cross sections.
• From surfaces: comparing the corridor surface against existing ground in a volume surface.

What eats the most hours in a firm, and can be automated:

• Creating the corridors for a subdivision with many streets, with the same typical section and its regions.
• Assigning targets in bulk, without opening the dialog street by street.
• Exporting corridor points by code and station to Excel, for staking or quantities.
• Checking, before plan production, that every corridor is rebuilt, has a boundary and has no empty regions.

Since Civil 3D 2025.1, Dynamo includes nodes for working with corridors; we cover them in 10 Dynamo scripts for Civil 3D. For tools the whole firm uses, the Civil 3D API in C# gives full control.