One of the most common questions we hear before a first flight is not about price or scheduling. It is about the files themselves: what will actually land in the client’s inbox when the job is done, and will it open in the software the project team already uses? The question matters more than it sounds like it should. A drone flight can generate an impressive amount of raw data, but if the finished deliverable does not match a client’s workflow, that data is a folder nobody can use.
Industry guidance on this is consistent: the right format depends entirely on what the client’s own software supports, and that needs to be settled during scoping, not after processing. A piece on drone delivery standards from Barnard HQ makes this point directly, noting that clarifying file compatibility upfront prevents a common failure mode — a finished dataset that arrives in a format the receiving engineer, architect, or GIS team simply cannot open. Here is a plain-language walk-through of the main deliverable types, so the terminology makes sense before that scoping conversation happens.
What is an orthomosaic, and how is it different from a photo?
A single aerial photo has perspective distortion — objects near the edges of the frame are stretched relative to how they would measure on the ground. An orthomosaic corrects for that. It is a composite image built from hundreds of overlapping photos, geometrically adjusted so scale is consistent across the entire frame. As Propeller Aero’s breakdown of drone survey outputs explains, an orthomosaic functions as a 2D map you can measure directly from — distances, areas, and positions — rather than a picture you can only look at. Orthomosaics are typically delivered as full-resolution GeoTIFF files, which carry embedded georeferencing information so they load correctly into GIS or CAD software at true scale.
What is a point cloud, and who actually uses one?
A point cloud is a dense collection of individually positioned points that together recreate the shape of a site in three dimensions. Photogrammetric point clouds built from drone imagery typically place points roughly 3 centimeters apart, which is enough resolution to measure elevation, depth, and spatial relationships across a site. These are generally delivered as LAS or LAZ files, the standard formats for point cloud data, so they can be imported into third-party survey, civil, or BIM software. Point clouds are the foundation that other deliverables, like elevation models and 3D meshes, are built from.
What is a DTM or DSM, and why does the distinction matter?
Digital Surface Models and Digital Terrain Models are both elevation datasets, but they are not interchangeable. A Digital Surface Model captures every surface the drone can see, including rooftops, vegetation, and stockpiles. A Digital Terrain Model filters those features out to represent bare-earth ground elevation. Per Propeller Aero’s overview, DTMs are what support grading analysis, drainage planning, and cut-and-fill calculations, since those calculations need actual ground elevation rather than the top of whatever is sitting on it. Both are typically delivered as GeoTIFF raster files with the coordinate system and georeferencing built in.
What is a 3D model, and what can I do with it?
A textured 3D model combines the site’s imagery with its positional data into a mesh — commonly built from a few hundred thousand individual mesh faces layered with texture. These models support volume measurements for stockpiles, haul road analysis, and cut-and-fill review, and are often exported as DXF files so they open directly in AutoCAD or comparable design software.
So what will I actually receive?
For most active construction sites, a standard progress or mapping flight delivers some combination of a GeoTIFF orthomosaic, a LAS/LAZ point cloud, and a PDF or web-based summary report for quick review without specialized software. Projects that need elevation analysis add a DTM or DSM; projects tracking volumes or built conditions in 3D add a textured model. Dragonfly Aerials scopes this during intake, asking what software your team already runs — Civil 3D, ArcGIS, QGIS, Bluebeam, or something else — so the files we deliver open on the first try rather than requiring a format conversion after the fact.
On accuracy: our flights and processing workflows are built to produce sub-centimeter-per-pixel imagery, delivering sub-cm-level work that is ready for engineering review. If your project requires a licensed survey stamp, that remains a distinct deliverable from a licensed surveyor, and we are glad to coordinate around it rather than blur the line.
All of this happens within the operating rules the FAA sets for commercial drone work. Under 14 CFR Part 107, flights are conducted by a certified remote pilot, within visual line of sight, and within the altitude and airspace limits the rule defines — the same framework that governs every flight Dragonfly Aerials conducts across the Front Range.
For a walk-through of how a flight moves from scheduling to finished deliverable, see our How It Works page. If you are comparing services for an upcoming project, see our full service list. Ready to talk through what your team’s software needs are? Get a quote now.
Sources:
https://www.propelleraero.com/blog/dissecting-the-data-outputs-of-drone-surveys/