12.2 Geodesy, Mapping, and Field Scenario
Key Takeaways
- Mapping items depend on control quality, datum awareness, surface-model interpretation, and field verification, not vocabulary alone.
- Orthometric height H = ellipsoidal height h − geoid height N; GNSS gives h, so a geoid model is required for elevations.
- State Plane grid distances differ from ground distances by the combined factor (elevation factor × scale factor).
- LiDAR, UAS, and photogrammetric surfaces still require ground control and classification before contours are trusted.
- Convergence (mapping angle) separates geodetic north from grid north and grows with distance from the central meridian.
Scenario: a topographic deliverable tied to survey control
A crew must produce a topographic map for a drainage redesign. The project mixes static GNSS on two NGS marks, RTK observations, total-station shots under tree cover, and a digital terrain model (DTM) built from a UAS LiDAR flight. The engineer needs 1-ft contours, spot elevations on NAVD 88, and confidence that the surface is good enough for preliminary grading.
This blends several FS areas. Surveying Processes and Methods covers the field workflow and control; Mapping Processes covers DTMs, UAS, LiDAR, photogrammetry, GIS, and CAD; Surveying Principles covers datums, projections, and the geoid; and computations enter through accuracy, residuals, and the grid-to-ground problem.
Get the heights right
GNSS does not measure the elevations the engineer wants. A receiver returns ellipsoidal height h referenced to the GRS 80 ellipsoid (within NAD 83 / the modernized NSRS). The usable orthometric height H (NAVD 88) is found with a geoid model:
H = h − N
where N is the geoid height (geoid–ellipsoid separation, negative across most of the conterminous U.S.). If an item gives h = 152.40 m and N = −29.20 m, then H = 152.40 − (−29.20) = 181.60 m. Missing the sign of N is the most common geodesy trap on the exam. So a contour set straight from raw GNSS without a geoid model is suspect.
Grid, ground, and surface quality
State Plane grid-to-ground
State Plane Coordinate System (SPCS) values are grid distances; the engineer stakes ground distances. Convert with the combined factor:
Combined factor = elevation (sea-level) factor × scale factor
Ground distance = grid distance ÷ combined factor. The elevation factor ≈ R / (R + h) shrinks measured ground length to the ellipsoid; the scale factor carries it onto the projection (Lambert or Transverse Mercator). Near the central meridian or standard parallels the scale factor approaches 1; far from it the difference grows. Also remember convergence (γ), the angle between grid north and geodetic north — it increases with distance from the central meridian and must be applied when converting a grid azimuth to a geodetic bearing.
Trust the surface only after the checks
| Scenario fact | What it tests | Quality check |
|---|---|---|
| Static GNSS on NGS marks | Control / datum | Confirm NAD 83 realization and a current geoid model. |
| LiDAR DTM contours | Mapping process | Verify ground classification, breaklines, and field shots. |
| Total station under canopy | Field method limits | Use leveling/TS where GNSS multipath degrades RTK. |
| Spot elevations on NAVD 88 | Vertical datum | Apply geoid model; do not report h as H. |
| GIS/CAD layers | Standards / metadata | Check coordinate system, units, and layer integrity. |
A point cloud is not a bare-earth model until it is classified; LiDAR penetrates canopy only partially, so contours under heavy cover need verifying total-station shots. The exam often asks which single action most improves reliability — the answer is usually "tie it to control and verify in the field," not "buy a denser sensor." Connect each technology back to the survey control that supports it, and a digital map becomes survey practice rather than software vocabulary.
Field methods, leveling, and error checks
The field half of the scenario tests how observations are made and verified. Under tree canopy, RTK GNSS degrades from multipath and weak satellite geometry — high PDOP (positional dilution of precision) and a float (not fixed) solution are red flags. The professional move is to fall back to a total station traverse or differential leveling for the obscured shots, then check those against the open GNSS-derived control.
Differential leveling is a recurring computation: the height of instrument equals the known benchmark elevation plus the backsight (BS), and each new point elevation equals the height of instrument minus the foresight (FS) — written HI = elev + BS, and elev = HI − FS. A loop or level run is checked by closing back to a known elevation; the misclosure should fall within the project's allowable, often expressed as a constant times √(distance in miles or number of setups). Balancing backsight and foresight distances cancels collimation and curvature-refraction error.
Accuracy, precision, and residuals
The statistics topic enters through quality checks rather than abstract theory:
| Term | Meaning | Use on the exam |
|---|---|---|
| Accuracy | Closeness to the true value | Affected by systematic error and blunders. |
| Precision | Repeatability of measurements | Improved by better instruments/procedures. |
| Residual | Observation minus adjusted value | Drives least-squares and closure checks. |
| Standard deviation | Spread of a normally distributed set | ~68% of values within ±1σ of the mean. |
| Relative accuracy | Misclosure over distance (1:N) | Reports traverse/leveling quality. |
A tight (precise) set of contours can still be inaccurate if a control point was mis-entered or a datum was mixed — precision is not accuracy. So the strongest review answer ties the digital deliverable back to verified control, the right datum and geoid model, classified ground points, and a documented closure. That integration — geodesy, field method, mapping, and statistics in one workflow — is what the FS scenario items are really testing.
A GNSS observation gives ellipsoidal height h = 210.00 m and the geoid model gives N = −27.50 m. What is the orthometric (NAVD 88) height H?
Why must a State Plane grid distance be adjusted before it is staked on the ground?
In a UAS LiDAR mapping deliverable, which action most directly makes the contours trustworthy for design?
In differential leveling, a backsight of 4.20 ft is read on a benchmark at elevation 500.00 ft, then a foresight of 6.85 ft is read on a turning point. What is the turning point's elevation?