Find the place — search on the map, or paste coordinates.
Paint what you want captured — brush over it in 3D.
A flight that clears the trees is proposed straight away. (Or tap its corners on the map.)
Pick the detail — from a quick look to several batteries.
Save, and Fly puts it on the controller.
Nothing to show in 3D yet.
Tap the map on what you want captured and the flight appears here —
or look at the ground first in the LiDAR survey.
Point
m
Advanced
Reads the national LiDAR under the whole flight and reports
the tallest thing standing there — trees, poles, a crane — whether or not anybody ever mapped it.
It never lowers your altitude, and it says so when a tile has not been built yet rather than
calling that flat ground. The first look at new ground takes a few minutes.
Opens the survey itself for the 500 m square in the
middle of the map — the ground, the buildings and the trees as the LiDAR saw them, with the
power lines over the top, in the service's own viewer. That page has nothing of ours in
front of it, so it is what you compare against when the survey view looks wrong. The first
look at a new square downloads it and takes minutes; after that it is instant. Nothing to
do with your plan, and it changes nothing.
Lowest altitude and ring count that fit one battery and DJI Fly's
200 waypoints. Runs by itself until you touch a control below.
Saving syncs to your other devices by itself.
Your plans and obstacles live under this key, and this
device made it up. Copy it into your other device to share one library; paste a different
one to move to that library, taking whatever is on this device with you. It is a name, not
a password — anyone who has it can read and write those lists.
1 Connect
Plug the controller in over USB.
2 Plan to install
3 Mission to overwrite
4 Install
No local server behind this page, so it cannot reach a
controller over USB. Serve it with npm start for that.
Before you fly: the camera settings this plan assumes
4:3, not 16:9. 16:9 crops the sensor, and every shot spacing here is
worked out from the full 4:3 frame — the same crop turns 75% front overlap into
about 67%.
12 MP, not 48/50. A 50 MP frame is roughly four times the card space and
its shutter cadence is unverified.
JPEG, not JPEG+RAW. RAW roughly triples the storage for images the
reconstruction does not read.
Single shot — no Timed Interval. Measured on the 28 Aug flight: a timed
interval kept firing through two hovers and 81 of 196 frames were duplicates of
each other. It is sticky across flights and overrides what the mission asks for.
Manual exposure and white balance, locked. A splat bakes the lighting, so
auto drifting across a long capture shows up as a colour gradient.
Return-to-home above everything.
Obstacle avoidance on, and know what it does: during a waypoint mission it
only brakes — it will not route around anything, and a brake ends the flight.
Getting the KMZ into DJI Fly by hand
In DJI Fly, create any throwaway waypoint mission so the app makes a mission folder.
Connect the RC and open Android/data/dji.go.v5/files/waypoint/.
Each mission is a folder named with a UUID containing one <same-UUID>.kmz.
Rename the exported file to that UUID and overwrite the one inside the folder.
Restart DJI Fly. The mission appears in the waypoint list.
On iOS the path is DJI Fly/wayline_mission/. DJI Fly caps a mission
at 200 waypoints — longer plans export as numbered parts to fly back to back.