Coordinate Systems & Datums: The Complete Guide

There are two fundamental ways to express a position. A geographic coordinate system uses latitude and longitude — angles on a curved ellipsoid, measured in degrees. A projected coordinate system flattens that ellipsoid onto a plane so you can work in metres of easting and northing, the way a total station or a site plan does.

You cannot flatten a sphere without distortion — that is a mathematical certainty. Every projection trades off distortion in area, shape, distance or direction. The surveyor's job is to pick a projection whose distortion is negligible over the project area, and to convert correctly between the two worlds. Our Coordinate Converter handles both directions.

A datum defines where the ellipsoid sits relative to the Earth — its size, shape and origin. Two coordinates can have identical latitude and longitude numbers and still be hundreds of metres apart on the ground if they use different datums. This is the single most expensive mistake in surveying, and it is entirely avoidable.

Here is the subtlety that catches people: WGS84 and ETRS89 were identical in 1989 but now differ by roughly 2.5 cm per year because the European plate drifts. After 30 years that is nearly a metre. For continental data this is irrelevant; for a cadastral survey it is a boundary dispute. Always confirm not just the datum but, for high accuracy, its epoch. Look up the exact definition of any datum in the EPSG Explorer, and see official choices by country in the Country Surveying Profiles.

The Universal Transverse Mercator system slices the world into 60 zones, each 6° of longitude wide, numbered 1–60 eastward from the 180° meridian. Within a zone, distortion stays under about 1 part in 1,000 — small enough for most survey work. Each zone has a northern and southern variant.

Zone numbers follow a simple rule: zone = floor((longitude + 180) / 6) + 1. So longitude 9°E (northern Italy) falls in zone 32N, EPSG:32632. Rather than compute it by hand, drop a pin in our UTM Zone Finder and read the zone and EPSG code directly. The trap to avoid: a project that straddles two zones. Working across a zone boundary introduces a coordinate jump — you either pick one zone for the whole project or use a national grid designed for the country's shape.

An EPSG code is a short number that unambiguously identifies a coordinate reference system — datum, ellipsoid, projection and units all bundled together. The EPSG registry contains over 8,000 codes. Quoting a code removes all ambiguity: instead of arguing about "UTM in metres", everyone agrees on EPSG:32632.

Some codes every surveyor recognises:

Search all 8,000+ codes, with their parameters and areas of use, in the EPSG Explorer. When you hand off data, always state the EPSG code in the metadata — it is the difference between a deliverable that loads correctly anywhere and one that lands in the ocean.

Conversions come in two flavours, and confusing them is where accuracy leaks away:

• A projection change within the same datum (e.g. WGS84 lat/lon → UTM 32N) is exact mathematics. No accuracy is lost.
• A datum transformation (e.g. WGS84 → ETRS89, or an old national datum → a modern one) is a modelled approximation. The quality depends entirely on the transformation parameters you use.

For datum shifts, a simple 3-parameter (Helmert) transform may be good to a metre, while a 7-parameter or an official grid-shift file (such as NTv2) reaches centimetres. Never mix datums silently and hope: a 1-metre error from the wrong transform looks perfectly plausible until it fails a check. Use the Coordinate Converter for everyday conversions, and verify the parameters against the official definition in the EPSG Explorer.

Horizontal coordinates are only half the story. Height needs its own datum, and there are two kinds that are easy to confuse:

• Ellipsoidal height — height above the mathematical ellipsoid, what GNSS gives you directly.
• Orthometric height — height above the geoid (mean sea level), what levelling and engineering actually use.

The difference between them — the geoid undulation — can exceed 50 metres in places. To convert GNSS ellipsoidal height into a usable elevation you apply a geoid model. Near the coast, the reference for sea level itself is a tidal datum, which has its own subtleties. See the Tide & Datum Reference and the GNSS Surveying guide for how this plays out in the field.

1. Know your output datum before you start. Check the legal/official datum for the country in the Country Profiles.
2. Record the EPSG code in every file. Look it up in the EPSG Explorer and put it in the metadata.
3. Pick one projection for the whole project. Use the UTM Zone Finder and avoid straddling zones.
4. Use official transformation parameters for datum shifts. Grid-shift files over simple 3-parameter where accuracy matters.
5. Validate on a known point. Transform a control point and confirm it lands where it should before trusting the whole dataset.

For definitions of any term here, the surveying glossary is a click away.