◆ Platform Overview
The complete drone data
processing pipeline
From processed capture to professional deliverable — the same QGIS/GDAL deliverables engine AeroLakeland has run on real commercial projects, now wrapped in a self-serve platform.
◆ Architecture
Four-layer processing architecture
Each layer runs the same order every time — a real, repeatable pipeline, not a black box.
Ingest Layer
Accepts DJI Terra, Pix4D, Metashape, and WebODM exports (DJI Terra is the most-tested path). File-type and plan-limit checks on upload; coordinate-reference validation before processing.
Deliverables Engine
QGIS/GDAL pipeline that turns your already-processed orthomosaic, DSM/DEM, point cloud, and 3D mesh into georeferenced KMZ, web-tiled overlays, and a branded PDF report. Upload raw flight photos instead and a containerized OpenDroneMap stage reconstructs them first, then hands off to the same pipeline.
Automated QA
Tileset health checks and elevation cross-validation run on every job before results reach your portal.
Deliverables Portal
Download files directly or share a revocable, expiring link with a client — no account required on their end.
◆ Technical Specs
Built for professional accuracy
Results depend on capture method, overlap, and whether ground control points or RTK/PPK were used — these figures reflect real project output, not a lab benchmark.
◆ Security & Access
Isolation at every layer
Data Encryption
TLS in transit. Files move via short-lived presigned URLs, never through a shared endpoint.
Isolated Tenancy
Per-account data scoping enforced at the database level on every request.
Role-Based Access
Owner, admin, and read-only roles enforced server-side, with every project scoped to its own account.
Controlled Sharing
Client links are revocable and can expire by date or view count.
◆ Vertical accuracy
Every elevation, labelled with what it actually is
Ellipsoidal and orthometric heights differ by roughly 90 feet in Florida. Software that reports the datum you requested rather than the one your export actually carried will happily show you 90 feet of progress that never happened.
Measured on every run
DroneFlow probes the vertical datum of every export it processes — not the setting you chose, the reference the data arrived on — and carries that verdict onto the project page, the comparison view, the cut/fill report and the AI assistant.
Mismatches are named, not averaged
If two flights sit on different references, the comparison says so rather than calling the difference progress. Upload surveyed checkpoints and it goes further: it tells you whether the error it measured is explained by the datum, or whether the problem is elsewhere.
An accuracy certificate
One page stating the delivered datum, the horizontal reference, the automated checks that ran, and — when you have supplied checkpoints — the measured error against them. It names what it does not verify, and it never grades the data. Whether the numbers meet your tolerance is your call.
Above-sea-level heights are not a North-America-only feature. Choose your vertical datum at upload — NAVD88 (GEOID18) for work specified against the US datum, or EGM2008 anywhere in the world. DroneFlow measures which datums actually resolve at your coordinates rather than assuming a region, and shows the offset each one applies at your site.
◆ Works With Your Tools
Export formats your team already uses
No proprietary lock-in — every deliverable exports to a format that opens directly in the software you already run.
QGIS / ArcGIS
GeoTIFF, Shapefile-compatible exports
Google Earth
KMZ / KML with layer toggles
Point Cloud Viewers
LAS / LAZ dense point clouds
CAD Software
DXF contour and boundary exports