Survey grid (lawnmower pattern)
A serpentine mapping pattern over an area, with no-fly holes routed around, the fewest lines by default, overshoot, and an optional crosshatch: waypoints, line count, path length, turns, photo count, and flight time.
Planning and education aid. Not for primary navigation. Full disclaimer
A published result changed on 2026-09-23: Image count and the survey grid (version 1.1.0) now count the way published flight planning does (Penn State GEOG 892): ⌈width / spacing⌉ + 1 lines… Changelog
Fly 4 lines for 3.02 km and about 104 photos. That takes about 5 min.
| Latitude | Longitude | Kind | Height |
|---|---|---|---|
| 39.9999657 deg | -105.0006714 deg | line_start | 120.0 m |
| 39.9999657 deg | -104.9922786 deg | line_end | 120.0 m |
| 40.0004386 deg | -104.9922786 deg | line_start | 120.0 m |
| 40.0004386 deg | -105.0006714 deg | line_end | 120.0 m |
| 40.0009114 deg | -105.0006714 deg | line_start | 120.0 m |
| 40.0009114 deg | -104.9922786 deg | line_end | 120.0 m |
| 40.0013842 deg | -104.9922786 deg | line_start | 120.0 m |
| 40.0013842 deg | -105.0006714 deg | line_end | 120.0 m |
| Latitude | Longitude | Kind | Height |
|---|---|---|---|
| 39.9999657 deg | -105.0006714 deg | line_start | 120.0 m |
| 39.9999657 deg | -104.9922786 deg | line_end | 120.0 m |
| 40.0004386 deg | -104.9922786 deg | line_start | 120.0 m |
| 40.0004386 deg | -105.0006714 deg | line_end | 120.0 m |
| 40.0009114 deg | -105.0006714 deg | line_start | 120.0 m |
| 40.0009114 deg | -104.9922786 deg | line_end | 120.0 m |
| 40.0013842 deg | -104.9922786 deg | line_start | 120.0 m |
| 40.0013842 deg | -105.0006714 deg | line_end | 120.0 m |
| Latitude | Longitude | Kind | Height |
|---|---|---|---|
| 40.0013842 deg | -105.0006714 deg | line_end | 120.0 m |
- Photos
- Path length
- Line length over the area
- Turns
- Flight time
- Line direction
Provenance
- Computed by
- drone.mission.survey-grid 1.3.0, core 0.1.0
- Model
- Lines swept on a local transverse Mercator plane, ⌈width / spacing⌉ + 1 of them centered so the outer lines reach the edges (Penn State GEOG 892), each covering its strip of the area and cut at buffered holes, joined in serpentine order; ⌈length / photo spacing⌉ + 1 photos per line plus the extras past each end; transits that would cross a hole follow its buffered boundary
- Accuracy
- Line spacing is true to within 1e-7 across a few kilometers (checked geodesically). Flight time ignores turns, climbs, and wind.
- Notes
- None
- Cites
- Abdullah, Q., Penn State College of Earth and Mineral Sciences, GEOG 892: Geospatial Applications of Unmanned Aerial Systems; Wolf, P. R., Dewitt, B. A., and Wilkinson, B. E., McGraw-Hill, Elements of Photogrammetry with Applications in GIS; Karney, C. F. F., Journal of Geodesy, Algorithms for geodesics
Something look off?
How we got thisFormula, worked example, sources, and proof
Model: Lines swept on a local transverse Mercator plane, ⌈width / spacing⌉ + 1 of them centered so the outer lines reach the edges (Penn State GEOG 892), each covering its strip of the area and cut at buffered holes, joined in serpentine order; ⌈length / photo spacing⌉ + 1 photos per line plus the extras past each end; transits that would cross a hole follow its buffered boundary
Accuracy: Line spacing is true to within 1e-7 across a few kilometers (checked geodesically). Flight time ignores turns, climbs, and wind.
When to use this: Use this to lay out a mapping flight over an area: parallel lines at your spacing, joined end to end, with photo points along them, routed around no-fly holes, and optionally crossed by a second set for a crosshatch. It gives the waypoints to load and the line count, path length, turns, photos, and flight time to plan batteries around. Add the camera’s ground footprint to see each photo on the map, darker where photos overlap, with the forward and side overlap the spacing gives.
Limitations: Lines are laid on a local plane, which is exact enough for a survey block but not for one hundreds of kilometers across. The pattern assumes flat ground and a constant height: over hills the overlap and ground sample distance change along each line. Turns are drawn as corners, so the path length and time leave out how the aircraft actually turns and accelerates.
Worked example: A 602 m by 150 m field at 52.5 m line spacing. Source: add-drone-suite survey-grid scenario: lines run along the long axis, ⌈150 / 52.5⌉ + 1 = 4 lines. It is golden test vector v029, and every build checks the tool still gives its answer within its tolerance.
You enter
- Area
- 40, -105 40, -104.99295 40.00135, -104.99295 40.00135, -105
- Groundspeed
- 10 m/s
- Height above ground
- 120 m
- Line spacing
- 52.5 m
- Photo spacing
- 30 m
You get
- Flight lines
- 4
- Photos
- 104
- Path length
- 3.02 km
- Line length over the area
- 2.41 km
- Turns
- 6
- Flight time
- 5 min
- Line direction
- 90°
- Height
- 120 m above ground level (constant) at every waypoint
- Mission time
- 302.4 s
- Scene time
- 302.4 s
- Photos captured
- 104
Review: Not yet independently reviewed by a Part 107 remote pilot.
Last verified: 2026-09-18, when a maintainer last confirmed this tool's sources at the issuer. See the sources ledger.
Status: version 1.3.0, core 0.1.0. See this tool in the verification report.
Changes
- 2026-10-12, changed: The survey-grid tool now plays the mission at the entered groundspeed. The core returns the playhead, flown path, aircraft position, and the photo triggers and footprints captured so far; the map keeps the remaining plan visible and fills coverage as the aircraft advances. Scrubbed permalinks reopen paused. Planning answers are unchanged. Changelog
- 2026-10-09, added: Survey grids take the camera's ground footprint across and along the line, as the ground sample distance tool gives it. The map then draws every photo's footprint, darker where photos overlap, and the result gives the forward and side overlap the spacings make, with a warning when the photos leave gaps. Without a footprint nothing changes. Changelog
- 2026-10-07, changed: Survey grid waypoints now carry the flight height when one is given, so they can go straight into a mission export; the drone mapping workflow ends with a mission KML to download, and the VFR cross-country workflow offers its nav log as CSV. Existing results are unchanged. Changelog
- 2026-09-23, fixed: The worked example was titled a 600 m by 150 m field, but its corners are 602 m apart along the lines, which is why it gives 22 photos a line and 104 in all. The title now says 602 m by 150 m. No results change. Changelog
- 2026-09-23, result change: Image count and the survey grid (version 1.1.0) now count the way published flight planning does (Penn State GEOG 892): ⌈width / spacing⌉ + 1 lines with the outer lines on the edges, and ⌈length / photo spacing⌉ + 1 photos per line plus extra photos past each end, 2 by default (a new input; 0 leaves them out). Most areas gain a line. The Penn State block now gives its published 10 lines and 430 photos, where 1.0.0 gave 9 and 342. The superseded vectors pinned the old line counts. Changelog
Checked against: 26 golden test vectors (download the test vectors, each with its source and tolerance). See how results are checked and every source.
Constants this tool assumes
Values you do not enter, and where each comes from.
- Default extra photos before and after each flight line
2 photos per end— GEOG 892: Geospatial Applications of Unmanned Aerial Systems
Sources
- GEOG 892: Geospatial Applications of Unmanned Aerial Systems, Abdullah, Q., Penn State College of Earth and Mineral Sciences, online course text, retrieved 2026-09-23. Lesson 4, Designing a Flight Route (number of flight lines; number of images).
- Elements of Photogrammetry with Applications in GIS, Wolf, P. R., Dewitt, B. A., and Wilkinson, B. E., McGraw-Hill, 4th edition. Chapter 18 (flight planning: flight lines, photo spacing, number of photos). Read free.
- Algorithms for geodesics, Karney, C. F. F., Journal of Geodesy, Vol. 87, No. 1. pp. 43-55 (direct and inverse geodesic problems).
Learn the concept: Photo overlap and flight lines explained