CoordCalc

Drone GSD Calculator

This drone GSD calculator works out the ground sampling distance — the size on the ground of one image pixel — from the sensor, the lens and the height you fly. It also returns the ground footprint of a single photo and, in the other direction, the height you need to hit a target GSD. Enter the camera once and the height becomes the design variable. Free, in your browser, no login.

Sensor and focal length are the true values, not the 35 mm equivalent. Picking a camera sets all five camera fields; edit any of them and the selection drops to Custom. If your camera crops its sensor for the photo mode you fly, enter the cropped sensor width and the matching pixel count.

Check the camera — sensor, focal length and image pixels must all be positive, and the height or target GSD must be greater than zero.

Ground sampling distance —

Ground coverage of one photo

At this heightValue

The footprint must equal the image size in pixels multiplied by the GSD — the calculator checks that identity and reports it below.

How the calculation works

The single formula behind all of it

A pinhole camera projects the ground onto the sensor by simple proportion. One pixel subtends the same angle as one sensor pixel, so the size of that angle on the ground grows linearly with the distance to it:

GSD = H × S_w ÷ (f × W)

with H the height above ground, S_w the physical sensor width, f the focal length and W the image width in pixels. Height and sensor width must be in the same unit; because focal length and sensor width are both in millimetres and cancel dimensionally, the safest habit is to convert the height to millimetres as well. The result is millimetres per pixel — divide by 10 for the centimetres per pixel that everyone quotes.

The same proportion gives the ground footprint of one photo directly, without going through the GSD: footprint_width = H × S_w ÷ f and footprint_height = H × S_h ÷ f. The two routes must agree — footprint width divided by image width is exactly the GSD — and the calculator tests that identity on every recalculation, because a factor of ten slipping into either route is the most common way these numbers go wrong.

Solving for the height

Rearranged, H = GSD × f × W ÷ S_w. That is the form you actually use on a job: the deliverable fixes the GSD, so the height is what you compute and then program into the flight app. Because the relationship is linear, halving the GSD means halving the height — which is why going from 3 cm/px to 1.5 cm/px doubles the number of flight lines and roughly quadruples the photos.

What the GSD is used for

The GSD is the resolution limit of the whole product. A ground feature smaller than about two or three pixels cannot be identified reliably no matter how the images are processed, so a 3 cm/px survey will not produce a trustworthy 1:500 plan even though the orthomosaic looks sharp at screen zoom. The usual planning rule is one tenth of the contour interval: 1 cm/px for 0.1 m contours, 2 cm/px for 0.2 m. Photogrammetric specifications commonly ask for 1.5–2 cm/px for 1:500 and 3–5 cm/px for 1:1000.

Which height to enter

The formula wants the height above the ground directly under the camera, and nothing else. It is not the altitude above sea level and not the barometric altitude the app displays.

TerrainWhat to enterConsequence if you do not
Flat siteThe height you programme; take-off and ground are the sameNone — the simple case
Sloping site, fixed altitudeHeight above the highest ground, to stay legalGSD varies along the slope; the uphill part is coarser than you planned
Sloping site, terrain followingThe constant AGL height the aircraft holdsNone — the GSD is constant, which is the reason to fly this way
Site at 1500 m elevationHeight above ground, not the altitude readingEntering the altitude gives a GSD several times too large
Tall structures in the blockHeight above ground; note them separatelyTheir tops are much closer to the camera, so their GSD is finer and their parallax larger

On a slope, the GSD varies with the range to each point, not its elevation. A point 100 m uphill at the same range as a point downhill has the same GSD; what changes is the incidence angle at the surface, which stretches the apparent pixel along the slope. This is why steep terrain needs more overlap, not a different GSD.

Worked example

The default is a 4/3 sensor 13.2 × 8.8 mm, a focal length of 8.8 mm, images of 5472 × 3648 px and a height of 120 m. Every number below can be done on a calculator in under a minute.

Convert the height to millimetres: 120 m = 120 000 mm. Then GSD = 120 000 × 13.2 ÷ (8.8 × 5472) = 1 584 000 ÷ 48 154, which rounds to 32.89 mm/px, or 3.29 cm/px.

The footprint follows from the same proportion: width = 120 000 × 13.2 ÷ 8.8 = 180 000 mm = 180 m and height = 120 000 × 8.8 ÷ 8.8 = 120 000 mm = 120 m. One photo covers 180 × 120 m = 2.16 ha. Check it the other way: 5472 px × 32.89 mm = 180 m, which agrees.

Now suppose the deliverable is a 1:500 plan and the specification asks for 2 cm/px. Solve for the height: H = 20 × 8.8 × 5472 ÷ 13.2 = 72 960 mm = 72.96 m. Every metre of altitude is about 0.27 mm of GSD with this camera, so the difference between 73 m and 120 m is the difference between a plan you can plot at 1:500 and one you cannot.

Switch the unit system to feet and the same camera at 400 ft gives a footprint of 600 × 400 ft exactly — 121.92 m of height, 182.88 × 121.92 m — and a GSD of 1.316 in/px. The footprint is a round number in feet because 13.2 ÷ 8.8 × 400 is exactly 600; that is a property of this lens, not of the units.

Further reading

Related calculators

Frequently asked questions

How do you calculate drone GSD?

GSD = H times sensor width divided by focal length times image width, with the height and the sensor width in the same unit. In practice: convert the flight height to millimetres, multiply by the physical sensor width in millimetres, and divide by the focal length in millimetres times the image width in pixels. The answer is in millimetres per pixel.

What GSD do I need for a 1:500 map?

About 2 cm per pixel. The usual planning rule is that the GSD should be around one tenth of the contour interval, so a 0.2 m interval calls for 2 cm; most specifications for 1:500 mapping ask for 1.5 to 2 cm. Fly lower if the site has hard edges you must resolve exactly.

Does latitude or terrain height change the GSD?

The GSD depends on the height above the ground under the camera, not on the barometric or above-sea-level altitude the aircraft reports. At 1000 m elevation a planned 120 m AGL flight is still 120 m above the ground if the aircraft uses a terrain-following or radar height, but a fixed take-off-relative altitude on sloping ground gives a smaller GSD uphill and a larger one downhill.

Why does my measured GSD differ from the calculator?

Three usual reasons: the focal length quoted is the 35 mm equivalent rather than the true focal length, the sensor size is the marketing 1-inch or 4/3 class rather than the actual active area, or the lens is focused closer than infinity at the height flown, which changes the effective focal length slightly. Compare a measured distance in the orthomosaic with the same distance on the ground to calibrate once.

Should I use the full sensor or a cropped image size?

Use the pixel dimensions of the images you will actually fly with. If the camera crops the full sensor for a 16:9 video mode but the photos are 4:3, the photo dimensions are the ones that matter. If you process with a fixed crop, use the cropped dimensions and the matching portion of the sensor.

How many photos and how much flight time for a site?

The GSD gives the footprint of one photo; the overlap then gives the spacing between flight lines and between shots. Divide the site by that spacing and multiply. The flight planner next to this page does exactly that, including turn distance and battery time.

Is this drone GSD calculator free?

Yes, free, no login, no account, no usage limit. Every calculation runs locally in your browser, so no flight or project data is uploaded.

Calculations run locally in your browser. Results are for reference — confirm against the governing specification and the aircraft's flight manual before you fly. About · Privacy & cookies · Terms of use · Developers