Get started

Coordinate Systems & Height Datums for Drone Surveying

Get the coordinate system wrong and your survey lands hundreds of metres — or several metres of height — off. This guide explains horizontal and vertical coordinate systems for drone mapping, with a reference of the main European and North American systems, and shows how Orthosite keeps every output in your chosen CRS.

What is a coordinate reference system (CRS)?

A CRS defines how a position on the curved Earth becomes numbers you can work with. It has two parts: a horizontal CRS (easting/northing, or latitude/longitude) and a vertical datum (height). A geographic CRS uses degrees on the globe (like WGS 84); a projected CRS flattens an area onto a grid and uses metres (like a national grid). Survey work almost always uses a projected national grid so you can measure directly in metres, and reads height in a national vertical datum. Every well-known system has an EPSG code — a short number (e.g. 3006) that names it unambiguously, so "EPSG:3006" always means SWEREF99 TM and nothing else.

Horizontal coordinate systems across Europe

Most European countries use a national grid based on ETRS89 (the European realisation of WGS 84), usually a Transverse Mercator projection in one or more zones. Use the one your project or mapping authority requires — mixing them, or using plain UTM where a national grid is expected, shifts your data by hundreds of metres to hundreds of kilometres.

Country / regionCoordinate systemEPSG
Pan-EuropeanETRS89 (geographic)4258
Pan-EuropeanETRS89-extended / LAEA3035
SwedenSWEREF99 TM3006
SwedenSWEREF99 local zones (12 00–21 45)3007–3018
SwedenRT90 2.5 gon V (legacy)3021
NorwayETRS89 / UTM 32–35N25832–25835
NorwayETRS89 / NTM zones 5–305105–5130
DenmarkETRS89 / UTM 32–33N25832–25833
DenmarkETRS89 / DKTM1–44093–4096
FinlandETRS-TM35FIN3067
FinlandETRS-GK19–313873–3885
GermanyETRS89 / UTM 32–33N25832–25833
GermanyDHDN / Gauss-Krüger 2–5 (legacy)31466–31469
FranceRGF93 / Lambert-932154
FranceRGF93 / CC42–50 (Conic Conformal)3942–3950
NetherlandsAmersfoort / RD New28992
United KingdomOSGB36 / British National Grid27700
IrelandIRENET95 / Irish Transverse Mercator2157
SpainETRS89 / UTM 28–31N25828–25831
PortugalETRS89 / Portugal TM063763
ItalyRDN2008 / TM zone 32–347791–7793
BelgiumBelgian Lambert 20083812
SwitzerlandCH1903+ / LV952056
AustriaMGI / Austria GK West–East31254–31256
PolandETRS89 / Poland CS922180
Czechia / SlovakiaS-JTSK / Krovak East North5514
GlobalWGS 84 (geographic)4326

Horizontal coordinate systems in the US & North America

North America uses NAD83. Local survey work typically uses a State Plane zone — and each state's zone comes in both metres and US survey feet, a classic source of scale errors if you pick the wrong one. Wider areas use UTM. Note that NAD83 and WGS 84 differ by 1–2 m, so they are not interchangeable for survey work.

Country / regionCoordinate systemEPSG
USA / CanadaNAD83 (geographic)4269
USANAD83(2011) (geographic)6318
USANAD83 / UTM 10–19N26910–26919
USAState Plane NAD83 (all state zones)26929–26998
USAState Plane NAD83 (US survey feet)2222–3559
CanadaNAD83(CSRS) / UTM & MTM2946–2961
GlobalWGS 84 / UTM (north/south)32601–32760

Height matters: vertical datums and the geoid

Raw GPS gives ellipsoidal height — height above a smooth mathematical model of the Earth. Surveyors need orthometric height — height above mean sea level, defined by the geoid (the Earth's gravity field). The difference, the geoid undulation, can be tens of metres (roughly +30 m in Sweden, ‑34 m in parts of the US), so you must apply the correct geoid/height model — a raw GPS altitude is not a usable ground height. Getting this wrong is one of the most common and expensive drone-survey errors.

RegionHeight system (vertical datum)EPSG
GlobalEGM2008 geoid height3855
GlobalEGM96 geoid height5773
GlobalWGS 84 ellipsoidal (no geoid)4979
SwedenRH20005613
NorwayNN20005941
NorwayNN54 (legacy)5776
FinlandN20003900
FinlandN60 (legacy)5717
DenmarkDVR905799
GermanyDHHN20167837
GermanyDHHN92 (legacy)5783
FranceNGF-IGN695720
NetherlandsNAP5709
United KingdomODN (Newlyn)5701
BelgiumOstend (TAW / DNG)5710
SwitzerlandLN025728
USANAVD885703
USANAVD88 (US survey feet)6360
USANGVD29 (legacy)5702

Datums, epochs and transformations

A datum pins a coordinate system to the Earth. Two things trip people up. First, WGS 84 and ETRS89 are not the same: ETRS89 is fixed to the stable part of the European plate, while WGS 84 follows the global frame, so they drift apart by about 2.5 cm per year — decades of drift now add up to well over half a metre. Second, precise frames carry an epoch (a date), because the ground itself moves with tectonic plates. For centimetre work you must transform between datums with the right method and epoch, not just relabel the numbers. Orthosite uses the authoritative PROJ transformation pipelines so a reprojection is a real datum shift, not a cosmetic one.

Common coordinate mistakes that ruin a survey

How Orthosite handles coordinates

Set your project's CRS from 3,000+ EPSG codes and Orthosite reads out coordinates on screen, in accuracy reports and in every export in that exact system — with proper vertical datums and geoid models so heights are correct, not just ballpark. Reprojection uses real PROJ datum transformations, GCPs are interpreted in the datum you surveyed them in, and you can switch between metres and feet anytime; it updates every measurement and report consistently.

Choosing the right one

Use the official national grid and height datum your deliverable requires — for example SWEREF99 TM + RH2000 in Sweden, or a State Plane zone + NAVD88 in the US. Confirm three things before you fly: the horizontal CRS (and zone), the vertical datum, and the units. When in doubt, match exactly whatever your ground control points were surveyed in, and check with the client or local mapping authority — it's far cheaper to confirm than to re-deliver.

FAQ

What's the difference between ellipsoidal and orthometric height?
Ellipsoidal height is measured from the WGS 84 ellipsoid (what raw GPS gives); orthometric height is measured from the geoid (mean sea level), which is what surveys use. They can differ by tens of metres.
What is an EPSG code?
A short number that uniquely names a coordinate system — e.g. EPSG:3006 is SWEREF99 TM, EPSG:27700 is British National Grid. Using the code removes any ambiguity about which system you mean.
Is WGS 84 the same as ETRS89 or NAD83?
No. ETRS89 and NAD83 are fixed to their continental plates and drift from global WGS 84 by up to ~2 m (ETRS89 ~2.5 cm/year). For survey work they must be transformed, not treated as identical.
Why is my drone data offset from the map?
Usually the wrong horizontal CRS, a datum mismatch between your GCPs and the project, or lat/lon axis order in an import. A wrong CRS can shift data hundreds of metres or more.
Which coordinate system should I use?
The official national grid and height datum your project or authority requires — e.g. SWEREF99 TM + RH2000 in Sweden, or State Plane + NAVD88 in the US. Match whatever your GCPs were surveyed in.
Metres or US survey feet?
US State Plane zones exist in both. Use whichever your deliverable specifies — mixing them scales everything by about 3.28, a common and costly error.
Does Orthosite support my coordinate system?
Yes — 3,000+ EPSG codes covering all major European and North American horizontal systems, plus vertical datums such as RH2000, NN2000, NAP, ODN, NAVD88 and EGM2008.
What is a geoid?
A model of mean sea level (the Earth's gravity equipotential surface). Orthometric heights are measured from it; converting a GPS height into a usable ground height needs a geoid model.

Turn your next flight into a survey-grade result

Upload your drone photos and Orthosite builds the orthomosaic, 3D model, point cloud and elevation models in the cloud — measure, share and export in open formats.

Get started with Orthosite
Language: EN SV NO DA FI DE FR ES NL