2.3 Control Surveys, Networks, Traverses, and Benchmarks

Build the Framework Before Collecting Details

Control surveys establish the spatial framework for a project. Boundary retracement, topographic mapping, construction staking, as-built surveys, and land development work all depend on control that is appropriate for the deliverable. If control is weak, later detail shots may look precise while still being wrong in position, elevation, orientation, or scale.

Horizontal control may be established by traversing, GNSS/GPS methods, resection, intersection, or connection to existing control. Vertical control may use benchmarks, differential leveling, trigonometric leveling, or GNSS/GPS-derived methods with proper vertical reference handling. The FS exam often asks candidates to recognize which check or workflow is appropriate, not merely to compute a number.

A traverse is more than a sequence of lines. It is a controlled observation network with angles, distances, setups, backsights, foresights, and closures. A closed traverse or a traverse tied to known control gives evidence about the quality of the observations. FS computation chapters handle adjustment details, but field-process questions can ask why closure matters and what a poor closure suggests.

Control documentation must be detailed enough for future use. Field records should identify point names, descriptions, monument type, coordinates, elevations, datum, coordinate system, units, observation method, date, crew, and unusual conditions. A point called CP-1 without a description or reference can be difficult to recover or defend later.

Benchmarks need special care. A benchmark set in unstable material, disturbed ground, or a place likely to be destroyed by construction may fail the project even if the original observation was accurate. For construction and as-built work, vertical control should be checked before relying on it for grades.

Control networks also require judgment about scale and purpose. A small site topographic survey may not need the same control design as a corridor project, but both need a framework that supports the deliverable. A cadastral retracement may need strong ties to record monuments and evidence, while a mapping project may emphasize coordinate consistency and coverage.

FS scenarios may describe a crew collecting hundreds of topo points before discovering that the backsight was wrong or the benchmark elevation was assumed incorrectly. The exam-aligned response is to understand that control is not administrative overhead. It is the basis for every later observation.

When studying, practice naming the control risk in each project type. Ask whether the problem is horizontal, vertical, datum-related, monument-related, closure-related, or documentation-related. That diagnostic habit connects field processes to computations, mapping, and boundary law.