The legacy Aerotas site described demo files as a way to inspect deliverables firsthand, especially for packages such as Full Linework, Clean Topo/TIN Surface, and Photogrammetry Only. That remains the right framing. Buyers learn fastest when they can open the files and see how the outputs fit their own workflows.
What good demo files should include
- A drafted CAD example that shows layer organization and feature clarity
- An orthophoto or image deliverable that shows visual quality and context
- A sample surface or point-cloud handoff where relevant
- Enough explanation to tie the files back to the underlying product scope
Current access path
The current site still references demo-file download routes from other pages, but the dedicated public route has not yet been rebuilt in this repo. For now, this resource page serves as the explanation layer while the exact download flow is being re-established.
Need sample deliverables now?
If you want to review example files before requesting a project, contact Aerotas and specify which deliverable package you want to inspect.
The backlog now tracks the remaining step: restoring a dedicated demo-file route or authenticated delivery path so the CTA is no longer just explanatory.