Drone survey deliverables: a buyer's checklist
A survey is only as useful as its accuracy statement, its control points, and its file formats. A checklist for buyers writing a drone survey scope.
Buyers often ask for "a drone survey" and receive a folder of images. The images are the raw material. The deliverable is the set of products that a surveyor, engineer, or GIS team can use without re-doing the work. Writing the scope around those products, rather than around the flight, is the single most useful thing a buyer can do.
The products to ask for
A complete drone survey normally includes:
- Orthomosaic. A georeferenced image of the site with the perspective removed, for measurement and visual review.
- Digital Elevation Model (DEM). A height surface of the terrain, and for many projects a digital surface model that includes structures.
- 3D point cloud. The dense set of measured points, in a format your GIS or CAD tools can open.
- Volumetrics. Stockpile or cut-and-fill volumes, where the project needs them, with the baseline surface stated.
- Control and accuracy report. The ground control points used, their coordinates, and the measured error against independent check points.
If any of these are missing from a quote, ask why. Often it is an omission, not a cost saving.
Accuracy is a statement, not a promise
"Survey-grade" is not a measurement. The accuracy of a drone survey depends on the ground control, the camera, the flight height, and the processing. A well-scoped survey states:
- The coordinate system and vertical datum.
- The number and layout of ground control points.
- The check points used to test accuracy, kept separate from the control.
- The resulting error, reported at a stated confidence.
A check point held out from processing is the only honest test of whether the survey is correct. Ask for it.
Compliance belongs in the scope
Commercial drone operations are regulated, and the regulatory details differ by jurisdiction. The scope should say which airspace framework applies, how flights are planned and notified, and who holds the operating authority. A project that skips this step can be stopped mid-survey, which costs more than the paperwork.
File formats decide who can use it
Deliver in formats the receiving team already uses: GeoTIFF or a standard tiled format for raster products, and common point cloud formats for the 3D data. Include the metadata that makes a file usable later: the coordinate system, the capture date, and the processing version.
A short checklist for the scope
- Named products: orthomosaic, DEM, point cloud, and volumetrics if needed.
- Coordinate system and vertical datum stated.
- Ground control and independent check points, with the accuracy result reported.
- Airspace compliance and operating authority named.
- Delivery formats and metadata specified.
- Acceptance criteria written so either side can test them.
A scope written this way is short, and it makes the survey easy to check when it arrives.
Clean-room write-up — public / synthetic data only.