User Rating 0.0 ★★★★★

Total Usage 0 times

Category Document Converters

Drop .gpx file here or click to browse Max 50 MB • GPX 1.0 / 1.1

or paste GPX content

JSON Output

Pretty Stats

Awaiting GPX input...

Is this tool helpful?

Your feedback helps us improve.

★ ★ ★ ★ ★

About

GPX (GPS Exchange Format) is an XML schema for describing waypoints, tracks, and routes. Raw GPX is verbose and difficult to process programmatically. Incorrect parsing drops trackpoints, truncates elevation data, or silently ignores route segments. This converter uses the browser's native DOMParser to walk the full GPX document tree, extracting trkpt coordinates (latitude φ, longitude λ), elevation ele, timestamps, waypoints wpt, routes rte, and nested metadata into a clean JSON structure. It also computes track statistics: total distance via the Haversine formula, cumulative elevation gain and loss, and duration.

The tool handles multi-track and multi-segment GPX files conforming to GPX 1.0 and 1.1 schemas. Extension elements are preserved as generic key-value objects. Note: coordinate precision is limited to the source file's decimal places. Garmin, Strava, and Komoot exports are all valid inputs. Files exceeding 50 MB are rejected to prevent browser memory exhaustion.

Formulas

Distance between consecutive trackpoints is computed using the Haversine formula, which accounts for Earth's spherical geometry:

a = sin²(Δφ2) + cos(φ₁) ⋅ cos(φ₂) ⋅ sin²(Δλ2)

d = 2 ⋅ R ⋅ atan2(√a, √1 − a)

Where φ is latitude in radians, λ is longitude in radians, Δφ = φ₂ − φ₁, Δλ = λ₂ − λ₁, and R = 6371 km (mean Earth radius, WGS-84).

Elevation gain is the sum of all positive elevation differences between consecutive points: gain = n∑i=1 max(0, ele_i − ele_i−1). Elevation loss uses the same logic for negative differences. Average speed v = d_totalt_elapsed, computed only when timestamps exist.

Reference Data

GPX Element	XPath	JSON Output Key	Data Type	Description
Metadata Name	/gpx/metadata/name	metadata.name	String	Document title
Metadata Description	/gpx/metadata/desc	metadata.description	String	Document description
Metadata Author	/gpx/metadata/author/name	metadata.author.name	String	Creator name
Metadata Time	/gpx/metadata/time	metadata.time	ISO 8601	Creation timestamp
Track	/gpx/trk	tracks[]	Array	Ordered collection of segments
Track Segment	/gpx/trk/trkseg	tracks[].segments[]	Array	Continuous sequence of points
Track Point	/gpx/trk/trkseg/trkpt	tracks[].segments[].points[]	Object	Single GPS fix with lat, lon
Elevation	trkpt/ele	point.elevation	Float (m)	Altitude above sea level
Timestamp	trkpt/time	point.time	ISO 8601	UTC time of fix
Waypoint	/gpx/wpt	waypoints[]	Object	Named POI with coordinates
Waypoint Name	wpt/name	waypoint.name	String	Waypoint label
Waypoint Symbol	wpt/sym	waypoint.symbol	String	Icon identifier
Route	/gpx/rte	routes[]	Array	Ordered list of route points
Route Point	/gpx/rte/rtept	routes[].points[]	Object	Planned navigation point
Extensions	/extensions/	*.extensions	Object	Vendor-specific data (HR, cadence, power)
Heart Rate (Garmin)	extensions/hr	point.extensions.hr	Integer (bpm)	Heart rate from chest strap or watch
Cadence	extensions/cad	point.extensions.cad	Integer (rpm)	Pedaling or step cadence
Power	extensions/power	point.extensions.power	Integer (W)	Cycling power meter output
Bounds	/gpx/metadata/bounds	metadata.bounds	Object	Bounding box: minlat, maxlat, minlon, maxlon
Link	/gpx/metadata/link	metadata.link	Object	URL with text and type attributes

Frequently Asked Questions

Each element becomes a separate object in the tracks[] array. Within each track, every becomes a nested segments[] array. This preserves the hierarchical structure. A GPX file from a multi-day hike with 3 tracks and 5 segments total produces exactly 3 track objects with their respective segment arrays intact.

Yes. Any child elements under at any level (trackpoint, track, or root) are recursively parsed into a generic extensions object. For example, Garmin's TrackPointExtension containing heart rate (hr) and cadence (cad) values appear as key-value pairs. The local element name is used as the key, stripping namespace prefixes for readability.

The converter gracefully omits missing fields. If a lacks an child, the elevation property is set to null in the JSON output. If no elements exist, the statistics section will report distance but show duration and speed as unavailable. The converter never fabricates data - it reflects exactly what the source file contains.

The Haversine formula assumes a perfect sphere with radius 6371 km. For most GPS tracks, this introduces error below 0.3% compared to the Vincenty formula (ellipsoidal model). At track scales under 1000 km, the difference is negligible. The primary source of distance error is GPS fix noise in the source data, not the formula.

Yes. Power data typically resides in vendor-specific extension elements. The recursive extension parser captures all such fields. A Wahoo ELEMNT export with power (W), temperature (°C), and speed values will appear under each trackpoint's extensions object. You can then process the JSON programmatically to compute normalized power or training stress.

The limit is 50 MB. The browser's DOMParser loads the entire XML document into memory, and JavaScript object creation roughly doubles the footprint. A 50 MB GPX file can consume over 150 MB of heap memory. Typical GPX files from day-long activities are 1-5 MB. Ultra-endurance files with 1-second recording intervals rarely exceed 20 MB.