Civil 3D section views: how to create them in bulk, keep them from stacking on top of each other and automate them with your standards

A section view draws what a sample line cuts: the ground, the corridor and its surfaces. So:

• No sample lines, no views. The sample line group comes first; we cover it in automated Civil 3D sample lines.
• Anything that isn't a source of the group won't show in the view.
• Delete a sample line and its section views are deleted too.
• If the corridor or the ground changes, the sections update, because they read the model.

Views are created one at a time (Create Section View) or all at once (Create Multiple Section Views), on the Home tab, Profile & Section Views panel.

What changes the result most is the height. With an automatic range, each view takes the height of what it cuts, and one odd section can produce huge views. With a fixed height that follows the ground, every view comes out the same size and centered on what matters.

In production, views are laid out from the sheet template and its viewport, at the chosen scale. If they don't fit, the problem is usually the template or the scale.

In draft, the group plot style lays them out, on its Array tab:

• Rows or columns: whether views fill across or upward, and from which corner.
• Cell size: uniform for all, sized to the largest view, or uniform per row or column, which packs them tighter.
• Spacing: the gap between columns and between rows.

After changing the style, update the group layout. Bands count too: a taller band makes every cell larger.

Labels. Views carry offset and elevation labels, slope labels and corridor edge labels. They're defined in the styles and can be changed for the whole group.

Cut and fill hatching. It isn't drawn by hand: it comes from Compute Materials, using quantity takeoff criteria. Each material has a shape style that the view shows with its hatch. If the colors come out swapped or cut shows zero, check the surface order in the criteria.

Tables per section. With materials computed, the wizard can add a table to each view with cut and fill areas and volumes.

Projected objects. You can project feature lines, survey figures, 3D polylines, COGO points and other objects into the views, across a whole group at once. It's how you show a wall, a ditch or a control point in every section.

When you add sample lines, their views don't join the existing group on their own: create the new views and use Move to Section View Group. The Update command doesn't re-sort them.

Section sheets are created on the Output tab with Create Section Sheets, as long as the views were created in production. If you add views later, the sheets aren't regenerated automatically.

The title block on each sheet comes from the template. Filling in its data on every sheet is a separate job: we cover it in title blocks filled automatically.

The wizard handles one group with one configuration. On real projects:

• Many alignments. A subdivision with 30 streets means running the same wizard 30 times, with the risk that one comes out with a different style or height.
• The full standard. Elevation range, bands, labels, hatching and tables, all per your firm's or the agency's configuration.
• After a change. New sample lines, views to move into the group and sheets to rebuild.
• Labels at specific points. Elevations at the centerline, the edges of pavement or the toe of slope, in every view.
• Sheet order. Numbering, the station range of each sheet in the title block, and the sheet index.

We build custom Civil 3D plugins. For section views, a typical plugin:

• Creates the views for every alignment in one pass, with one group per alignment.
• Applies your standard: elevation range, bands, labels, cut and fill hatching and tables per section.
• Adds the labels your agency asks for at the centerline, the edges and the toe of slope.
• Keeps the group in order when sample lines are added or removed.
• Builds the sheets with numbering and station ranges in the title block.
• Logs what it did in a report, so you can check it before plotting.

If you'd rather start without code, since Civil 3D 2025.1 Dynamo includes a node to create section views from a sample line. We cover it in 10 Dynamo scripts for Civil 3D.

How we work:

1. Diagnosis (1 week, free): we look at how you build sections today and write down the standard.
2. Prototype (1 to 2 weeks): we validate the logic on one of your projects.
3. Development (2 to 4 weeks): the C# plugin, tested on your own models.
4. Installation: an installer for the whole firm, a button on the Civil 3D top toolbar, a manual and documentation.
5. Support: updates with every new Civil 3D release.

The source code belongs to your company: the plugin is yours.