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 / region | Coordinate system | EPSG |
|---|---|---|
| Pan-European | ETRS89 (geographic) | 4258 |
| Pan-European | ETRS89-extended / LAEA | 3035 |
| Sweden | SWEREF99 TM | 3006 |
| Sweden | SWEREF99 local zones (12 00–21 45) | 3007–3018 |
| Sweden | RT90 2.5 gon V (legacy) | 3021 |
| Norway | ETRS89 / UTM 32–35N | 25832–25835 |
| Norway | ETRS89 / NTM zones 5–30 | 5105–5130 |
| Denmark | ETRS89 / UTM 32–33N | 25832–25833 |
| Denmark | ETRS89 / DKTM1–4 | 4093–4096 |
| Finland | ETRS-TM35FIN | 3067 |
| Finland | ETRS-GK19–31 | 3873–3885 |
| Germany | ETRS89 / UTM 32–33N | 25832–25833 |
| Germany | DHDN / Gauss-Krüger 2–5 (legacy) | 31466–31469 |
| France | RGF93 / Lambert-93 | 2154 |
| France | RGF93 / CC42–50 (Conic Conformal) | 3942–3950 |
| Netherlands | Amersfoort / RD New | 28992 |
| United Kingdom | OSGB36 / British National Grid | 27700 |
| Ireland | IRENET95 / Irish Transverse Mercator | 2157 |
| Spain | ETRS89 / UTM 28–31N | 25828–25831 |
| Portugal | ETRS89 / Portugal TM06 | 3763 |
| Italy | RDN2008 / TM zone 32–34 | 7791–7793 |
| Belgium | Belgian Lambert 2008 | 3812 |
| Switzerland | CH1903+ / LV95 | 2056 |
| Austria | MGI / Austria GK West–East | 31254–31256 |
| Poland | ETRS89 / Poland CS92 | 2180 |
| Czechia / Slovakia | S-JTSK / Krovak East North | 5514 |
| Global | WGS 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 / region | Coordinate system | EPSG |
|---|---|---|
| USA / Canada | NAD83 (geographic) | 4269 |
| USA | NAD83(2011) (geographic) | 6318 |
| USA | NAD83 / UTM 10–19N | 26910–26919 |
| USA | State Plane NAD83 (all state zones) | 26929–26998 |
| USA | State Plane NAD83 (US survey feet) | 2222–3559 |
| Canada | NAD83(CSRS) / UTM & MTM | 2946–2961 |
| Global | WGS 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.
| Region | Height system (vertical datum) | EPSG |
|---|---|---|
| Global | EGM2008 geoid height | 3855 |
| Global | EGM96 geoid height | 5773 |
| Global | WGS 84 ellipsoidal (no geoid) | 4979 |
| Sweden | RH2000 | 5613 |
| Norway | NN2000 | 5941 |
| Norway | NN54 (legacy) | 5776 |
| Finland | N2000 | 3900 |
| Finland | N60 (legacy) | 5717 |
| Denmark | DVR90 | 5799 |
| Germany | DHHN2016 | 7837 |
| Germany | DHHN92 (legacy) | 5783 |
| France | NGF-IGN69 | 5720 |
| Netherlands | NAP | 5709 |
| United Kingdom | ODN (Newlyn) | 5701 |
| Belgium | Ostend (TAW / DNG) | 5710 |
| Switzerland | LN02 | 5728 |
| USA | NAVD88 | 5703 |
| USA | NAVD88 (US survey feet) | 6360 |
| USA | NGVD29 (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
- Wrong horizontal CRS — data lands hundreds of metres or kilometres away; the classic "why is my map in the sea?".
- Ellipsoidal vs orthometric height — heights off by tens of metres because a raw GPS height was used instead of a geoid-corrected one.
- Metres vs US survey feet — a State Plane zone in the wrong unit scales everything by ~3.28.
- Mixing datums — GCPs surveyed in one datum, project set to another (e.g. NAD83 vs WGS 84), leaving a 1–2 m offset.
- Ignoring the epoch — using ETRS89 numbers as if they were WGS 84 (or vice-versa) on precise work.
- Lat/lon axis order — swapping latitude and longitude in imported files.
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?
What is an EPSG code?
Is WGS 84 the same as ETRS89 or NAD83?
Why is my drone data offset from the map?
Which coordinate system should I use?
Metres or US survey feet?
Does Orthosite support my coordinate system?
What is a geoid?
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