A drone can collect thousands of sharp photographs and still produce a map that is unsuitable for the job. The problem is usually not image quality. It is an incomplete scope.
"High accuracy," "survey grade," and "centimeter-level" are often used as sales language, but none of those phrases tells a client how accuracy will be measured, what coordinate reference will be used, whether independent checkpoints will be collected, or what happens if the finished product misses the requirement.
A better procurement process starts with the intended decision. A construction team checking stockpile changes needs a different product from an engineer coordinating site features, a facilities group documenting roof assets, or a surveyor using drone imagery as one input in a larger licensed workflow. The scope should define what the data must support before the contractor selects the aircraft, flight altitude, control method, or processing settings.
Start With the Use Case, Not a Generic Accuracy Number
The first question should be: What will someone do with the map?
Common commercial uses include:
- visual progress documentation;
- plan-to-field comparisons;
- earthwork and stockpile calculations;
- roof, pavement, façade, or asset inventories;
- preconstruction condition records;
- orthomosaic basemaps;
- three-dimensional site models;
- drainage or surface-review support; and
- measurements that will be checked or incorporated by a licensed professional.
Each use has a different tolerance for positional error, surface noise, occlusion, vegetation, reflective materials, and incomplete coverage. A client who only needs a current visual basemap may not benefit from an expensive control network. A client using elevations for payment quantities or design coordination needs a documented and independently tested workflow.
Do not ask a contractor to choose the required accuracy after the proposal is awarded. State the business use, required features, acceptable error, coordinate system, and validation method in the request for proposal.
Accuracy, Resolution, and Precision Are Not the Same Thing
These terms are frequently mixed together.
Resolution describes the level of visible detail, often expressed as ground sample distance. A small ground sample distance can make an image look detailed, but it does not prove that the image is correctly positioned on the earth.
Precision describes repeatability. A dataset may be internally consistent while the entire model is shifted horizontally or vertically.
Accuracy describes how closely measured positions match accepted reference positions. This is the client-facing requirement that needs a test method.
A dense point cloud and crisp orthomosaic can therefore be precise and visually impressive while still failing the project's positional requirement. The specification should separate image resolution from horizontal and vertical accuracy.
Define the Coordinate Reference and Units
The scope should identify the horizontal coordinate reference system, vertical datum, geoid model when applicable, and units. "State plane" is not enough. The exact zone, datum realization, vertical reference, and unit must be stated.
This prevents common handoff problems such as:
- feet being interpreted as meters;
- international feet being mixed with U.S. survey feet;
- ellipsoid heights being mistaken for orthometric elevations;
- data being delivered in a local coordinate system without transformation notes; and
- CAD, GIS, and photogrammetry files appearing offset when combined.
Require the contractor to repeat the coordinate information in the final report and in file metadata where the format supports it.
Understand GCPs, Checkpoints, RTK, and PPK
Ground control points, or GCPs, are surveyed targets or identifiable features used to help position and constrain the photogrammetric model. They are part of the solution.
Checkpoints are independent surveyed points withheld from model adjustment and used to test the finished product. They are part of the verification.
That distinction matters. Reporting residuals only on points used to build the model does not independently demonstrate final product accuracy.
RTK and PPK workflows can improve the estimated position of each image. RTK applies corrections during collection; PPK applies them afterward. Both can reduce field-control requirements on suitable projects, but neither automatically proves final map accuracy. Satellite geometry, base-station quality, camera calibration, terrain, vegetation, flight design, image blur, processing choices, and the stability of the correction link or reference data can affect results.
For a consequential project, require independent checkpoints even when the aircraft uses RTK or PPK. The appropriate number and distribution should be based on project size, terrain, product type, risk, and the governing standard or professional judgment—not a one-size-fits-all claim.
Put an Accuracy Statement in the Scope
A usable requirement identifies four things:
- The product being tested, such as an orthomosaic, surface model, point cloud, or contours.
- The horizontal and vertical accuracy class or numerical tolerance.
- The test method and reporting statistic.
- The independent reference data used for testing.
ASPRS publishes industry-consensus positional accuracy standards for digital geospatial data. Its 2024 Edition 2, Version 2 includes addenda for photogrammetry, UAS, field surveying, lidar, and oblique imagery. A project may cite the relevant standard directly or use it as the basis for a tailored acceptance requirement.
Avoid vague clauses such as "accuracy within two centimeters" unless the contract explains whether that means horizontal, vertical, root mean square error, a confidence statistic, a maximum residual, or another measure. Also specify whether the tolerance applies across the entire project or only under defined surface and visibility conditions.
Require a Flight and Control Plan
Before mobilization, the contractor should provide or confirm a concise plan covering:
- target ground sample distance;
- planned altitude and image overlap;
- camera orientation and whether oblique imagery is included;
- expected site access and control placement;
- checkpoint count and distribution;
- treatment of vegetation, water, reflective roofs, narrow corridors, and vertical surfaces;
- airspace status and authorization needs;
- operations over people or vehicles;
- weather and sun-angle limits;
- coordinate reference and units;
- data-retention period; and
- contingency steps if control is disturbed or coverage is incomplete.
FAA compliance belongs in this plan, but regulatory compliance and mapping accuracy are separate issues. Part 107 governs the flight. It does not certify the positional accuracy of the resulting map. Controlled-airspace operations require authorization, and the remote pilot remains responsible for operating limitations, visual line of sight, aircraft safety, and other applicable rules.
Specify Deliverables, Not Just "A Map"
A complete scope should list required files and formats. Depending on the project, deliverables may include:
- georeferenced orthomosaic;
- digital surface model or digital terrain model;
- classified or unclassified point cloud;
- contours with stated interval and generation method;
- textured three-dimensional mesh;
- CAD or GIS feature layers;
- control and checkpoint coordinates;
- flight log or mission summary;
- processing report;
- accuracy report;
- coordinate-system statement;
- excluded-area or limitation map;
- web viewer; and
- original imagery when contractually required.
State whether the client needs GeoTIFF, LAS or LAZ, CSV, DXF, SHP, GeoPackage, PDF, OBJ, or another format. Define naming conventions, layer structure, units, and whether tiled files are acceptable.
For long-term value, require enough documentation that another qualified person can understand how the dataset was produced. A web viewer alone is convenient but may not be an adequate archival deliverable.
Include Independent Acceptance Criteria
The contract should explain how delivery will be accepted. A practical acceptance checklist can require:
- all required files open successfully;
- coordinate systems and units match the scope;
- checkpoint results meet the stated requirement;
- checkpoint coordinates and residuals are included;
- voids, blurred areas, reconstruction artifacts, and excluded surfaces are disclosed;
- deliverables cover the agreed boundary;
- the report identifies collection dates, aircraft, sensor, processing software, and material workflow assumptions; and
- any failed area is recollected, reprocessed, excluded, or accepted through a documented exception.
Do not rely only on a screenshot of software residuals. Ask for a readable table showing each independent checkpoint, reference coordinate, measured coordinate, residual, and summary statistic.
Know When a Licensed Surveyor Should Be Involved
Drone mapping can support surveying, engineering, construction, inspection, and asset-management work, but professional-practice laws vary by state and by intended use. A drone contractor should not represent a product as a boundary survey, certified topographic survey, or other regulated professional service unless the work is performed under the required license and authority.
When outputs will establish property boundaries, support stamped design, control legal rights, or serve another regulated purpose, involve the appropriate licensed professional early. That person can define control, accuracy, deliverables, and certification requirements before collection begins.
A Better Request-for-Proposal Paragraph
A client can adapt the following structure:
"Provide a georeferenced orthomosaic and surface model for the defined project boundary in the stated horizontal coordinate system, vertical datum, and units. The products must meet the specified horizontal and vertical accuracy requirements when tested against independent checkpoints not used in model adjustment. Submit the proposed flight design, control and checkpoint plan, required airspace approach, file formats, processing report, checkpoint residual table, known limitations, and corrective-action process before mobilization."
The exact numbers and standards should be supplied by the project's qualified technical lead. The value of the paragraph is that it makes the contractor explain the method and the proof.
The Bottom Line
Drone mapping accuracy is not a feature that comes automatically with an RTK label, a low flight altitude, or expensive processing software. It is a project requirement that must be designed, measured, reported, and accepted.
The strongest commercial scopes define the intended decision, coordinate reference, accuracy class, independent checkpoints, file formats, limitations, and remedy for failure. When those items are agreed before the flight, clients can compare proposals on method and accountability instead of marketing language.
FAQs
Does an RTK drone eliminate the need for ground control?
Not always. RTK can reduce the amount of control needed, but project conditions and accuracy requirements still matter. Independent checkpoints remain valuable because they test the finished product rather than helping build it.
Is ground sample distance the same as map accuracy?
No. Ground sample distance describes image detail at the ground. Positional accuracy describes how closely mapped coordinates match accepted reference coordinates.
How many checkpoints should a drone-mapping project use?
There is no responsible universal number. The count and distribution should follow the applicable standard, project size, terrain, product type, risk, and qualified professional judgment. Checkpoints should be independent and distributed across the project.
Can a drone map be called "survey grade"?
The phrase is incomplete without a stated accuracy standard, validation method, coordinate reference, and professional context. Regulated surveying claims also depend on state law and the intended use of the product.
What should a client receive with the final map?
At minimum, the agreed geospatial files, coordinate-system statement, processing summary, checkpoint results, known limitations, and any required source imagery or archival files should be delivered.
Source Notes
- FAA — Small Unmanned Aircraft Systems Regulations (Part 107): https://www.faa.gov/newsroom/small-unmanned-aircraft-systems-uas-regulations-part-107
- FAA — Part 107 Airspace Authorizations: https://www.faa.gov/uas/commercial_operators/part_107_airspace_authorizations
- FAA — UAS Facility Maps: https://www.faa.gov/uas/commercial_operators/uas_facility_maps
- ASPRS — Positional Accuracy Standards for Digital Geospatial Data, Edition 2 Version 2: https://www.asprs.org/Main/Main/Standards/Positional-Accuracy-Standards.aspx
- ASPRS — 2024 standards adoption notice and UAS addendum summary: https://old.asprs.org/archives/asprs-approves-edition-2-version-2-of-the-asprs-positional-accuracy-standards-for-digital-geospatial-data-2024.html
- USGS — Aerial Imaging and Mapping: https://www.usgs.gov/centers/whcmsc/science/aerial-imaging-and-mapping
- USGS — Ground Control Points: https://www.usgs.gov/landsat-missions/ground-control-points
- USGS — Checkpoint documentation requirements example: https://www.usgs.gov/ngp-standards-and-specifications/require-photographs-checkpoints