UTM zone 32 or 33? Choosing EPSG:25832 and EPSG:25833
A UTM coordinate without its zone is ambiguous. German datasets commonly use ETRS89 / UTM 32N or 33N. Both produce six-digit eastings in metres, so the coordinate values alone usually do not reveal the correct zone.
Published · Updated
The short answer
The regular boundary between zones 32 and 33 is 12° east longitude. Longitudes from 6°E up to 12°E fall in zone 32; from 12°E up to 18°E they fall in zone 33. For ETRS89, the common codes are EPSG:25832 and EPSG:25833.
Source metadata still comes first. Survey authorities and cross-boundary projects may deliberately publish a dataset in one zone for continuity. The geographical rule is a check, not permission to override documented metadata.
Zone 32 and zone 33 compared
| CRS | Regular longitude range | Central meridian | EPSG code |
|---|---|---|---|
| ETRS89 / UTM zone 32N | 6°E to below 12°E | 9°E | EPSG:25832 |
| ETRS89 / UTM zone 33N | 12°E to below 18°E | 15°E | EPSG:25833 |
How to determine the correct zone
- Read the metadata. Search a
.prj, layer properties, delivery note or product description for25832,25833,UTM32orUTM33. - Check the data authority or project convention. Its documented CRS takes precedence over a simple rule based on the dataset's centre point.
- Test a known point in both zones. Transform the same easting and northing to WGS 84. The wrong zone generally moves the result several hundred kilometres east or west.
- Do not rely on the easting alone. Values around 300,000–700,000 occur in both zones. A zone prefix such as 32 or 33 can be a clue, but digital datasets often omit it.
Worked example: Berlin interpreted in the wrong zone
The reference point 13.405°E / 52.52°N in Berlin transforms, using the same PROJ path as GeoVerto, to approximately 391779.259 E / 5820072.159 N in EPSG:25833.
If those exact numbers are interpreted as EPSG:25832, the point appears near 7.405°E instead of 13.405°E — on roughly the same latitude but around 400 kilometres too far west. That pattern is a strong sign that the UTM zone was swapped.
Assign the source CRS before transforming
First identify which CRS the unchanged numbers already use. Assign that as the source. Only then transform to a different target CRS. Simply replacing an EPSG label without understanding the source does not convert anything; it changes how software interprets the same numbers.
Preserve the original file, record the evidence for your choice and verify at least one known point after transformation. For a Shapefile, store the confirmed definition in its.prj file.