Write proper disclaimers when delivering GIS-grade versus survey-grade data
domain: asprs.org · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Determine which category the deliverable actually falls into: survey-grade output comes from a licensed boundary/control survey workflow with centimeter-level, verifiable positional accuracy, while GIS-grade/mapping-grade data (typical of handheld or mapping-grade GNSS) is order(s) of magnitude less precise, commonly in the roughly 0.5–5 foot range depending on equipment.
State the achieved accuracy quantitatively using an ASPRS-consistent accuracy statement (RMSE-based, per the current ASPRS Positional Accuracy Standards) rather than a vague 'approximate' label, whenever accuracy testing was performed.
Explicitly disclaim that GIS-grade/mapping-grade deliverables are not a boundary survey and do not establish legal property lines or corners — this line is required to avoid implying licensed survey work occurred when it did not.
If a licensed surveyor did not seal the deliverable, do not use survey terminology (e.g., 'boundary,' 'corner,' 'survey') that implies licensed practice in the disclaimer or on the map itself, since this can raise unauthorized-practice-of-surveying concerns under state law.
Include datum, coordinate system, collection method/equipment class, and date of collection alongside the accuracy disclaimer so downstream users can judge fitness for their intended use.
Known gotchas
Calling mapping-grade GIS output a 'survey' or implying boundary-level precision — even informally in a cover email — can create liability and, in some states, unauthorized-practice-of-surveying exposure; keep terminology and disclaimers consistent across all deliverables.
An accuracy disclaimer without a quantitative RMSE figure is weak protection; where testing was done, cite the number and the standard it was measured against.
Clients often reuse GIS-grade deliverables for purposes (fencing, construction layout) that require survey-grade accuracy — a clear, prominent disclaimer on the face of the map, not buried in a footer, reduces misuse risk.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?