GPX to CSV Converter
Analyze GPS tracks in Excel, a BI tool, or a SQL database — one row per trackpoint.
Common issues converting GPX to CSV
- Each trackpoint produces one CSV row. A typical 1-hour bike ride recorded at 1Hz produces ~3,600 rows.
- Waypoints are emitted alongside trackpoints with a 'type' column distinguishing them.
- Fitness-extension fields (hr, cad, atemp) appear as dedicated columns when present in the source. Blank cells mean the extension wasn't recorded at that point.
- Timestamps are kept in ISO 8601 so Excel's text-to-date parsing works cleanly.
Frequently asked questions
What columns does the output have?
type (trackpoint/waypoint/routepoint), latitude, longitude, elevation, time, plus any fitness extension fields present (hr, cad, atemp).
Are track boundaries preserved?
A 'track_name' or 'segment_id' column records which track/segment each point belongs to, so you can GROUP BY downstream.
Can I import this into Strava or Garmin?
No — those platforms require GPX, not CSV. Use GeoJSON→GPX or export CSV and re-import into a tool that builds GPX.
How accurate are GPS timestamps?
They reflect what the source device wrote. Consumer GPS clocks are accurate to ~100ms; the CSV preserves whatever precision the GPX had.