Converts GeoJSON into GPX so a GPS device can use it. GeoJSON is the format of web mapping; GPX is the format of hardware, and they do not overlap.
What GPX cannot take
Polygons become closed tracks — the outline survives, the area does not, and holes are dropped.
Arbitrary properties mostly vanish. GeoJSON lets a feature carry any JSON object; GPX has fixed fields. name, description and time are mapped; everything else has nowhere to go. Convert to CSV instead if the attributes are the point.
MultiPolygons and GeometryCollections are split into their parts first, so nothing disappears silently.
Elevation
<ele>. Two-value positions produce points with no elevation, which is valid GPX — most devices treat missing elevation as unknown rather than as zero, which is the right behaviour.Which GPX element each geometry becomes
Other names for this
Also searched as “json to gpx”, “geojson to garmin”.
Questions
- My polygons became lines.
- GPX has no polygon type. The outline is preserved as a closed track, and the tool says so.
- Where did my feature properties go?
- GPX has fixed fields — name, description, time — and no general property mechanism. Use CSV if the attributes matter.
- It says my JSON is not GeoJSON.
- A plain array of {lat, lng} objects is not GeoJSON. Convert it to CSV first, then use CSV to GeoJSON.
- Is my file uploaded?
- No. Everything runs in this tab. That matters more here than almost anywhere else on the site — a calendar is your movements, an address book is other people’s personal data, and a GPS track is where you live and where you run. None of it is sent anywhere.