Shapefile to GPX Converter
Push GIS-sourced points or lines onto a GPS device (trail volunteers, field surveyors, cartographers).
Common issues converting Shapefile to GPX
- Point shapefiles become <wpt> waypoints. Line shapefiles become <trk> tracks. Polygons are rendered as tracks using their outer ring.
- DBF attributes don't map cleanly to GPX. Only name, description, and time are preserved; other attributes are dropped.
- The shapefile must include a .prj (or already be in WGS 84) — GPX requires WGS 84 and we can't reproject without projection metadata.
- A shapefile of tens of thousands of features produces a large GPX. Most GPS devices handle GPX files up to a few MB gracefully; above that behavior varies.
Frequently asked questions
What shapefile geometry types become tracks?
Lines become tracks (<trk>). Polygons become tracks built from their outer ring (useful for property lines or loop hikes). Points become waypoints (<wpt>).
Do DBF attributes carry over?
Only a handful map cleanly — name, description, time. Most custom attributes are dropped. GPX has no open attribute-table concept.
What if the shapefile is in UTM or State Plane?
The .prj is used to reproject to WGS 84, which GPX requires. Without a .prj we can't safely reproject and the output may land in the wrong place.
Will it load on my Garmin?
Yes, modern Garmins read GPX 1.1. Very large files may be chunked by the device or imported into BaseCamp first.