3.3 CAD, BIM, and Plan Production Workflows

CAD, COGO, and the Survey Coordinate Basis

Computer-aided design (CAD) is the drafting and geometry environment where survey data becomes plans. The bridge between field measurements and the drawing is COGO (coordinate geometry) — the routines that compute coordinates, inverse a bearing and distance between two points, intersect lines, offset alignments, and compute parcel areas (typically by the coordinate/shoelace method).

Every CAD survey drawing rests on a stated coordinate basis: a horizontal datum and projection (often State Plane Coordinates, NAD 83), a vertical datum (NAVD 88), and drawing units. Two issues dominate the FS exam:

• Units. A drawing must declare whether one drawing unit equals one US survey foot, one international foot, or one meter. Mixing US survey feet and international feet introduces ~2 ppm error (about 0.6 ft over a SPC northing of millions of feet) — small per length but large in absolute coordinates.
• Grid vs. ground. State Plane coordinates are grid values reduced by a combined scale factor; design and stakeout usually need ground distances. Multiplying or dividing by the wrong combined factor (grid-to-ground) misplaces or misscales the entire project.

Layers, Blocks, External References, and Annotation Scale

A well-built survey CAD file separates information so it cannot be confused:

• Layers group features by type and source (e.g., V-NODE field shots, V-PROP-LINE record/computed boundary, C-TOPO contours) and control color, lineweight, and on/off display.
• Blocks are reusable symbols (monuments, trees, inlets) inserted at point locations.
• External references (xrefs) attach other drawings (basemap, survey, design) by reference so a single source updates everywhere.
• Annotation (plot) scale governs how text and symbols size on the printed sheet; the same model geometry can be plotted at different sheet scales, and getting the annotation scale wrong yields unreadable or oversized text.

The survey deliverable must preserve the difference between field-located, computed, record, and design geometry — typically by layer and linetype. Mixing them is exactly the failure FS items probe: a record line and a measured line plotted on the same layer leaves the user unable to know which controls.

BIM and Civil Model-Based Workflows

Building Information Modeling (BIM) and civil corridor/surface models extend CAD into intelligent 3D objects with attributes. Survey data feeds these models as the existing-conditions surface and control. Regardless of platform, the surveyor must still document datum, units, geoid model, control basis, and source accuracy, because a 3D model that looks authoritative can carry an undocumented or wrong coordinate basis. The model inherits the accuracy of the survey; it does not improve it.

Plan Production and Quality Control

Turning the model into signed sheets is plan production, and it carries its own checks:

1. Plot/scale check — verify the graphic scale, sheet scale, and that distances measured from the plot match coordinates.
2. Layer/lineweight review — confirm existing vs. proposed, screening, and that survey vs. design layers are correct.
3. Title block metadata — datum, basis of bearings, project number, north arrow, units, surveyor seal, and revision history.
4. Coordinate integrity — confirm no inadvertent move/rotate has shifted the drawing off its control.

A common FS trap is a CAD operation that silently shifts coordinates: inserting a block or xref at the wrong base point, or scaling a drawing to fit a sheet, can translate the entire dataset. Because CAD will render anything without complaint, independent numeric checks against known control points — not visual inspection — are the reliable QC.

Point Files, Descriptors, and Surface Building

Field data usually enters CAD as a point file — rows of point number, Northing, Easting, elevation, and a feature code (descriptor) such as EP (edge of pavement), TC (top of curb), or TREE. Linework codes (begin/continue/close) let the software connect coded shots automatically into breaklines and figures. Getting descriptors right at collection time is far cheaper than reconnecting linework in the office, and a single mis-coded shot can drag a breakline across a building or invert a ditch.

From coded points the software builds the surface (TIN), draws contours, and supports COGO and design. The surveyor's checks are numeric and systematic:

• Confirm the coordinate range is plausible for the project's State Plane zone.
• Verify elevations against known benchmarks.
• Inspect the surface for spikes caused by a fat-fingered HI or rod height.
• Confirm closure on traverse points before they seed the drawing.

Deliverable Standards and Interoperability

A survey rarely lives in one program, so data exchange matters. Common transfer formats include DWG/DXF (CAD geometry), LandXML (points, surfaces, alignments, parcels in a neutral schema), shapefile/GeoPackage for GIS, and PDF for plotted sheets. When data crosses platforms, the three things most often lost or corrupted are units, datum, and the coordinate basis — exactly the metadata the surveyor must restate in the deliverable. A clean DWG handed off without a units statement or datum note is incomplete, even if the geometry is perfect.

The professional standard is that every electronic deliverable travels with enough metadata that a downstream user can place it correctly without guessing.