The final Aerotas handoff is built around usable project files, not just screenshots or visual previews. Depending on the product, a customer may receive drafted CAD files, raster imagery, surfaces, point clouds, and supporting production data that help validate or extend the work.
Common final outputs
- DWG or DXF. Drafted linework and surface content intended for CAD use.
- GeoTIFF orthophotos. Spatially referenced imagery suitable for GIS or CAD context.
- Surface files and contours. Clean topographic models built for practical design and review workflows.
- Point clouds. Dense 3D data, often delivered for users who need deeper analytical access.
- Specialized corridor files. Products such as power-line work may include package-specific exports.
Why multiple file types are useful
Different consumers of the deliverable need different things. Drafting teams often want clean vector output. GIS users may care most about georeferenced rasters. Technical reviewers may need intermediate files or point clouds for their own checks. A good deliverable package supports those different use cases without forcing everyone into the same tool.
Rule of thumb: smaller, cleaned, drafted files are usually easier for day-to-day production use than raw dense data, even when the raw data is also made available.
Coordinate systems and compatibility
Coordinate system handling should be confirmed up front, especially for customers working in custom or local systems. Aerotas Atlas guidance on the site already notes support for standard state-plane workflows as well as customer-provided control when a project needs a different coordinate framework.