Mapping mission planner
Area, overlap and altitude decide everything else: line spacing, image count, airborne minutes and pack count. This does the whole chain.
Researched from published specifications and verified owner reviews · updated 2026
The short answer
At 100 m altitude with 75 percent front and 65 percent side overlap, a typical 1-inch sensor prosumer drone covers roughly 25 to 40 acres per 20 minute usable battery at about 2.7 cm per pixel. Halving the altitude halves the ground sample distance and roughly quarters the area one battery can cover.
A mapping flight is the one kind of drone work where guessing is expensive in a very specific way: you find out the mission was wrong after you have flown it, when the processing finishes and the model has holes, or the resolution is not good enough for what the client asked. The inputs are all knowable beforehand, which makes this the single most useful calculation on the site for anyone doing commercial work.
Enter the site area, the camera, the altitude and the overlap, and the planner returns ground sample distance, the footprint of a single frame, flight line spacing, the number of images, the airborne time and the battery count. Then check the resolution it gives you against what the deliverable actually needs before you drive anywhere.
Coverage and overlap
Mapping mission plan
Sensor width and focal length are physical camera properties, printed in the aircraft's specifications. The presets below cover the common camera drone sensors.
Planning estimates only. Turn overhead, wind, terrain following and the mission planner's own behaviour will move the airborne figure, usually upward. Commercial mapping requires a Part 107 certificate, a registered aircraft, Remote ID compliance, and an airspace authorization before launch in controlled airspace. Verify current requirements with the FAA.
What ground sample distance actually means
Ground sample distance is the real-world size of one pixel on the ground. A GSD of 2 cm/px means each pixel in your imagery covers a 2 cm square of the world, so the smallest feature you can hope to identify is a few pixels across, which is something like 6 to 10 cm. Everything about mapping resolution reduces to this number, and it is set entirely by the camera and the altitude.
The relationship is linear with altitude, which has a pleasant consequence and an unpleasant one. The pleasant one: halving altitude halves GSD, so resolution doubles. The unpleasant one: halving altitude also quarters the area each frame covers, so you fly roughly four times as long for the same site. Resolution is expensive in battery terms, and the discipline is to fly at the highest altitude that still delivers the GSD the deliverable requires, not the lowest altitude you can get away with.
| Deliverable | Target GSD | Typical altitude, 4/3 sensor 24 mm equivalent |
|---|---|---|
| Progress photography, visual site record | 4 to 6 cm/px | 120 m |
| Orthomosaic for planning and area takeoff | 2.5 to 4 cm/px | 80 to 120 m |
| Stockpile volumes | 2 to 3 cm/px | 70 to 100 m |
| Topographic surface for design | 1.5 to 2.5 cm/px | 50 to 80 m |
| Pavement condition, crack detection | 0.5 to 1 cm/px | 20 to 35 m |
| Roof condition, shingle-level detail | 0.3 to 0.6 cm/px | 12 to 25 m |
Full altitude and GSD pairings for the common sensors are tabulated on the GSD and altitude chart, and the calculation on its own lives at the ground sample distance calculator.
Choosing overlap
Overlap exists so the photogrammetry software can find the same physical feature in many images and triangulate its position. Front overlap is along the flight line and is cheap, since it costs only shutter frequency. Side overlap is between lines and is expensive, because raising it means flying more lines over the same ground.
Seventy five front and sixty five side is the general-purpose setting. Raise both for anything with weak or repetitive texture, because that is where matching fails: dense vegetation, water, fresh snow, sand, and large uniform roofs all defeat feature detection at low overlap. Lower them only over well-textured flat ground where you have processed a similar site before and know it reconstructs cleanly.
One trap worth naming: tall structures need more overlap than the ground around them, because a building 20 m high at 80 m altitude is effectively being photographed from 60 m, where the frame footprint is smaller and the effective overlap on the roof is lower than what you set. On sites with significant vertical relief, either raise overlap or use a terrain-following mission if your aircraft supports it.
Nadir is not enough for vertical surfaces
A straight-down mission produces a good orthomosaic and a poor building. Vertical faces are barely visible from directly above, so they reconstruct as smeared texture stretched down from the roof edge. The fix is a second pass with the gimbal at 60 to 70 degrees rather than 90, flown either as a cross-hatch at right angles to the first grid or as one or more orbits around the structure.
Budget for it. An oblique pass typically adds 40 to 60 percent to the airborne time of the nadir mission, which means a pack you had not planned for. The full sequence from capture to deliverable is written up in the photogrammetry workflow guide, and the mission planning conventions in how to plan a mapping mission.
Ground control and accuracy claims
Photogrammetry gives you excellent relative geometry almost for free. Absolute position is a different claim, and it is the one that needs evidence. A model built from aircraft GPS alone typically sits within a few metres horizontally and considerably worse vertically, which is fine for a visual and useless for anything a surveyor signs.
There are two ways to fix it. Surveyed ground control points, such as a set of Ground control point targets (10 pack) ($70), placed and measured with survey-grade equipment and distributed around and through the site, five as a practical minimum on a small job. Or onboard RTK, which timestamps each image against a corrected position, as on the Autel EVO II Pro RTK V3 ($2,999). RTK is faster in the field and still benefits from a few checkpoints, because a checkpoint is how you prove the accuracy rather than assert it.
Cards, storage and the mission that will not fit
A 100 acre mission at 3 cm/px generates something like 900 to 1,400 images, which is comfortably over 40 GB shooting JPEG plus raw. Running out of card space mid-mission means re-flying lines, so size the card for the whole job. A SanDisk Extreme 512 GB microSD ($140) handles a full survey day, and a SanDisk 1 TB portable SSD (USB-C) ($166) in the car means the day exists in two places before you drive home. Cards are compared in best microSD cards for drones and offload options in storage for drone footage.
For the aircraft itself, the mapping-capable options and what actually separates them are in best drones for mapping and surveying, and the complete commercial kit at a stated total is the commercial mapping build.
Questions people ask
+ What overlap should I use for photogrammetry?
Seventy five percent front overlap and sixty five percent side overlap is the safe general setting for a nadir mapping mission over mixed terrain. Push front overlap to eighty and side to seventy for vegetation, water, snow, sand or anything else with repetitive or low texture, because the matching algorithm needs distinct features to tie images together. Flat, well textured ground such as a parking lot tolerates seventy and sixty.
+ How is ground sample distance calculated?
Ground sample distance equals sensor width in millimetres, multiplied by flight altitude in metres, multiplied by one hundred, divided by the product of focal length in millimetres and image width in pixels. The result is centimetres per pixel. In practice it is linear with altitude, so doubling your altitude doubles your GSD and halves your resolution while quartering the number of images needed.
+ How many acres can one battery cover?
For a typical prosumer camera drone at 100 m altitude with 75 and 65 percent overlap, one 20 minute usable pack covers roughly 25 to 40 acres depending on ground speed and turn overhead. At 60 m altitude, where GSD is better, the same pack covers roughly 10 to 15 acres. Altitude is the strongest single lever on coverage, and it trades directly against resolution.
+ Do I need ground control points?
You need them whenever the deliverable makes a claim about accuracy. Without surveyed ground control, a photogrammetry model has excellent relative geometry and unverified absolute position, which is fine for a visual or a volume comparison against itself and not fine for a boundary, a design surface or anything a surveyor will sign. Five well distributed targets is the usual minimum for a small site.
+ Why does the flight take longer than the calculator says?
Turn overhead is the usual culprit. At the end of every flight line the aircraft decelerates, turns and accelerates again, which on a small site with short lines can add thirty percent to the total. Long lines along the site's longest axis reduce the number of turns and are almost always the faster orientation, even when the mission planner defaults to the other one.
+ Is a nadir-only mission enough?
For a flat site producing an orthomosaic, yes. For anything with vertical structure, no. Buildings, stockpiles, walls and towers reconstruct poorly from straight-down imagery alone because the vertical faces are barely visible. Add a second pass with the camera at 60 to 70 degrees, ideally flown as an orbit or a cross-hatch, and the model quality on vertical surfaces improves dramatically.
