Buy a Usable Dataset, Not Just a Sharp Picture
A drone-mapping package should answer a project question, open in the client’s software and include evidence supporting its intended use. A visually impressive map is only part of that package.
Before commissioning a flight, agree on the products, coverage, coordinate references, accuracy assessment and acceptance process. Otherwise, the operator may deliver exactly what was quoted while the client receives something that cannot support the decision they need to make.
This guide offers a practical specification framework for Canadian project teams. It does not prescribe a universal accuracy threshold, certify a dataset or replace project-specific professional requirements.
What the client needs
Products matched to a defined use, clear references, compatible files and documented limitations.
What should not be assumed
That small pixels prove accuracy, an attractive model is bare-earth terrain or an RTK label settles quality assurance.
Start with the Decision the Data Must Support
Progress reporting, stockpile comparison, asset inspection and terrain analysis are different tasks. The required products and evidence should follow the intended use rather than a standard bundle offered without discussion.
Write a short project brief
Identify the area, features of interest, date or monitoring interval, intended users and receiving software. State whether the output is for visual context, measurement, comparison or another specified purpose.
Ask the responsible project professional to define necessary tolerances and any applicable contractual standards. Do not select an accuracy claim because it sounds impressive or simply copy it from a different project.
Specify exclusions
Identify inaccessible areas, obscured surfaces, water, moving objects or other conditions that may limit coverage. Require the supplier to mark gaps and explain limitations rather than silently filling the delivery with an apparently complete surface.
Choose the Products You Actually Need
USGS describes an orthomosaic as a combination of orthorectified images used as a geospatial base map. Its photogrammetry guidance also distinguishes terrain models that represent ground elevations from products that include above-ground features. Agree on product definitions in the scope.
| Product | Potential project use | What to specify or verify |
|---|---|---|
| Orthomosaic | Georeferenced visual context and agreed plan-view tasks. | Coverage, pixel size, image quality, coordinate reference and supported positional accuracy. |
| Point cloud | Three-dimensional analysis and downstream processing. | Coordinate reference, required attributes, classification if needed, gaps and receiving-software compatibility. |
| Surface or terrain model | Elevation-related analysis appropriate to the product. | Whether buildings and vegetation are included, how ground is identified and where the surface is uncertain. |
| Mesh or visual model | Communication, visualization and asset context. | Model completeness, texture quality, viewing requirements and any restrictions on measurement. |
| Derived measurements | Agreed volume, distance or change-reporting tasks. | Method, boundaries, reference surfaces, units and uncertainty relevant to the result. |
| Quality and metadata package | Review, acceptance and future reuse. | Capture details, processing record, accuracy assessment, limitations and file inventory. |
Do not treat a surface model as bare earth by default
Ask what each elevation cell represents. If the intended analysis needs ground levels beneath vegetation, request evidence that the delivered method and dataset can support that use. A terrain label should be backed by a documented process and limitations.
Agree on source-data delivery
If future reprocessing matters, specify which original images, positioning records, project files or other inputs are included. Establish ownership, permitted use, storage arrangements and any software dependencies before work begins.
Resolution Is Not Positional Accuracy
USGS calibration guidance explicitly warns against assigning higher accuracy merely because imagery has a lower ground sample distance. Fine image detail and trustworthy coordinates are related workflow concerns, not interchangeable measurements.
Ask what the accuracy statement means
Require the report to identify the product tested, horizontal and vertical results where relevant, assessment method, reference data, units and limitations. An overall “centimetre-level” claim without this context is difficult to evaluate.
Keep control and independent checks separate
USGS orthoimagery guidance describes accuracy testing with independent checkpoints not used in initial georeferencing. Its lidar specification likewise distinguishes calibration control from checkpoints used to assess accuracy. These are useful quality-assurance principles, not a declaration that every USGS specification is mandatory for a Canadian project.
Ask which points influenced the solution and which were reserved for independent assessment. Require enough information for the responsible reviewer to understand the test design and whether it represents the area being delivered.
Do not turn equipment labels into acceptance evidence
Request documentation of the actual positioning and processing workflow, followed by an appropriate assessment of the delivered products. An RTK-equipped aircraft or a successful processing screen should not substitute for the evidence specified in the contract.
Name the standard and edition when one applies
USGS notes changes in updated ASPRS accuracy standards. If the project adopts a standard, state its edition, relevant clauses and reporting method rather than combining thresholds from different publications. The responsible project professional should determine the applicable requirements.
Buyer’s question: “What independent evidence shows that this delivered product meets the requirement for my use?” is more useful than “How small are the pixels?”
Make Coordinates and File Compatibility Explicit
As a recommended handover practice, request the full coordinate-reference description rather than an ambiguous shorthand. Have the project’s geospatial lead confirm horizontal reference, projection, vertical reference, units and any relevant realization, epoch or transformation details.
Ask for a sample before the full delivery
Request a representative file and open it in the actual receiving software. Check that it appears in the expected location, carries the required attributes and can support the intended task. A screenshot of a correctly positioned model is not the same as a successful client import.
Agree on formats, versions and packaging
Specify the raster, point-cloud, vector or model format appropriate to your workflow, including version requirements, compression, tiling and naming where necessary. For example, GeoTIFF or LAS/LAZ may be candidates to discuss, not automatic requirements or proof of compatibility.
Include a readable file inventory explaining each product, its units and its intended use. State whether access depends on a hosted viewer, a subscription or specialist software, and what remains accessible if a service ends.
Plan recurring surveys for comparison
If change detection is the goal, define a consistent reference framework, comparable boundaries and a method for distinguishing real change from uncertainty. Ask how differences in capture and processing will be documented between visits.
A Practical Acceptance Checklist
- Confirm the brief. The delivery covers the agreed area, date, products and intended use.
- Open the files. Test representative outputs in the receiving software, not only the supplier’s viewer.
- Check references and units. Resolve unexplained shifts, height differences or scale issues before measurement.
- Review the quality evidence. Compare the reported assessment against the agreed method and acceptance criteria.
- Inspect coverage and limitations. Confirm that gaps, obscured areas and uncertain surfaces are clearly identified.
- Test the intended task. Have the responsible user carry out a representative workflow or calculation.
- Record acceptance or corrections. Keep versioned files, unresolved issues and the approving person’s decision together.
Suggested scope wording
“Provide the agreed mapping products for the defined area in the client-approved reference framework and formats, with capture and processing metadata, documented limitations and an accuracy assessment against the agreed project criteria. Acceptance includes successful import into the receiving workflow and review by the designated project representative.”
This is a planning starting point, not a complete contract. Add project-specific tolerances, responsibilities, correction procedures, delivery dates and data-handling terms with the appropriate advisers.
Match the equipment to the deliverable
Once the required outcome is defined, evaluate the capture and processing system against it. The best procurement question is whether the complete workflow can reliably produce an acceptable dataset, not which aircraft has the most attractive headline specification.
For wider planning, see our data-security review framework and our fleet-transition cost checklist.
Supplier disclosure: Unmanned Canada sells DJI equipment. This article does not certify any aircraft, dataset or supplier as suitable for a regulated professional task. Confirm project-specific responsibilities and acceptance with qualified reviewers.
Frequently Asked Questions
Does a small ground sample distance prove map accuracy?
No. USGS warns against inferring accuracy from GSD alone. Request a documented assessment of the delivered product against the project requirement.
Is an orthomosaic enough for every project?
No. It may provide the required visual base, but elevation analysis, 3D workflows or defensible measurements may require additional products and quality evidence.
Are ground control and checkpoints interchangeable?
Not for an independent assessment. Ask which points influenced the solution and which were held out for testing, along with the applicable assessment method.
Does RTK remove the need to check the deliverable?
Do not treat RTK as a substitute for acceptance. The buyer still needs evidence supporting the actual output, reference framework and intended use.
Should every client request the same accuracy?
No universal threshold is proposed here. Have the responsible project professional define the necessary tolerances and assessment method for the decision the data must support.
What is the most useful check before commissioning?
Agree on a written deliverables and acceptance schedule, then test a representative sample in the receiving workflow before committing to a large handover.
Start with the Deliverable Your Team Needs
Bring your project area, intended use, software workflow and required outputs. Unmanned Canada can discuss equipment and workflow considerations before you commit to a capture system.
Discuss Your Mapping RequirementsSources and Editorial Notes
- USGS: Guidelines for calibration of uncrewed aircraft systems imagery, GSD, control and accuracy considerations.
- USGS: NUSO research activities, orthorectification and orthomosaics.
- USGS: Creating point clouds, elevation models and orthomosaics through photogrammetry, surface and terrain terminology.
- USGS: Digital Orthoimagery Base Specification V1.0, independent-checkpoint principle; not asserted as a current Canadian project mandate.
- USGS: Lidar processing and handling requirements, control and checkpoint distinction, specific to its stated scope.
- USGS: Adopt updated accuracy standards, why editions and reporting methods matter.
- Niricson: Toronto Pearson Airport project, illustration source, not the source of the general acceptance checklist.
Reviewed November 7, 2026. The specification and acceptance checklist is editorial guidance. US technical sources are used for defined concepts, not presented as binding Canadian requirements. No universal accuracy, certification or suitability claim is made.
General information, not a professional survey opinion, legal advice or certification. Have the responsible professionals define and approve requirements for the intended use.
