Processed before the huddle.
Upload starts on the pad, before the props stop turning. Maps, surfaces, volumes and panoramas are processed and differenced against the previous pass 40 min after capture — while the huddle is still pouring coffee.
What it does
Transfer begins the moment the aircraft is back on the cradle or the robot is back on its dock — over the site link where there is one, over LTE where there is not, resuming chunk by chunk when the link drops. Nobody carries a card into the trailer.
Processing then runs without anyone asking for it: orthomosaic, surface and volumes for a flight; aligned, drawing-pinned panoramas for a walk. Each output is differenced against the previous pass, so what lands is not another dataset but a change — 2,400 m³ moved, Level 6 closed up, stockpile 3 down 11%.
How it works
- 01
Upload on landing
Transfer starts on the pad and resumes by chunk if the link drops. A 214 ha flight moves in about 12 min on site LTE, and nothing waits for a drive into the office.
- 02
Process without a ticket
Every capture runs its full chain automatically — ortho, surface, volumes, panorama alignment — at the same settings as last week, so this week's result is comparable rather than merely newer.
- 03
Difference against the last pass
Outputs are compared with the previous capture and published as change: quantities moved, areas closed, deltas flagged. Capture to record runs 40 min end to end, unattended.
Spec
- CAPTURE→RECORD
- 40 MIN
- UPLOAD
- STARTS ON LANDING · RESUMABLE
- LINK
- SITE WI-FI OR LTE
- OUTPUTS
- ORTHO · SURFACE · VOLUME · 360
40 min
Capture to record, unattended