Back to Converter Index
CLI GuideChannel: wgs 84 (epsg:4326) → etrs89 / utm zone 32n (epsg:25832)

WGS 84 (EPSG:4326) to ETRS89 / UTM Zone 32N (EPSG:25832) Converter

Convert GPS coordinates into metric coordinates for central Europe.

This guide explains how to reproject spherical global coordinates (WGS 84) to metric ETRS89 / UTM Zone 32N coordinates. Metric projections are required for precise distance and area calculations in central Europe.

Indirect Mapping Execution Required

Because database connection attributes or local attributes parsing is required, direct web streams are disabled. Use the GDAL CLI script below for precise terminal conversions.

Specification Rules

  • Prepare global GPS files for regional planning calculations in Europe
  • Measure exact property line dimensions without distortion
  • Export localized maps that align with municipal standards in Germany
  • This projection is only accurate within its specific zone in Europe
  • Requires grid shifts for high-precision scientific mappings
  • Values change from degrees to metric coordinate readings

GDAL Direct Equivalent Terminal Command

sh — gdalready
$ogr2ogr -f GPKG output.gpkg input.geojson -s_srs EPSG:4326 -t_srs EPSG:25832

When to use this conversion

Use this reprojection when working with data in central Europe (Germany, Austria, Czech Republic, much of Italy and Poland) and you need accurate metric measurements — building footprints in square metres, distances in metres, areas computed correctly. UTM Zone 32N is the workhorse projected CRS for that region.

Technical Details

GDAL applies a PROJ transformation pipeline from WGS 84 geographic (EPSG:4326) to ETRS89 / UTM 32N (EPSG:25832). PROJ performs the datum shift (WGS 84 ↔ ETRS89 is essentially negligible at sub-metre precision because the two are functionally equivalent for Europe) and then the UTM 32N projection (transverse Mercator centred on 9°E with a scale factor of 0.9996). The result is metric coordinates with sub-metre accuracy across the zone.
Output file size

Reprojection does not change file size meaningfully. Coordinate string length is slightly larger in metric (7-digit easting vs 6-digit longitude) but the difference is under 5% in most formats.

Common Errors & Fixes

  • Data outside UTM 32N: applying this projection in zone 33 (eastern Germany, Austria) produces metre-scale distortion. Fix: use EPSG:25833 instead for those regions.
  • Vertical datum confused with horizontal: 4326 → 25832 is a horizontal transformation only; elevations stay in the source vertical reference. Fix: handle vertical CRS separately if elevations matter.
  • Grid shift file missing: ultra-high-precision work requires the BeTA2007 NTv2 grid shift between DHDN and ETRS89. Fix: install the PROJ-data resource package containing the grid shift files.
  • Round-trip drift: repeated 4326↔25832 conversions accumulate floating-point error. Fix: convert once, keep the projected CRS as the working coordinate system for analysis.

Alternative Tools

  • PROJ CLI: cs2cs +init=epsg:4326 +to +init=epsg:25832
  • QGIS: right-click layer → Export → Save Features As with Target CRS set to EPSG:25832
  • Python: geopandas.GeoDataFrame.to_crs(25832)
  • PostGIS: ST_Transform(geom, 25832) in any SELECT

Frequently Asked Questions

Why does my mapping look stretched when using EPSG:4326?

EPSG:4326 uses spherical calculations, distorting measurements as you move away from the Equator. UTM Zone 32N provides an accurate metric projection for Central Europe.

How do of measurement unit types change?

Your coordinate systems transition from decimal degrees to physical metric meters of easting and northing.

Is this conversion applicable to areas outside Europe?

No. Using this projection in other parts of the world will result in severe coordinate distortion.

Related Transformations Map

Epsg 4326 To Epsg 3857Geojson To GeopackageShapefile To Geopackage