Convert GPX to GeoJSON

GPX to GeoJSON: why convert

GPX is the standard way to get a recorded hike, ride or run out of a GPS device, Strava, Garmin Connect or Komoot. To show that trip on a Leaflet or MapLibre map, draw an elevation profile with D3, or load it into PostGIS or another database, GeoJSON is the format to have. This converter reads the waypoints, routes and tracks in the GPX and writes them as GeoJSON features, with the elevation of every point as the third coordinate. GPX files come with a long list of standard fields that are almost always empty, such as magvar, hdop or link2_type; only the fields that hold a value are kept, so the properties stay clean. Everything runs in your browser with GDAL, and the file is not uploaded.

How to convert GPX to GeoJSON

1. Drop your .gpx file in the box, or click to choose it.
2. Check the track on the map, and tick the box if you also want every track point with its time.
3. Click Convert and download the GeoJSON file, or a zip with one file per kind of data.

What changes when you convert

One GeoJSON file per kind of data

A GPX can hold waypoints, routes and tracks at the same time, with different fields for each. They become separate files named waypoints.geojson, routes.geojson and tracks.geojson in a zip. A file that holds only a track, as most exports from Strava or a watch do, gives a single GeoJSON named after the GPX.

A track is a MultiLineString

A GPX track is made of segments, and a new segment starts when the recording was paused or the signal was lost. To keep those gaps, each track becomes one MultiLineString feature with a line per segment. A route is a single LineString and a waypoint a Point.

Elevation as the third coordinate

Elevations from the ele tags become the third value of each coordinate, as RFC 7946 allows, for example [12.504, 55.77, 38]. Web maps ignore it, but it is there for elevation profiles and 3D views. Points without elevation keep two values, and the elevation of waypoints is also kept as an ele property.

Time stamps need the track points

A line in GeoJSON has no place for a time per point. Tick "Also include every track point" to get an extra file, track_points.geojson, with one Point feature per recorded point and its time, elevation, track number and segment number as properties. That file can be large: a two-hour ride recorded every second has over 7,000 points.

Device extensions are not read

Heart rate, cadence, power and temperature that watches and bike computers store as extensions to each point are not part of the output. Waypoint names, descriptions, symbols and types are kept.