Civil 3D ACP cheat sheet

Objects (points, surfaces, alignments, profiles, corridors, pipe networks) live in a drawing but are exposed to all drawings through a project database; the Prospector tree reads that database, not the current viewport.

A Civil 3D object is defined by its style plus its properties; changing a style changes display only, while changing properties (elevations, geometry, name) changes the underlying data.

Drawing Settings control ambient behavior: units, zone, scale, and the abbreviation and object layers assigned to each object type; object layers are set per object type per drawing.

A description key set maps raw field codes to full descriptions, point styles, point label styles, and layers; key matching runs on the raw description before the point is created.

Figure prefix databases assign linework (breaklines, lot lines) to layers and mark them as breaklines at import time; a figure prefix must exist before the field file is imported.

Data shortcuts (shortcuts folder in the project) reference surfaces, alignments, profiles, pipe networks, and view frame groups without duplicating geometry between drawings.

Reference objects are read-only in the consuming drawing; editing happens in the source drawing and the change propagates on synchronize.

Assemble a working folder with a single project structure (source, sheets, exports, shortcuts) so relative paths survive moving or archiving the project.

A surface is a TIN built from point, breakline, boundary, and contour data; editing the definition list changes the surface, while surface properties alone do not.

Breaklines come in three types: standard (adds triangle edges), proximity (adds edges within a distance), and wall (adds a vertical face between two breaklines).

Boundaries clip a surface: outer boundaries remove data outside, show boundaries remove display, hide boundaries remove display inside, and data clip boundaries exclude data from the build.

Surface volumes use the composite volume method by default; the TIN volume surface is a separate surface object whose elevation at any point is the elevation difference between two surfaces.

Point groups are dynamic queries (by description, elevation, name, or inclusion) so points added later that match the query join the group automatically.

An alignment-based grading or feature line uses elevations and slopes; grading criteria (distance and slope or elevation) drive the daylight line that ties to the target surface.

Feature lines carry elevation and can be assigned to a site; feature lines in the same site interact and create crossings, so site membership must be deliberate.

Surface analysis types include elevation, slope, contour, watershed, and directions; slope arrows and watersheds read the TIN triangles, so a coarse TIN yields coarse results.

An alignment is a horizontal control object: fixed, floating, and free sub-entities differ in how many constraints they hold and which neighbors they depend on.

A profile view is a graph of a profile; a surface profile is sampled from a surface, a layout profile is drawn from tangents and curves, and a superimposed profile shows another alignment's profile.

Vertical curves are defined by K value, length, or curve pass-through; K = L / A where L is length and A is the algebraic difference in grades, so L = K x A.

Design criteria files check alignment and profile geometry (minimum radius, maximum grade, K values) and flag violations; the criteria file must be assigned in the object's design criteria settings.

Station equations shift stationing along an alignment (for example 10+00 back = 9+50 ahead); they do not change the geometry.

Profile view styles and label styles are separate; band sets control the data shown under the profile view, and vertical exaggeration is set in the profile view style.

Superelevation is computed from a superelevation axis of rotation and a design criteria file, then applied to the alignment and consumed by corridors.

Offset alignments and widening parameters are created from a parent alignment and stay dynamically linked to it.

A corridor is built from a baseline (alignment plus profile), a horizontal region with a station range, and an assembly of subassemblies applied along that region.

Assemblies define the cross-section shape; subassemblies carry the parameters and targets (surface, alignment, profile, offset, elevation) that resolve at each station.

Targets must be set per region, not per corridor; a region with unresolved targets produces default (often flat) geometry at those stations.

Corridor surfaces are created from links and feature lines in the corridor properties; the corridor surface is dynamic to the corridor and must be added to the surface list explicitly.

Sample lines cut sections through a corridor or surface at a station interval and at additional stations; section views display those sections with a group plot style.

A corridor's daylight subassembly needs a target surface; if the target is missing the daylight cannot compute and the corridor reports an error at those stations.

Material lists and quantity takeoff read corridor shapes and surfaces; pay items and the QTO manager compute quantities from those shapes.

Corridor rebuild order matters: change the alignment, profile, or assembly, then rebuild the corridor before extracting or reporting surfaces.

A pipe network is a set of pipes and structures; pipes connect to structures, and the network has one parts list that defines available sizes, materials, and rules.

Part rules (minimum and maximum cover, slope, drop across structure) are applied when parts are created or when rules are applied; they do not re-run automatically after later edits.

A pipe's flow is defined by its start and end structure invert elevations and its slope; changing the slope moves the downstream invert unless the invert is locked.

Interference checks compare pipe networks against other networks or 3D solids and report clashes with a clearance value.

QTO (quantity takeoff) computes volumes and areas from material lists and pay item lists; the results are a snapshot unless the report is regenerated after edits.

Sectional quantities come from sample line material lists; average end area volume = L x (A1 + A2) / 2, where L is the distance between sections.

Data shortcuts must be validated and repaired when source drawings move; a broken shortcut shows as a reference with a missing source path.

Audit and recover the drawing, and purge unused styles and objects, before archiving or handing off a project to keep the file size and dependencies controlled.

A Civil 3D object is defined by its style plus its properties; changing a style changes display only, while changing properties (elevations, geometry, name) changes the underlying data.

Drawing Settings control ambient behavior: units, zone, scale, and the abbreviation and object layers assigned to each object type; object layers are set per object type per drawing.

A description key set maps raw field codes to full descriptions, point styles, point label styles, and layers; key matching runs on the raw description before the point is created.

Figure prefix databases assign linework (breaklines, lot lines) to layers and mark them as breaklines at import time; a figure prefix must exist before the field file is imported.

Data shortcuts (shortcuts folder in the project) reference surfaces, alignments, profiles, pipe networks, and view frame groups without duplicating geometry between drawings.

Reference objects are read-only in the consuming drawing; editing happens in the source drawing and the change propagates on synchronize.

Assemble a working folder with a single project structure (source, sheets, exports, shortcuts) so relative paths survive moving or archiving the project.

A surface is a TIN built from point, breakline, boundary, and contour data; editing the definition list changes the surface, while surface properties alone do not.

Breaklines come in three types: standard (adds triangle edges), proximity (adds edges within a distance), and wall (adds a vertical face between two breaklines).

Boundaries clip a surface: outer boundaries remove data outside, show boundaries remove display, hide boundaries remove display inside, and data clip boundaries exclude data from the build.

Surface volumes use the composite volume method by default; the TIN volume surface is a separate surface object whose elevation at any point is the elevation difference between two surfaces.

Point groups are dynamic queries (by description, elevation, name, or inclusion) so points added later that match the query join the group automatically.

An alignment-based grading or feature line uses elevations and slopes; grading criteria (distance and slope or elevation) drive the daylight line that ties to the target surface.

Feature lines carry elevation and can be assigned to a site; feature lines in the same site interact and create crossings, so site membership must be deliberate.

Surface analysis types include elevation, slope, contour, watershed, and directions; slope arrows and watersheds read the TIN triangles, so a coarse TIN yields coarse results.

An alignment is a horizontal control object: fixed, floating, and free sub-entities differ in how many constraints they hold and which neighbors they depend on.

A profile view is a graph of a profile; a surface profile is sampled from a surface, a layout profile is drawn from tangents and curves, and a superimposed profile shows another alignment's profile.

Vertical curves are defined by K value, length, or curve pass-through; K = L / A where L is length and A is the algebraic difference in grades, so L = K x A.

Design criteria files check alignment and profile geometry (minimum radius, maximum grade, K values) and flag violations; the criteria file must be assigned in the object's design criteria settings.

Station equations shift stationing along an alignment (for example 10+00 back = 9+50 ahead); they do not change the geometry.

Profile view styles and label styles are separate; band sets control the data shown under the profile view, and vertical exaggeration is set in the profile view style.

Superelevation is computed from a superelevation axis of rotation and a design criteria file, then applied to the alignment and consumed by corridors.

Offset alignments and widening parameters are created from a parent alignment and stay dynamically linked to it.

A corridor is built from a baseline (alignment plus profile), a horizontal region with a station range, and an assembly of subassemblies applied along that region.

Assemblies define the cross-section shape; subassemblies carry the parameters and targets (surface, alignment, profile, offset, elevation) that resolve at each station.

Targets must be set per region, not per corridor; a region with unresolved targets produces default (often flat) geometry at those stations.

Corridor surfaces are created from links and feature lines in the corridor properties; the corridor surface is dynamic to the corridor and must be added to the surface list explicitly.

Sample lines cut sections through a corridor or surface at a station interval and at additional stations; section views display those sections with a group plot style.

A corridor's daylight subassembly needs a target surface; if the target is missing the daylight cannot compute and the corridor reports an error at those stations.

Material lists and quantity takeoff read corridor shapes and surfaces; pay items and the QTO manager compute quantities from those shapes.

Corridor rebuild order matters: change the alignment, profile, or assembly, then rebuild the corridor before extracting or reporting surfaces.

A pipe network is a set of pipes and structures; pipes connect to structures, and the network has one parts list that defines available sizes, materials, and rules.

Part rules (minimum and maximum cover, slope, drop across structure) are applied when parts are created or when rules are applied; they do not re-run automatically after later edits.

A pipe's flow is defined by its start and end structure invert elevations and its slope; changing the slope moves the downstream invert unless the invert is locked.

Interference checks compare pipe networks against other networks or 3D solids and report clashes with a clearance value.

QTO (quantity takeoff) computes volumes and areas from material lists and pay item lists; the results are a snapshot unless the report is regenerated after edits.

Sectional quantities come from sample line material lists; average end area volume = L x (A1 + A2) / 2, where L is the distance between sections.

Data shortcuts must be validated and repaired when source drawings move; a broken shortcut shows as a reference with a missing source path.

Audit and recover the drawing, and purge unused styles and objects, before archiving or handing off a project to keep the file size and dependencies controlled.