4.3 Topographic, Hydrographic, and Remote Sensing Surveys

Topographic mapping

A topographic survey depicts the shape of the ground (relief) and planimetric features (buildings, pavements, utilities, vegetation) for design or mapping. NCEES lists topographic and planimetric mapping and control standards, interpretation and adjustment of topo data, QA/QC, ground/hydrographic/remote-sensing equipment, the U.S. National Map Accuracy Standards, and utility nomenclature.

Density, breaklines, and contours

A surface model is only as good as its data. Breaklines are lines along which the surface changes slope abruptly: curbs, ditches, ridges, tops and toes of slope, edges of pavement. A triangulated surface that ignores breaklines will smooth across these edges and misrepresent drainage. Collect breaklines, not just random spot shots.

Contour interval is the vertical spacing between contour lines. Flat sites and detailed grading need a tight interval (for example 0.5 or 1 ft); steep or reconnaissance terrain can use a wider interval. A tighter interval demands denser data and better vertical control.

Map accuracy standards

The U.S. National Map Accuracy Standards (USNMAS, 1947) are listed on the exam. They define horizontal and vertical tolerances for well-defined points relative to map scale and contour interval. Modern work also uses FGDC/NSSDA reporting at 95 percent confidence. Match the stated standard to the deliverable.

Hydrographic and bathymetric surveys

Hydrographic and bathymetric surveys measure water depth and the underwater surface. Single-beam echo sounders measure a line of depths beneath the boat; multibeam systems sweep a swath for full-coverage seafloor mapping. Depths are referenced to a sounding datum (often a low-water datum), and horizontal positions come from GNSS, with corrections for vessel motion, tide, and sound velocity in water. The exam point: water-depth work needs both a horizontal reference and a properly stated vertical/sounding datum, plus corrections that ground surveys do not require.

Remote sensing and validation

LiDAR and photogrammetry produce dense surface data quickly, but they are not self-validating. Both require:

1. Ground control to register the data to a datum and frame.
2. Classification (for LiDAR, separating ground from vegetation and structures).
3. Validation against independent checkpoints to confirm accuracy.
4. Metadata stating sensor, datum, projection, units, density, and accuracy.

A point cloud labeled accurate without checkpoints, datum, and metadata is not defensible. The professional response on the exam is to require control, classification, validation, and documentation before relying on remotely sensed surfaces.

Field methods and data density

Ground topographic data still come from total stations and GNSS RTK. The crew collects spot elevations on a grid or feature-coded basis, captures breaklines along edges, and adds checkpoints. Data density should match the contour interval and design use: a parking-lot grading plan at 0.5 ft contours needs far denser, more accurate points than a reconnaissance map at 5 ft contours. Sparse data plus a tight interval produces contours that look precise but are not supported by the observations, a classic over-claim the exam penalizes.

Interpreting and adjusting topo data

Raw topo data contain errors: a miskeyed rod height, a shot on a vehicle instead of ground, a busted code. QA/QC for topographic surveys includes reviewing the surface for spikes and pits, checking that breaklines do not cross, confirming that contours follow drainage logically (contours point upstream when crossing a channel), and validating against independent checkpoints. The surveyor reconciles conflicting shots and removes blunders before generating the deliverable surface.

Contours and surface logic

Contours obey rules the exam can test: they never cross (except at a vertical cliff), they close on themselves or run off the map, they are evenly spaced on uniform slopes and tightly spaced on steep ground, and a V pattern points upstream in a valley and downhill on a ridge. Reading these patterns lets a surveyor sanity-check a surface and catch a flipped sign or a missing breakline.

Hydrographic corrections in detail

Hydrographic depth must be corrected for several effects that ground surveys ignore: sound velocity in the water column (which varies with temperature and salinity), vessel motion (heave, pitch, roll, yaw measured by an inertial unit), draft and squat of the vessel, and tide or water-level reduction to the sounding datum. A multibeam survey without sound-velocity and motion correction can show false ridges and troughs. The deliverable must state the horizontal datum, the vertical and sounding datum, and the corrections applied, so a reviewer can judge the bathymetric surface.

Utility nomenclature on topographic maps

NCEES lists utility nomenclature under topographic. A topographic map that depicts utilities must label features and qualify their source: a manhole, catch basin, valve, hydrant, meter, pedestal, or transformer observed on the surface is mapped as observed evidence, while subsurface alignment between those features is inferred unless verified. The map should distinguish observed surface evidence from utility-record data and from designated or located lines, mirroring the quality levels used in subsurface utility work. Mislabeling inferred lines as verified is a common over-claim.

Choosing a method for the deliverable

The method must match the required accuracy and feature detail. A high-detail grading survey of a small site favors total station or RTK ground collection with dense breaklines; a large corridor or watershed favors aerial photogrammetry or LiDAR with ground control and checkpoints; an underwater surface requires hydrographic equipment. The exam rewards matching the tool to the accuracy standard, the terrain, and the deliverable rather than defaulting to one technology. Whatever the method, control, validation against checkpoints, and complete metadata are non-negotiable before the surface is relied upon.