GeoJSON to GPX Converter
Gets a route planned in a web tool onto a GPS device or fitness app.
Common issues converting GeoJSON to GPX
- LineStrings become <trk> elements by default (tracks). Set a 'gpxType': 'route' property on the feature to emit <rte> elements instead.
- Polygons have no native GPX equivalent. Their outer ring is written as a track — usable for property lines or loop hikes.
- GeoJSON 3D coordinates (longitude, latitude, elevation) become <ele> elements on each trackpoint. 2D features get no elevation tag.
- Feature 'name' properties map to the GPX <name> element so tracks and waypoints are labeled correctly on-device.
Frequently asked questions
Which GeoJSON geometries become tracks versus routes?
By default LineStrings become tracks (<trk>), because that matches the convention of a recorded path. Set 'gpxType': 'route' on the feature to emit <rte> elements instead.
Will my output work on a Garmin?
Yes. The output is GPX 1.1, which every Garmin device and app (BaseCamp, Connect, Edge) reads natively.
Can I include elevation?
Yes. If your coordinates have a Z component (3D GeoJSON), it's written as <ele> on each point.
What about Point features?
They become GPX <wpt> waypoints, with name, description, and time preserved from the feature properties.