A drone’s positioning specification is not the same thing as verified accuracy for the terrain data you plan to use for design. Before accepting a deliverable, ask for evidence that the finished dataset agrees with independently surveyed positions—not just a description of the equipment used to collect it.
That distinction matters because drone mapping accuracy depends on flight geometry, the arrangement of ground control and checkpoints, and surface conditions. Precise positioning helps, but it is only part of the workflow.
Ground control helps build the map; checkpoints test it
Ground control points, or GCPs, are locations with known coordinates used during processing to anchor a map to real-world positions. Checkpoints have surveyed coordinates too, but serve a different purpose: comparing the processed map with measurements that were not used to fit it.
The practical distinction is whether a point helped shape the result or was kept separate to evaluate it. A target’s appearance does not tell you which role it played.
For example, imagine a provider shows you a list of surveyed targets and their agreement with the map. Your next question should be: Which of these were used as control, and which were withheld as independent checks? A close fit at points used to build the map is not the same evidence as agreement at independent checkpoints.
This principle extends beyond drones. The Federal Geographic Data Committee’s National Standard for Spatial Data Accuracy describes evaluating coordinate differences at identical points using an independent source of higher accuracy.
What precise drone positioning does—and does not—prove
Real-time kinematic positioning, or RTK, and post-processed kinematic positioning, or PPK, are correction methods that improve the drone’s satellite-based positions. They reduce positioning error associated with images and can reduce the need for dense ground control.
But reduced reliance on control is not a reason to skip verification. Drone manufacturer Wingtra’s mapping guidance distinguishes checkpoints from processing inputs: checkpoints verify how closely the mapped position matches the measured ground position. Its guidance also identifies flight geometry, point layout and surface conditions as factors affecting accuracy.
For a project owner, the useful question is therefore not simply, “Was this flown with RTK or PPK?” It is, “What independent evidence supports the accuracy of the delivered terrain data?”
Ask which accuracy standard the report follows
Ask the provider to identify the standard and edition behind its accuracy statement. Avoid treating every report format or checkpoint count as interchangeable.
The U.S. Geological Survey’s summary of the American Society for Photogrammetry and Remote Sensing (ASPRS) Positional Accuracy Standards, Edition 2, Version 2, identifies several important changes:
- The minimum checkpoint count for product accuracy assessment increased from 20 to 30.
- The accuracy of the checkpoint surveys must be included when computing final product accuracy.
- References to the 95% confidence level as an accuracy measure were eliminated.
Those are changes within the identified standards framework—not a blanket statement that every drone mapping job legally requires 30 checkpoints. USGS says the revision was published in its Lidar Base Specification 2024 rev. A. The ASPRS announcement also identifies guidance addenda covering drone mapping and mapping from photographs.
The older federal standard describes reporting at the 95% confidence level. That contrast is another reason to ask for an exact edition rather than accept a vague claim of “standards compliance.”
This is general guidance, not a determination of legal or licensing obligations. Requirements vary by state and jurisdiction. Confirm applicable requirements with your state licensing board, county or a licensed professional before treating an accuracy report as sufficient for your project.
Questions to ask before accepting terrain data
Request evidence tied to your deliverable
- Which points were independent? Request separate identification of ground control and checkpoints, including confirmation that checkpoints were not used to fit the map.
- Where were the checks? Ask for a location diagram and an explanation of how the checks represent the areas and surfaces relevant to your design.
- What was compared? Request surveyed coordinates, corresponding dataset coordinates and their differences, with horizontal position and elevation results clearly identified.
- How accurate were the checkpoint measurements? Ask how their uncertainty was handled in the reported product accuracy.
- What acceptance target applies? Have the provider and design professional identify the agreed standard, edition and accuracy target.
Put these requests into the scope before collection begins. Before releasing terrain data for design, ask the responsible professional to review the checkpoint evidence against the agreed acceptance target—not the drone’s specification sheet.
Footnotes & Sources
- Drone surveying: how it works and what accuracy to expect | Wingtra, Wingtra. — Factors affecting drone mapping accuracy, the roles of control and checkpoints, and RTK/PPK position corrections.
- Ground control points: How many do you need? | Wingtra, Wingtra. — Ground control as a processing input, checkpoints as verification rather than processing inputs, and reduced ground-control needs with corrected positioning.
- National Standard for Spatial Data Accuracy, fgdc.gov. — Independent higher-accuracy coordinate comparisons and the older NSSDA reporting convention at the 95% confidence level.
- Adopt updated accuracy standards, U.S. Geological Survey. — ASPRS accuracy-assessment changes and their publication in the USGS Lidar Base Specification 2024 rev. A.
- ASPRS Positional Accuracy Standards for Digital Geospatial Data (2024) Announced – The American Surveyor, The American Surveyor, June 28, 2024. — Identification of ASPRS Edition 2, Version 2 and its drone-mapping and photogrammetry guidance addenda.