2.4 Topographic Surveys, Feature Coding, and Field Records
Key Takeaways
- Topographic surveys capture position (X, Y) and elevation (Z) of natural and built features, tied to project control, to produce a surface and feature map.
- Field-to-finish workflows use feature codes and linework codes in the data collector so points connect into lines, symbols, and surfaces automatically in the office.
- Breaklines force the triangulated surface (TIN) to honor real grade changes such as curbs, ditches, and ridges; mass points fill open areas.
- Complete field records — point numbers, codes, descriptions, instrument/antenna heights, and check shots — are essential to a defensible, reproducible survey.
Purpose and Tie to Control
A topographic survey captures the three-dimensional shape of a site — the X, Y, and Z of natural and built features — to produce a map showing contours, spot elevations, and feature locations. Every topo shot is referenced to project control (Section 2.3); without good control, the relative detail may be self-consistent but wrongly placed on the datum.
Data is collected with a total station (angle + distance to a prism), with RTK GNSS, or by terrestrial/aerial scanning. The surveyor selects shots that define the surface: tops and toes of slopes, grade breaks, edges of pavement, drainage flow lines, and enough interior mass points to model open ground. Point density must match the deliverable — a 1-ft contour map needs tighter spacing than a 5-ft map. Over-shooting flat areas wastes time; under-shooting grade changes loses the surface.
Field-to-Finish: Feature Codes and Linework
Field-to-finish is the workflow where each observed point carries a feature code (and often linework/connectivity codes) entered in the data collector, so the office software automatically draws lines, places symbols, and builds the surface with little manual editing. A consistent code library is essential — “EP” for edge of pavement, “CL” for centerline, “TREE” for a tree symbol, and control codes like begin line, close, curve, and point-on-curve.
| Element | Role in field-to-finish |
|---|---|
| Feature code | Identifies what the point is (curb, tree, manhole) |
| Linework code | Tells software to start/continue/close a line or curve |
| Point number | Unique key linking field shot to office point |
| Description | Human-readable note for QA and plat |
Errors in coding — a missed close, a mistyped code, a crossed line sequence — are the most common topo blunders and are corrected far more cheaply in the field than at the desk. Many crews record a quick note or photo for anything ambiguous.
Surface Modeling and Field Records
The office builds a surface as a triangulated irregular network (TIN) from the shots. Two point types control it:
- Mass points — scattered elevations that fill open, smoothly varying ground.
- Breaklines — connected lines along real grade discontinuities (curbs, ditch flow lines, ridges, retaining walls) that force triangle edges to follow them, so contours bend correctly instead of cutting across a curb.
Missing breaklines is a frequent FS topic: without them a TIN smooths over a curb or ditch and the contours are wrong even though every point is correct.
Defensible field records include the point numbers and codes, descriptions, instrument and target/antenna heights, control occupied and backsighted, date/crew/weather, and check shots to a known point at the start and end of a session to catch a bad setup or datum shift. The FS exam favors answers that pair adequate point selection and correct coding with breaklines and documented checks — the ingredients of a reproducible topographic survey.
On a topographic survey, what is the primary purpose of collecting breaklines rather than only mass points?
In a field-to-finish workflow, the role of a feature code entered at each point is to:
Why does a crew shoot a check shot to a known control point at the start and end of a topo session?
Methods, Density, and Common Topo Errors
Topographic detail is captured by several methods, and the FS exam expects you to match method to site. A total station with a prism gives precise, line-of-sight shots ideal under canopy or near buildings. RTK GNSS is fast in open areas but fails under trees and near structures from multipath and signal loss. Laser scanning / LiDAR captures dense point clouds for complex or hazardous features. Many surveys blend methods: GNSS in the open, total station where the sky is blocked.
| Method | Best where | Weakness |
|---|---|---|
| Total station | Line of sight, under canopy | Needs setup over control; slower |
| RTK GNSS | Open sky, large areas | Multipath/obstruction near trees, buildings |
| Laser scan / LiDAR | Dense detail, hazardous features | Data volume; registration to control |
Point density must suit the contour interval: a 1-ft contour map needs tighter spacing than a 5-ft map, and grade breaks always need a shot whether or not the open ground does. The most common topo blunders are not measurement errors but judgment and bookkeeping errors — too few shots across a slope so contours are wrong, a missed feature, a wrong instrument or rod height that shifts every elevation, or a code/linework mistake that crosses or fails to close a line. Disciplined records and check shots are what separate a defensible topo survey from a fast but unreliable one.
Deliverables and the Office Handoff
The topographic survey's deliverable is typically a base map with contours, spot elevations, planimetric features, and a tied surface model that downstream design work (grading, drainage, alignment) builds on. A clean field-to-finish handoff — correct codes, complete breaklines, documented control and instrument heights, and start/end check shots — means the office can produce that deliverable with minimal interpretation.
The recurring FS lesson is that topographic accuracy depends as much on what and how you record as on the raw measurement precision: the right shots, coded correctly and checked against control, are what make the map both accurate and defensible. Surveyors often capture a quick sketch or photo for any ambiguous feature so the office is never guessing about a code or a connection.
A topo map carrying a stated contour interval, a coordinate basis, the survey date, and the control it ties to is far more useful — and far more defensible — than an uncredited cloud of points, because every downstream user can judge its accuracy and reproduce it.