Audited ·Last updated 28 Jul 2026·4 citations·Tier 2·0 uses

Ground Sample Distance (GSD) Calculator

Work out cm per pixel from flight height, sensor width, image width and focal length — or the altitude and lens a target GSD needs. With frame footprint.

Ground Sample Distance Calculator

What do you need?
Imaging-area width in millimetres. The 13.2 mm default is derived from DJI's own published figures for the Phantom 4 RTK: an 8.8 mm lens quoted as 24 mm equivalent means a 2.727× multiplier, giving a 15.86 mm diagonal and a 13.2 × 8.8 mm 3:2 imaging area. Full frame is 36 mm; APS-C about 23.5 mm.
mm
Still-image width in pixels, not video resolution. DJI publishes 5472 × 3648 (3:2) for the Phantom 4 RTK.
px
Still-image height in pixels. Only used for the frame footprint and coverage area — the GSD itself comes from the width and the sensor width.
px
The lens's actual focal length, not its 35 mm equivalent. Entering the equivalent would apply the sensor's crop factor twice. Ignored when you are solving for the focal length.
mm
Height above the terrain you are photographing — not above sea level, and not above your take-off point unless the two are the same. Ignored when you are solving for the altitude.
m
The ground sample distance the deliverable calls for, in centimetres per pixel. Only used when you are solving for altitude or focal length.
cm/px
Answer
At 100 m above the ground with a 8.8 mm lens, one pixel covers 2.74 cm. Each frame lands 150 m × 100 m on the ground — 1.5 hectares.
The solved quantity stated in the terms of the mode you chose, together with the ground each frame covers so the mission plan can be sanity-checked at a glance.
Ground sample distance
2.7412 cm/px
GSD in millimetres
27.4123 mm/px
Height above ground
100 m
Focal length
8.8 mm
Pixel pitch
2.4123 µm
Frame footprint (width)
150 m
Frame footprint (height)
100 m
Coverage per frame
1.5 ha
Smallest orthoimage pixel
2.8855 cm/px
What this does and does not tell you
ASPRS Edition 2 requires the acquired GSD to be no more than 95 % of the final orthoimage pixel size, so 2.74 cm/pixel raw imagery supports an orthoimage no finer than 2.89 cm/pixel. Remember that this figure is computed at one reference plane: ASPRS notes that in raw imagery "pixel size is not uniform and varies based on sensor orientation and terrain", so ground 10 % closer than the plane you entered is sampled 10 % finer. GSD is a sampling interval, not a measure of sharpness, and it is not the same thing as positional accuracy.

Background.

Ground sample distance is the number that decides whether a survey flight is worth flying. It is the ground distance one image pixel covers — 2.5 cm per pixel, 30 cm per pixel, 30 metres per pixel — and it is the single figure clients specify, deliverables are judged against, and flight plans are built around. ASPRS defines it in the Positional Accuracy Standards for Digital Geospatial Data as "the linear dimension of a sample pixel's footprint on the ground". Pix4D puts the same idea operationally: the GSD is "the distance between two consecutive pixel centers measured on the ground", so a GSD of 5 cm means one pixel represents 5 cm linearly and 25 square centimetres of area.

The arithmetic is similar triangles and nothing more. A pixel of physical size p sitting at focal length f behind a lens sees a patch of ground p × H ÷ f across, where H is the height above that ground. Divide the sensor width by the image width to get the pixel pitch, multiply by the height, divide by the focal length, and you have the answer. This calculator will solve that identity in any of three directions, because in practice you rarely know the same two things twice: how sharp will imagery from this height be, how low must I fly to hit a target, and — the one most calculators skip — what lens do I need when regulation pins my altitude at 120 metres and the client still wants 2 centimetres per pixel?

Alongside the GSD it returns the frame footprint, because that is what turns a resolution figure into a flight plan. A useful property falls out of the algebra: the footprint is sensor width × height ÷ focal length, with the pixel count cancelling out entirely. Doubling your camera's megapixel count halves the GSD but does not widen the frame by a millimetre. That is why a higher-resolution sensor lets you fly higher for the same GSD and therefore cover more ground per battery, and it is the single biggest lever on survey productivity.

The page also applies the one hard rule the standards impose. ASPRS Edition 2 states that when producing digital orthoimagery, the GSD as acquired "should not be more than 95% of the final orthoimage pixel size" — so a 2.74 cm raw GSD supports an orthomosaic no finer than 2.89 cm per pixel. Delivering a 2.5 cm orthomosaic from that flight would be resampling, not resolution, and this calculator says so rather than letting you find out at acceptance.

Two cautions run through everything below. GSD is computed at one reference plane, and ASPRS's own definition warns that in raw imagery "pixel size is not uniform and varies based on sensor orientation and terrain" — fly 100 m above a valley floor and a ridge 30 m up is sampled 30 % finer. And GSD is a sampling interval, not a measure of sharpness and certainly not a measure of accuracy: a motion-blurred, poorly controlled dataset has exactly the GSD its geometry says it has. Below the widget you will find the identity derived, a worked example computed by hand against a published drone specification, and an account of where the model stops being true.

What is ground sample distance calculator?

Ground sample distance is the spacing, projected onto the ground, between the centres of two adjacent pixels in an image. It is the standard way of describing the spatial resolution of aerial and satellite imagery, and it has a formal definition: ASPRS's Positional Accuracy Standards for Digital Geospatial Data, Edition 2, defines it as "the linear dimension of a sample pixel's footprint on the ground", adding that "in raw imagery, pixel size is not uniform and varies based on sensor orientation and terrain" and that "the term 'nominal GSD' refers to the average or approximate size of pixels in raw imagery", while "in orthorectified imagery, the GSD for all pixels is uniform and constant regardless of the terrain variation". That distinction matters commercially: the GSD written into a contract is almost always the orthoimage pixel size, which is a processing output, while the GSD a flight plan controls is the nominal raw GSD at mean terrain. The scale spans an enormous range. A drone at 2 metres inspecting a weld operates at fractions of a millimetre per pixel; a mapping flight at 100 metres is at a few centimetres; the USGS Landsat 8 OLI instrument delivers 15-metre panchromatic and 30-metre multispectral imagery, with its thermal bands at 100 metres. Every one of those figures comes from the same relation between pixel pitch, focal length and distance. What GSD is not is resolution in the optical sense. Resolution is about whether two nearby features can be told apart, which depends on the lens, on focus, on diffraction, on motion during the exposure and on atmospheric conditions. GSD only says how finely the scene is sampled. A perfectly focused image and a badly blurred one taken from the same height with the same camera have identical GSD. Nor is GSD accuracy: ASPRS Edition 2 moved deliberately to accuracy thresholds "independent of published GSD", precisely because a fine GSD with poor ground control produces detailed imagery in the wrong place.

How to use this calculator.

  1. Choose what you are solving for. "GSD" answers how sharp imagery from a planned height will be. "Altitude" answers how low to fly for a client-specified GSD. "Focal length" answers which lens meets the spec when the altitude is fixed by regulation or by terrain.
  2. Enter the sensor's imaging-area width in millimetres. If the manufacturer publishes only an actual and a 35 mm-equivalent focal length, divide the equivalent by the actual to get the crop factor, then divide 43.27 mm by that to get the sensor diagonal — the hint on the field walks through this for the default camera.
  3. Enter the still-image width and height in pixels. Use the stills resolution, not the video resolution: many cameras crop the sensor for video, which would make the pixel pitch wrong.
  4. Enter the lens's actual focal length in millimetres, never the 35 mm equivalent. The sensor width already accounts for the format, so an equivalent focal length would apply the crop factor a second time.
  5. Enter the height above the ground being imaged. This is height above terrain. Most autopilots hold height relative to the take-off point, so on sloping ground the GSD you actually acquire drifts across the site unless terrain-following is switched on.
  6. Read the GSD, then read the frame footprint. Divide the footprint dimensions by your overlap requirements to get the shutter interval along track and the flight-line spacing across track — that is the step that turns a resolution number into a mission.
  7. Check the smallest orthoimage pixel figure against what the deliverable specifies. If the contract asks for a finer orthomosaic than this flight supports under the ASPRS 95 % rule, you need to fly lower, use a longer lens or use a higher-resolution sensor — resampling will not create detail that was never acquired.
  8. Treat the result as a nominal figure at one plane. Add margin for terrain relief, and remember that GSD says nothing about whether the imagery is sharp: check your shutter speed against the aircraft's ground speed separately.

The formula.

p = SW / ImW · GSD = p × H / F · H = GSD × F / p · F = p × H / GSD · footprint = SW × H / F

The derivation is a pinhole and a pair of similar triangles. Put the lens at the apex. On the image side, a feature of size p sits at distance F from the apex; on the object side, its counterpart of size G sits at distance H. The two triangles share an angle, so G/H = p/F, which rearranges to

G = p × H / F

Take p to be the width of one photosite and G is the ground sample distance. The pixel pitch itself comes from the two figures every camera publishes:

p = sensor width (mm) / image width (px)

For the Phantom 4 RTK, 13.2 mm ÷ 5472 px = 0.0024122807 mm, or 2.4123 µm per pixel. At 100 m with the 8.8 mm lens:

GSD = 0.0024122807 × 100 / 8.8 = 0.0274122807 m = 2.7412 cm per pixel

The two rearrangements the other modes use follow immediately: H = GSD × F ÷ p, and F = p × H ÷ GSD.

The frame footprint is the same relation applied to the whole sensor rather than one pixel:

footprint width = SW × H / F footprint height = SH × H / F

Notice what dropped out. Multiply GSD by the image width and the pixel count cancels: GSD × ImW = (SW/ImW) × H/F × ImW = SW × H / F. The footprint depends only on the sensor's physical size, the height and the focal length. Doubling the megapixel count of the same sensor halves the GSD and leaves the footprint untouched. This is the arithmetic behind the productivity argument for higher-resolution survey cameras: a finer GSD at the same height, or the same GSD from a greater height, which means fewer flight lines and fewer batteries for the same site.

One externally-imposed number appears on the page, and it is quoted rather than invented. ASPRS Positional Accuracy Standards, Edition 2, section B.2: "When producing digital orthoimagery, the GSD as acquired by the sensor (and as computed at mean average terrain) should not be more than 95% of the final orthoimage pixel size." Rearranged, the smallest orthoimage pixel a given raw GSD can support is GSD ÷ 0.95. For the worked example, 2.7412 ÷ 0.95 = 2.8855 cm per pixel.

What the model deliberately leaves out: terrain relief, which makes the acquired GSD vary continuously across a site and is the reason ASPRS distinguishes nominal from actual; camera tilt, since an oblique frame has a GSD that changes from the near edge to the far edge; lens distortion, which photogrammetric processing corrects but which does make raw pixel geometry non-uniform; and image sharpness, which is a completely separate question governed by focus, diffraction, and the shutter speed against your ground speed.

A worked example.

Example

A DJI Phantom 4 RTK flying a mapping grid at 100 metres above the terrain. DJI publishes the camera on its own specification page as a 1-inch CMOS with 20 million effective pixels, an 8.8 mm lens quoted as 24 mm in 35 mm-equivalent terms, and a still-image size of 5472 × 3648 in 3:2. DJI does not print the imaging area in millimetres, so the sensor width is derived from the two figures it does print: 24 ÷ 8.8 gives a 2.727× format multiplier, the 135-format diagonal is √(36² + 24²) = 43.27 mm, so the sensor diagonal is 43.27 ÷ 2.727 = 15.86 mm, and at 3:2 that is 13.20 mm wide by 8.80 mm high. Now the arithmetic. The pixel pitch is 13.2 ÷ 5472 = 0.0024122807 mm, which is 2.4122807018 micrometres. The ground sample distance is 0.0024122807 × 100 ÷ 8.8 = 0.0274122807 metres, or 2.7412280702 centimetres per pixel — call it 2.74 cm. The frame footprint comes out at exactly 150 metres by 100 metres, and that exactness is a useful self-check, because the footprint equals sensor width × height ÷ focal length = 13.2 × 100 ÷ 8.8 = 150 m with the pixel count playing no part at all. Coverage per frame is 1.5 hectares before overlap; at a typical 75 % forward and 70 % side overlap, useful new coverage is closer to 0.11 hectares per frame, which is what determines how many images the site will produce. Finally the deliverable check: under the ASPRS 95 % rule this flight supports an orthomosaic no finer than 2.7412 ÷ 0.95 = 2.8855 centimetres per pixel, so a contract calling for a 2.5 cm orthomosaic cannot be met from 100 metres with this aircraft. Switching to altitude mode with a 2 cm target answers what would: fly at exactly 72.96 metres. And switching to focal-length mode with the altitude pinned at the 120-metre ceiling shows the alternative — a 14.47 mm lens, about a 39 mm equivalent, which the stock camera does not have.

image Width Px5,472
image Height Px3,648
sensor Width Mm13.2
target Gsd Cm2
altitude M100
solve Forgsd
focal Length Mm8.8

Frequently asked questions.

Is height measured above sea level, above take-off, or above the ground?
Above the ground you are photographing, and the distinction is the most common source of GSD error on real sites. The identity contains the distance from the lens to the surface being imaged, so on a hillside a single flight at a constant barometric height produces a GSD that varies continuously — 100 m above the valley floor and 60 m above a ridge 40 m higher gives 2.74 cm/pixel in the valley and 1.64 cm/pixel on the ridge from the same flight. ASPRS's definition anticipates exactly this: "in raw imagery, pixel size is not uniform and varies based on sensor orientation and terrain", which is why the standard speaks of nominal GSD computed at mean average terrain. Most autopilots hold height relative to the take-off point unless terrain-following is enabled and a terrain model is loaded, so on any site with relief you should either enable terrain-following or plan against the highest ground and accept a coarser GSD in the low areas.
Does a higher-megapixel camera let me cover more ground?
Yes, and the algebra shows exactly why. The frame footprint is sensor width × height ÷ focal length — the pixel count cancels out completely. Doubling the pixels across the same physical sensor therefore halves the GSD while leaving the footprint identical. Since GSD scales linearly with height, you can then fly twice as high and get the original GSD back, and at twice the height the footprint doubles in each dimension — four times the ground per frame. That is the entire productivity case for higher-resolution survey cameras, and it compounds: fewer flight lines, fewer frames, fewer batteries, less processing. The limits are real though. Flying higher means smaller pixels resolving through more atmosphere, tighter shutter-speed requirements relative to ground speed, and in many jurisdictions a hard regulatory ceiling — 120 m or 400 ft in a great many places — that caps the trade before the optics do.
What is the difference between GSD and resolution?
GSD is a sampling interval; resolution is about whether adjacent features can actually be distinguished. They are routinely conflated and they are not the same thing. An image taken at 2 cm GSD with a badly focused lens, or with the aircraft moving fast enough to smear the frame, still has a 2 cm GSD — the geometry has not changed — but it may resolve no better than 6 cm imagery from a sharp camera. Diffraction sets a hard ceiling too: stop a small drone lens down to f/11 and the Airy disc grows larger than the pixel, so extra pixels sample blur rather than detail. The practical takeaways are that GSD is necessary but not sufficient, that you should check your shutter speed against ground speed separately, and that you should be sceptical of any claim that a fine GSD alone guarantees a usable deliverable.
Why does my orthomosaic have a different pixel size from the GSD I planned?
Because those are two different quantities and the standards treat them differently. The GSD you plan is the nominal raw sampling distance at mean terrain; the orthomosaic pixel size is a processing choice made when the rectified image is resampled onto a regular grid. ASPRS Positional Accuracy Standards Edition 2 sets the relationship explicitly: "When producing digital orthoimagery, the GSD as acquired by the sensor (and as computed at mean average terrain) should not be more than 95% of the final orthoimage pixel size." So the orthomosaic pixel must be at least GSD ÷ 0.95 — a 2.74 cm acquisition supports 2.89 cm or coarser, not 2.5 cm. The standard also notes that accuracy classes are associated with the final orthoimage pixel size, not the raw GSD. If a specification names a GSD without saying which of the two it means, ask before you fly.
How does drone GSD compare with satellite imagery?
By three to four orders of magnitude, which is worth internalising when a client asks why a drone survey costs what it does. The USGS Landsat 8 OLI instrument delivers 15-metre panchromatic and 30-metre multispectral imagery, with the TIRS thermal bands at 100 metres. A consumer mapping drone at 100 metres produces about 2.7 centimetres per pixel — roughly a thousand times finer linearly, and a million times finer by area. One Landsat multispectral pixel covers 900 square metres; one drone pixel at 100 m covers 7.5 square centimetres. The trade is coverage and cadence: Landsat images 185 km swaths on a fixed repeat cycle for free, while the drone covers 1.5 hectares per frame and needs someone standing in the field. Both figures come out of exactly the same relation between pixel pitch, focal length and distance — only the distance changes, from 100 metres to 705 kilometres.
Which focal length should I enter if my camera lists two?
Always the actual focal length, never the 35 mm equivalent. Small-sensor cameras publish both — the Phantom 4 RTK lists "8.8 mm / 24 mm (35 mm format equivalent: 24 mm)" — because the equivalent tells photographers how the framing will look. But the equivalent is a framing convenience, not an optical property: an 8.8 mm lens bends light like an 8.8 mm lens whatever sits behind it. Since you have already entered the physical sensor width, entering 24 mm here would apply the crop factor a second time and understate the GSD by a factor of 2.7. There is one genuinely useful thing the equivalent figure gives you, though, and this page uses it: dividing the equivalent by the actual gives the crop factor, and dividing the 43.27 mm 135-format diagonal by that gives the sensor diagonal, which is how you recover a sensor width the manufacturer never published.

References& sources.

  1. [1]American Society for Photogrammetry and Remote Sensing (2023). ASPRS Positional Accuracy Standards for Digital Geospatial Data, Edition 2, Version 1.0. Definitions: 'ground sample distance (GSD) – The linear dimension of a sample pixel's footprint on the ground. In raw imagery, pixel size is not uniform and varies based on sensor orientation and terrain. The term "nominal GSD" refers to the average or approximate size of pixels in raw imagery. In orthorectified imagery, the GSD for all pixels is uniform and constant regardless of the terrain variation.' Annex B.2: 'When producing digital orthoimagery, the GSD as acquired by the sensor (and as computed at mean average terrain) should not be more than 95% of the final orthoimage pixel size.' Linked here via a hosted copy because asprs.org returns HTTP 403 to automated requests; the quoted text was read directly from this PDF.
  2. [2]Pix4D SA. Ground sampling distance (GSD) in photogrammetry — product documentation. 'The Ground Sampling Distance (GSD) is the distance between two consecutive pixel centers measured on the ground', and 'A GSD of 5 cm means that one pixel in the image represents linearly 5 cm on the ground (5*5 = 25 square centimeters)'. Uses the same variable set as this calculator: flight height H, image width ImW, sensor width SW, focal length F.
  3. [3]DJI. Phantom 4 RTK — Specs. Source of every default on this page: camera sensor '1" CMOS; Effective pixels: 20 M'; lens 'FOV 84°; 8.8 mm / 24 mm (35 mm format equivalent: 24 mm); f/2.8 - f/11'; still photography image size '4864×3648 (4:3); 5472×3648 (3:2)'. The 13.2 mm sensor width used as a default is derived from the published 8.8 mm / 24 mm-equivalent pair, not quoted from DJI.
  4. [4]U.S. Geological Survey. Landsat 8 mission page. The Operational Land Imager collects data at '15-meter panchromatic and 30-meter multi-spectral spatial resolutions', and the Thermal Infrared Sensor's two bands are collected at 100 m. Used on this page as the scale anchor for comparing drone-scale and satellite-scale ground sample distances.

In this category

Embed

Quanta Pro

Paid features are coming later.

  • All 590 calculators remain free
  • No billing is enabled
Coming soon