Mission planning
The mission planner generates routes for the drone fleet in two modes: SAR with separation (searching an area with several drones at once) and General (photogrammetry with a single drone). Plus two presets shared across the organisation - they remember the last parameters used.
The flow
- Area - drawn on the map (polygon or rectangle) or loaded straight from the operations map, e.g. one drawn during an incident (it is a copy: later changes on the operations map do not affect the plan). A finished area can be adjusted with the “Edit area” button - every change discards the generated routes.
- Calculate the plan - the system shows, per drone: ceiling, GSD, line spacing, distance, time and battery margin.
- Generate missions - the routes go through terrain validation, with a violation report.
- Save to cloud → incident name or Download ZIP - missions saved to the cloud go into the organisation’s active incident, and the pilot picks them up straight from the DJI Pilot 2 route library on the controller.
No file transfers: the pilot opens the route library on the controller and the mission is already there, with a “downloaded” status visible in the system.
The fleet in SAR mode
- The SAR tab fills in the organisation’s drones that are currently sending telemetry, with their model and fleet name. When none is transmitting, the fleet is added with ”+ From fleet” (paired drones, online and offline) or ”+ From catalogue” (any model).
- Missions for fleet drones are named after the drone, e.g.
Las-Kabacki-0712-sokol1-matrice4t-80m- the pilot sees right away in the route library which mission is theirs. - Carrier platforms (Matrice 300/350/400) get a “Check camera” mark because telemetry does not say which payload is mounted - the operator picks the camera.
- The fleet sensor is one for all drones: IR or Wide. A drone without a thermal camera (e.g. Matrice 4E, Mavic 3E) switches the fleet to Wide; a mixed fleet is rejected, because thermal and RGB GSD are not comparable.
- The GSD of the RGB cameras in the Mavic 3T, Matrice 4T/4TD and Zenmuse H30T is calculated for the native 12 MP resolution, not the 48 MP mode.
Cloud missions
The planner panel shows the three newest missions; the “Show all” button opens the full mission library of the organisation: tile or list view, sorting (newest, oldest, drone model, awaiting download first), a filter by name or drone model and an operation-type tag (SAR, PHOTO, preset name). Every mission shows whether the controller has already downloaded it. Pilots can view the library and download missions; only the operator can delete them.
The list shows the missions of the active incident; a mission can be moved to another incident with the “Move…” button - see “Incidents”.
The parameters that matter
- You set the altitude as a ceiling (m AGL) or a target GSD (cm/px) - the other value is calculated for you.
- Terrain following keeps a constant height above ground based on a 1 m elevation model. It works over Poland; the model describes bare ground.
- Speed is calculated from the photo parameters and platform limits - it can only be lowered.
- Flights above 120 m AGL are clipped: a drone that would need a higher ceiling gets a “clipped to 120 m” note and a “Deliberately allow >120 m” checkbox. Once ticked and the plan recalculated, the drone flies higher with an “above 120 m (override)” note, and the operator’s consent is recorded in the report.