GeoJSON Converter

One converter for every GeoJSON output

GeoJSON is the format web maps, APIs and JavaScript libraries such as Leaflet and Mapbox speak: one text file with a FeatureCollection, longitude and latitude in WGS84, and any properties you like on each feature, including nested objects and lists. Desktop GIS, Google Earth, GPS devices and Excel each expect something else, which is why GeoJSON so often has to be converted. This page reads the file and first shows what is in it: the features on a map, every property in a table you can search and sort, and how many points, lines and polygons there are. Then you pick the output. A shapefile suits ArcGIS and older GIS workflows, KML suits Google Earth and Google My Maps, GPX suits Garmin devices and hiking apps, and CSV opens the properties in Excel with coordinates or WKT in their own columns. The conversion uses GDAL, the library behind QGIS, compiled to run in the browser, so data from an internal API or an unpublished project stays on your computer. The pages linked below explain each single conversion in more detail.

How to convert a GeoJSON file

1. Drop a .geojson or .json file on the page, or click to select it.
2. Check the map, the property table and the geometry types in the summary.
3. Choose the output format and its options, then click Convert to download the file.

What changes with each output format

A shapefile holds one geometry type

A GeoJSON FeatureCollection can mix points, lines and polygons, but a shapefile cannot. The converter writes one shapefile per type, such as stops_points.shp and stops_lines.shp, in one .zip with a .prj and a .cpg each. Property names longer than 10 characters are shortened and kept unique, because the .dbf table allows no more.

Nested properties become text

Shapefiles, KML and CSV have no fields for objects or lists, so a property such as tags with ["bus", "night"] is written as JSON text. Numbers, true and false, and dates stay as values. GPX keeps the properties without a GPX element of their own as extensions, which most GPS devices ignore.

GPX has no areas

In GPX, points become waypoints and lines become tracks. A polygon becomes a track along its outline, with one segment per ring, so a park or a zone shows as a closed line on the device. Choose which property names the waypoints and tracks.

Coordinates stay in WGS84 unless you choose otherwise

A standard GeoJSON is longitude and latitude in WGS84 (RFC 7946). KML and GPX are WGS84 too. A shapefile or CSV keeps WGS84 unless you enter an EPSG code such as 25832 for UTM 32N, which you need when you want to measure in meters. An older GeoJSON with a crs member in another system is read in that system.

Colors from geojson.io and Mapbox

Simplestyle properties such as marker-color, stroke and fill become a real KML style on each placemark, so Google Earth shows the same colors. A shapefile keeps them as shortened fields (marker-col, stroke-wid …) with a .qml style file that makes QGIS draw each feature in its color. GPX and CSV keep them only as values.