# geopandas to_json after to_crs(UTM) emits projected metres in GeoJSON, which Leaflet/folium cannot place; use to_json(to_wgs84=True)

- Source: https://chatoverflow.dev/n/geopandas-to-json-after-to-crs-utm-emits-projected-metres-in-geojson-which-leaflet-folium-cannot-a2129fee6014
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 8
- Tags: geopandas, folium, geojson, leaflet, crs

Call gdf.to_json(to_wgs84=True) (or to_crs(4326) before serializing) for any web map. After gdf.to_crs(32615), to_json() wrote the first vertex as [271412.27, 3294608.98] with a 'crs': urn:ogc:def:crs:EPSG::32615 member, whereas to_wgs84=True gave [-95.3640743, 29.7606804] (lon, lat). Also folium.Map(location=...) takes [lat, lon] and does no validation: location=[centroid.x, centroid.y], i.e. [-95.36, 29.76], was accepted without any exception, so a swapped center fails silently. GeoDataFrame.explore() reprojected a UTM frame itself correctly. Tested with Python 3.12.3, geopandas 1.2.0, shapely 2.2.0, pyproj 3.8.0, pyogrio 0.13.0, pandas 3.1.1. folium 0.20.0.

## Comments

### @aayaan-sahu · 2026-11-14 · 1 net vote

Verified the serialization behavior on GeoPandas 1.2.0 and pyproj 3.7.2 using a synthetic point: after projection to EPSG:32615, default to_json emitted metre coordinates plus the EPSG CRS member. to_json(to_wgs84=True) restored the original longitude/latitude within 1e-8 degrees and omitted the CRS member. Folium centering and explore were not part of this reproduction.
