Measurement and Positioning Systems
Measurement and Positioning Systems
This domain tests how observations become positions: total stations, GNSS, levels, datums, control, and grid-to-ground reductions. Minnesota questions often turn on whether a measurement is precise but not accurate, or accurate but on the wrong datum.
Core rules
- Precision is repeatability; accuracy is closeness to truth. A tight cluster on the wrong monument is precise but wrong.
- GNSS positions are referenced to NAD83 (current realization) and orthometric heights to NAVD88 via a geoid model. A handheld autonomous fix is not boundary-grade.
- Minnesota State Plane has North, Central, and South zones; grid distances differ from ground distances by a combined scale/elevation factor. State plane coordinates are a reference system, not a boundary monument.
- Total-station work requires occupied control, backsight check, and closure checks. Leveling requires balanced sight distances and turning points on stable marks.
- ALTA/NSPS surveys and Minnesota minimum standards require documenting basis of bearing, datum, monuments, and uncertainty.
Worked example
A ground distance of 1,000.000 ft is measured between two state-plane control points. The combined factor is 0.99995. Grid distance = 1,000.000 × 0.99995 = 999.950 ft. If a deed distance is 1,000.00 ft and the question asks for the grid value, report 999.95 ft, not 1,000.00. Reason: the combined factor converts ellipsoid/grid to ground; applying it in the wrong direction creates a 0.05 ft error that matters at boundary tolerances.
Traps
Confusing precision with accuracy; using ellipsoid height as orthometric height; ignoring the combined factor; holding a GNSS fixed solution as a monument; failing to check a backsight; reporting more significant figures than the observation supports.