Drone Mapping File Formats Explained
A practical guide to choosing drone mapping deliverables for survey, design, construction, GIS and asset teams.
By SkyViews Aerial Drone Studio
Drone mapping projects can produce several file types, and a technically impressive folder is not automatically a useful one. The right deliverables depend on the decision the client needs to make, the coordinate reference system, the required accuracy and the software used by the receiving team.
Aligning File Formats with Decision Objectives
Start with the decision
Ask whether the output is for visual measurement, earthwork quantity, design coordination, asset inventory, planning, inspection evidence or public presentation. A web viewer may be useful for review, while an engineering team may need georeferenced raster, point cloud, CAD or GIS layers.
Common deliverables
An orthomosaic is a corrected, map-like image assembled from overlapping photographs. A DSM represents visible surfaces such as roofs, trees and stockpiles. A DTM is intended to represent bare-earth terrain where the processing method and ground classification support that use. Contours are derived lines at a chosen interval, not a substitute for explaining source data and accuracy.
Point clouds are commonly delivered as LAS or LAZ. Meshes may be supplied as OBJ or another 3D format. CAD and GIS outputs can include DXF, SHP, GeoPackage, GeoTIFF or CSV depending on the workflow. Confirm the target application before processing because conversions can lose attributes, coordinate information or classification.
Specify reference and accuracy
The brief should name the horizontal and vertical datum, projection or EPSG code, units, ground-control approach, check points, expected ground sampling distance and reporting method. “Centimetre accurate” is incomplete without saying how accuracy will be tested and which surfaces are being measured.
Construction Handover & Delivery Checklist
Build a useful handover
Request a short read-me file, layer naming convention, coordinate reference information, capture date, processing assumptions, exclusions, control report and known limitations. A clean handover lets surveyors, architects and project managers use the same source without guessing.
First decide who will open the files
Ask the receiving team which program and version it uses, what it will do with the data and whether it needs measurements or only a visual reference. A project manager may be happy with a web view and a PDF. A GIS analyst may need a georeferenced raster and editable vector layers. A design team may need a surface or point cloud that opens in its existing CAD workflow. The handover should be chosen for the user, not for the longest list of export options.
Write a one-line purpose beside each requested file. For example: “GeoTIFF orthomosaic for site context in GIS,” “classified point cloud for terrain review,” and “PDF overview for management.” This prevents the common problem of receiving several large files with no explanation of which one is authoritative.
Core Photogrammetry & Spatial Data Deliverables
Read an orthomosaic correctly
An orthomosaic joins overlapping images and corrects them so they can be viewed like a map. It is useful for roads, roofs, stockpiles, land cover and the visible layout of a site. It is not a live image, a legal boundary survey or proof that every pixel has the same positional accuracy. Tall objects can lean or show stitching effects if capture and processing are not suitable.
For technical use, ask for a GeoTIFF and its coordinate reference information. The OGC GeoTIFF standard describes how georeferenced raster information is encoded. A plain JPEG may look identical on screen but may not carry the location information the receiving system needs. Test alignment against known points or an approved base map. A pretty overlay in a web viewer is not an accuracy report.
If the image will be published, make a separate compressed version. The full mapping raster can be too large for a website, while a small web image may be too coarse for measurement. Keep the technical master and the public graphic clearly named.
Know what a DSM and DTM can show
A digital surface model, or DSM, describes the top visible surface reconstructed by the method. Trees, roofs, vehicles and piles may appear as height. A digital terrain model, or DTM, aims to describe ground after suitable classification or modelling. Drone photographs do not see through a dense tree canopy. A file labelled DTM is not automatically a reliable bare-earth model in every place.
Ask the provider how ground was identified, where it was hidden, and what checks support the output. If a civil engineer needs grades beneath vegetation or inside a structure, plan additional ground observations or a different sensor. For stockpile work, define the base surface and boundary used to calculate the volume. A small change in the chosen base can change the reported quantity.
Contours are lines derived from a surface. Their interval should suit the terrain and the accuracy of the source. Closely spaced contour lines do not create extra accuracy. Include the underlying surface and a method note when contours will influence design or earthwork decisions.
Understand a point cloud before importing it
A point cloud contains many three-dimensional points. LAS is a common exchange format; LAZ is a compressed form often used to reduce file size. Ask whether points have colour, classification, intensity or other attributes needed by the receiving workflow. A dense cloud from photographs can cover visible features but may leave holes in water, vegetation or shadow. A laser-derived cloud has its own visibility and registration limits.
Before delivery, agree whether the client wants all points or a thinner working copy. Large files can overwhelm a laptop or design application. Request a small sample and test it in the actual software. Check that units, height reference and location remain correct after import. A model displaced by hundreds of metres can still look internally consistent in a viewer.
For BIM or design coordination, ask which parts should become a model rather than expecting a point cloud to behave like finished CAD objects. Turning points into walls, pipes or surfaces is a separate interpretation task and should be priced and checked separately.
Choose CAD and GIS exports deliberately
DXF can carry lines, points and other CAD geometry, but the receiving program may need a particular layer structure, units and coordinate note. A drawing that looks right at its own origin may not align with the site grid. SHP is widely recognised but involves several companion files and has data-field limits. GeoPackage can hold multiple GIS layers in one file. CSV is useful for simple tabular point lists when column names and coordinates are explained.
Give the provider a sample of the client's expected template. Name the required layers, fields, units, line types and feature IDs. Test a small export before processing the whole site. Confirm whether labels and attributes survive conversion. If a format cannot carry something essential, request a second file and a clear cross-reference rather than silently dropping the information.
Make coordinates visible in the read-me
A coordinate reference system tells software how file numbers relate to real locations. Record the projection or EPSG identifier where applicable, the horizontal and vertical datums, units and any local grid transformation. If the project uses a site-specific benchmark, name it and explain the relationship to other data. Do not leave a reviewer to infer metres versus feet or ellipsoidal versus local heights from a screenshot.
Ask how ground control and independent check points were used. A receiver should be able to distinguish the points that helped fit the model from points that tested it. The ASPRS accuracy standards provide an industry reference for reporting geospatial accuracy; the project specification must say which tests apply. Ground sampling distance, or pixel size, is not itself a full accuracy result.
Example: a construction handover
Imagine a contractor asking for a monthly site record. The project manager wants a PDF overview and a dated web image. The engineer wants a GeoTIFF orthomosaic, a checked surface and a small set of cross-sections. The quantity surveyor wants a stockpile boundary, base assumption and volume report. One flight may support several of these outputs, but each needs its own acceptance check. The file list should say which team owns that check.
For the first month, send a sample folder. The engineer opens the raster in the project coordinate system and checks independent points. The quantity surveyor reviews the stockpile base before accepting the volume. The project manager checks date and captions on the overview. The same names and boundaries are then used for later months so comparisons are possible.
A simple delivery checklist
Start with a read-me that lists every file and purpose. Include capture date, area, coordinate system, units, method and version. Put raw or source files in a separate folder if the contract includes them. Open a sample of each delivered format in the receiving software, and confirm that the files align with the client's base data. Note missing areas, low-confidence surfaces and restrictions on use. Finally, keep one approved copy so later edits cannot silently replace the accepted record.
If the project needs only presentation graphics, do not order a complex geospatial package without a user. If it needs engineering measurements, do not accept only a flattened image. The useful format is the one that lets the responsible team answer the project question and verify the result.
See the RTK/PPK and GCP guide and as-built survey guide.
Plan your project
Share your site, dates and intended output so we can confirm a suitable scope.
Drone Survey & Mapping · Compare project scope · Get in touch
Related reading
- Agriculture Drone Mapping for Farms and Estates in Karnataka: Practical Guide
- Archaeological Excavation Drone Mapping in India: Documentation Guide
- Drone Client Approval Checklist: Review Video, Photos and Mapping Before Release
- Drone Inspection for Sewer and Utility Corridors in India: Planning Guide
- Drone Inspection for Substations and Electrical Assets in India
- DJI Mavic 3 Enterprise Mapping in India: Accuracy Starts on the Ground
Contact SkyViews Aerial Drone Studio at +91 90190 56479 or skyviewsdronestudio@gmail.com. Service area: Bangalore, Karnataka and India and wider Bangalore, Karnataka and India.