Case Study #1 · Raw-photo reconstruction
547 raw drone photos in.
A full map set out, in 44.6 minutes.
No desktop photogrammetry software. The raw geotagged frames went up straight off a DJI RTK aircraft, and DroneFlow.Ai reconstructed the orthomosaic, elevation models, contours, point cloud and 3D model. Below: the output, the flight it came from, and what a flight like this can and cannot establish.
This is the same ground as Case Study #1, which starts from a processed DJI Terra export instead. Same flight, two pipelines.
200 nadir + 347 oblique, geotagged in-EXIF. Nothing else was supplied.
Upload to finished deliverable set, at the fast preset.
8,132,721 points, LAS 1.4 — read from the file header.
Each file was opened and parsed before this page was written.
The orthomosaic DroneFlow built from the raw frames
What was flown
| Aircraft / camera | DJI M4E · 20.9 MP (5280×3956) |
|---|---|
| Frames | 547 — 200 nadir + 347 oblique |
| Flight altitude | ~51 m AGL |
| Native GSD | ~1.3 cm/px |
| Positioning | DJI RTK, geotagged in-EXIF |
| Ground control / checkpoints | None on this flight |
What DroneFlow produced
| Orthomosaic | 11,109×7,396 px · 5 cm/px |
|---|---|
| DSM & DTM | 10 cm/px · 44.5 m relief |
| Contours | 7,615 lines · 1 ft interval |
| Point cloud | 8,132,721 pts · LAS 1.4 |
| 3D model | Textured mesh + 10,134 web tiles |
| Coordinate system | WGS84 / UTM 17N (EPSG:32617) |
What we measured — and what we didn't
Every deliverable above was opened and validated by the automated pipeline self-checks before this page was written. The two notes below are not caveats added afterwards: they are the boundary of what a single RTK flight with no surveyed control can establish at all.
- PASSAll 6 deliverable types produced from raw photos — orthomosaic, DSM, DEM, contours, point cloud and textured 3D model — and each file opened and parsed cleanly.
- PASSAll 547 frames georeferenced; the browser 3D tileset built 10,134 payload-sized tiles (median 14 KB), the size range that streams without stalling.
- NOTEAbsolute accuracy is anchored by the aircraft's onboard RTK positions (per-photo σ ~8 cm horizontal / ~15 cm vertical), not independently verified — this flight carried no surveyed ground control or checkpoints, so no residuals can be reported. For design or record work, add checkpoints and a licensed review.
- NOTEThis map was built at the fast processing preset. The point cloud (8.1 M points, 5 cm ortho) is intentionally lighter than a premium desktop engine would produce from the same frames — a deliberate speed/detail trade, tunable per project.
Accuracy depends on the aircraft, camera, altitude, flight geometry, image overlap and quality, RTK/PPK correction, ground control, checkpoints, terrain, vegetation, coordinate system, and processing configuration. Centimeter-level results may be achievable with appropriate RTK, PPK, surveyed ground control, checkpoints, and qualified validation. DroneFlow.Ai outputs do not constitute a licensed land survey unless reviewed and certified by an appropriately licensed professional.