How Datum Errors Become Negligence Claims
A datum error crosses from "technical mistake" to legal claim when:
- A licensed professional owed a duty of care (surveyor, engineer, mapping firm)
- The professional deviated from the accepted standard of care for datum transformations
- The error caused measurable harm (construction costs, property loss, flood damage)
- The harm is quantifiable in dollars (cost of re-survey, rework, mitigation)
Standard of Care Thresholds by Accuracy Class
| Class | Precision | Max Datum Error Allowed |
|---|---|---|
| A — Geodetic Control | 1:100,000+ | ≤ 1 cm positional |
| B — Boundary Survey | 1:10,000 | ≤ 10 cm per 1,000 m |
| C — Construction | 1:5,000 | ≤ 20 cm per 1,000 m |
| D — Topographic/GIS | 1:1,000 | ≤ 1 m |
Any systematic datum error exceeding the class threshold is per-se evidence of standard-of-care breach.
Statute of Limitations by State (Survey Negligence)
| State | SOL Period | Discovery Rule? |
|---|---|---|
| Texas | 2 years (professional services) | Yes — from discovery |
| California | 3 years (professional negligence) | Yes |
| Pennsylvania | 2 years | Yes |
| New York | 3 years | Limited |
| Florida | 4 years (professional negligence) | Yes |
10-Point Datum Error Prevention Checklist
- Identify the project's legally required datum and coordinate system at project kickoff
- Confirm which EPSG code applies — do not assume "WGS84 = NAD83 = NAD83(2011)"
- Use the national grid-shift model (NADCON5, OSTN15, RDNAPTRANS2018) not a simple Helmert
- Document all datum transformations in the project technical report
- Verify the transformation with an independent check point of known coordinates
- Apply the combined scale factor (C = E × k) for all measured distances
- Flag any legacy data using older datums (NAD27, NGVD29) with explicit conversion notes
- For FEMA work: always use VERTCON for NGVD29 → NAVD88 — never a constant offset
- For pipeline/utility: document datum used for all as-built coordinates
- Obtain client sign-off on the coordinate system and datum before deliverable acceptance