2.4 Topographic Surveys, Feature Coding, and Field Records

Key Takeaways

  • Topographic surveys collect natural and built features needed for mapping, design, and analysis.
  • Feature coding, breaklines, point descriptions, and field sketches affect the quality of the final surface or map.
  • Good field records preserve context that coordinates alone cannot show.
  • FS questions may test which details must be collected for a usable topographic deliverable.
Last updated: May 2026

Collect Topographic Data So the Map Can Be Built Correctly

A topographic survey collects the shape of the ground and the visible features needed for mapping, design, permitting, construction, or analysis. The FS exam can test what to collect, how to code it, and why field records matter. A coordinate file alone is not a topographic survey if the points cannot be interpreted correctly.

Typical features include ground shots, grade breaks, roads, curbs, sidewalks, buildings, utilities, fences, drainage structures, trees, walls, water edges, and other site-specific details. The correct list depends on the scope. A drainage design survey needs inverts, pipe sizes, flow directions, grate elevations, channels, and breaklines. A site plan may need buildings, pavement edges, visible utilities, trees, property evidence, and access features.

Topographic itemWhy it matters
Ground shotsSupport contours, surfaces, spot elevations, and terrain models.
BreaklinesPreserve abrupt grade changes such as curbs, ditches, ridges, and walls.
Feature codesTell CAD or GIS software what each point represents.
DescriptionsAdd human-readable context for review and drafting.
Field sketchesClarify linework, feature relationships, and unusual conditions.
Quality checksCompare shots, control, and surface behavior before leaving the site.

Breaklines are especially important. If a crew collects many random ground shots but misses curb lines, ditch flowlines, or retaining wall edges, the digital terrain model may smooth across features that should be sharp. FS questions may ask why a contour map looks wrong even though many points were collected. The answer may be missing breakline logic rather than too few total points.

Feature coding connects field work to office processing. Consistent codes allow linework, symbols, layers, and surfaces to be generated efficiently. Inconsistent or ambiguous codes create drafting errors and rework. A point labeled UTIL with no description may be less useful than a point labeled WV for water valve or MH sanitary with rim and invert notes.

Field records preserve information that sensors do not capture. Notes can identify a locked utility structure, unsafe area, obscured feature, assumed pipe direction, inaccessible property corner, temporary obstruction, or observation made from an offset. A sketch can show how points connect when linework coding is uncertain.

Topographic surveys also require judgment about density. Flat open ground may need fewer shots than complex terrain. A steep swale, curb return, or drainage structure needs enough observations to represent its shape. The FS focus is the relationship between data collection and final deliverable quality.

Before leaving the site, crews should review coverage. Are all required features collected? Does the surface make sense? Are control checks acceptable? Are descriptions clear? Are there gaps that will require a return trip? Exam questions may frame this as choosing the best quality-control step.

Study topographic processes as a workflow from scope to field collection to CAD or GIS output. That helps you answer practical questions about what a surveyor should do, not just what a term means.

Test Your Knowledge

Why are breaklines important in a topographic survey?

A
B
C
D
Test Your Knowledge

Which field record best supports office processing of topographic data?

A
B
C
D
Test Your Knowledge

A surface model smooths across a curb that should be sharp. What field issue is most likely?

A
B
C
D