1. Introduction
AirWorks can process drone data from any provider, as long as the processed outputs meet the specifications below.
The most important point: AirWorks processes finished, georeferenced deliverables, not raw drone photos. Your drone provider must stitch and georeference their imagery into an orthomosaic (and, if you need elevation, a point cloud) before the data comes to AirWorks.
Share this page with your drone provider before the flight. Specs that are caught before capture cost nothing; specs that are missed after capture usually mean a re-fly.
2. What to Deliver
|
Deliverable |
Required? |
Format |
Purpose |
|---|---|---|---|
|
Orthomosaic |
Required |
GeoTIFF ( |
Planimetric feature extraction (2D basefile) |
|
Point cloud |
Required for elevation/topo |
|
Elevation, 3D features, topo |
|
Coordinate system info |
Required |
EPSG code embedded in files |
Correct placement of your deliverable |
|
Vertical datum |
Strongly recommended |
Stated with delivery |
Correct elevations |
|
GCP / checkpoint report |
Strongly recommended |
PDF or CSV from provider |
Accuracy verification |
|
Project boundary |
Optional (can be drawn in app) |
|
Defines the processing area |
3. Detailed Requirements
3.1 Orthomosaic
-
Format:
.tifor.tiff(GeoTIFF). -
Ground Sample Distance (GSD): between 0.01 and 0.25 ft (about 0.3–7.6 cm).
-
Survey-grade accuracy (1/10 ft): GSD below 0.05 ft (about 1.5 cm).
-
Georeferencing: must be georeferenced to a recognized coordinate system with an EPSG code. Imagery without a coordinate system cannot be processed.
-
Distortion: minimal. Watch for smearing, warping, or ghosting at the edges of the capture and around tall structures.
-
Coverage: the orthomosaic must fully cover the project boundary, with margin.
If your imagery is coarser than the GSD threshold, the AirWorks app will show a warning. You can proceed if you don't need a highly accurate deliverable.
3.2 Point Cloud
-
Format:
.lasor.laz(multiple versions accepted). -
Photogrammetric point clouds: density above 400 points per square meter; ideally above 800.
-
LiDAR point clouds: point spacing under 1 ft in both directions; ideally under 6 in.
-
Must be in the same coordinate system as the orthomosaic.
3.3 Coordinate System and Datum
-
Horizontal coordinate system must be embedded (EPSG code) in both the orthomosaic and point cloud.
-
State the vertical datum (e.g., NAVD88) and units (US survey feet, international feet, or meters) with your delivery.
-
If ground control points (GCPs) or checkpoints were used, include the provider's accuracy report.
See Coordinate Reference System (CRS) for more detail.
3.4 Project Boundary
You can draw your boundary directly in the AirWorks app, which avoids misalignment issues. If you're uploading a boundary file, use a single, fully enclosed .kml polygon. See Accepted File Formats.
4. Before You Upload: Checklist
- Orthomosaic is a GeoTIFF with an embedded EPSG code
- GSD is within 0.01–0.25 ft (below 0.05 ft for survey-grade)
- Point cloud (if needed) is
.las/.laz, meets density, and matches the ortho's coordinate system - Vertical datum and units are documented
- GCP/checkpoint report is included, if control was used
- Imagery fully covers the project boundary
- Files follow File Naming Conventions and File Size Limits
5. Planning a New Drone Capture (?)
If your site hasn't been flown yet, loop AirWorks in before the flight. Send us your boundary and the features you need extracted (edge of pavement, striping, utilities, etc.), and we'll confirm the specs your drone provider should fly to so the capture works for extraction the first time.
If you don't have a drone provider, see Imagery & Data Sourcing for other ways to get data for your site.
6. Common Issues
-
Raw photos instead of an orthomosaic: individual drone images can't be processed. Ask your provider for the stitched, georeferenced orthomosaic.
-
No coordinate system: files exported without an EPSG code can't be placed correctly.
-
Mismatched coordinate systems: the orthomosaic and point cloud must use the same CRS.
-
Unknown vertical datum or units: elevations can end up offset or in the wrong units.
-
Incomplete coverage: gaps at the edge of the boundary mean gaps in your deliverable.
Questions? Contact your AirWorks account manager or support@airworks.io.