GPX Viewer & Trail Track Visualizer
Upload and inspect GPX files from GPS watches, Garmin, or Strava. Renders GPS trail tracks, computes total track distance, and parses elevation profiles directly in your browser.
GPX File Inspector & Map Viewer
Paste or upload a GPX file to render spatial geometries.
How to use the GPX viewer
- 1Open a GPX file
Drop or choose a .gpx file from a GPS watch, Garmin device or app such as Strava.
- 2Draw the track
Tracks, routes and waypoints are drawn on the map in your browser.
- 3Read distance and elevation
See the total track distance and the elevation data recorded in the file.
What Is a GPX File?
Established in 2002 by Dan Foster of TopoGrafix and updated to version 1.1 in 2004, the GPS Exchange Format (GPX) is the global open XML standard for exchanging GPS telemetry between consumer navigation devices (Garmin, Wahoo, Apple Watch, Suunto) and spatial mapping software (Strava, Gaia GPS, Komoot, QGIS).
GPX organizes geographic movement into three distinct spatial concepts:
- Waypoints (
<wpt>): Individual, isolated points of interest. They have no sequential or temporal relationship to one another (e.g., parking lots, water sources, emergency shelters). - Routes (
<rte>): An ordered list of navigation points (<rtept>) representing where you plan to go. A GPS unit calculates turn-by-turn vectors between these milestone intersections. - Tracks (
<trk>): An ordered, high-frequency breadcrumb record of where you actually went. Tracks contain one or more track segments (<trkseg>) composed of hundreds or thousands of sequential track points (<trkpt>).
What a GPX Track Contains: Time, Speed and Heart Rate
Unlike pure geographic lines that only capture latitude and longitude, a true GPX track point is a multi-dimensional physical event:
Four-Dimensional Coordinates
Each <trkpt lat="..." lon="..."> includes an elevation element (<ele> in meters) and an exact UTC timestamp formatted in ISO 8601 (e.g., <time>2026-09-19T14:32:05Z</time>). Dividing spatial distance between points by elapsed seconds yields instantaneous velocity and acceleration profiles.
Garmin Biometric Extensions
Modern fitness wearables inject vendor extension schemas inside track points (<gpxtpx:TrackPointExtension>), recording heart rate in beats per minute, pedaling cadence in RPM, cycling power in watts, and ambient temperature.
Why GPX Elevation Gain Numbers Differ
Hikers, mountaineers, and cyclists frequently notice a perplexing anomaly: uploading the exact same GPX file to Strava, Garmin Connect, and AllTrails produces radically different total elevation gain figures (e.g., 850 m vs. 1,120 m vs. 940 m).
This occurs because raw satellite GPS elevation fixes fluctuate erratically due to atmospheric refraction, clock drift, and satellite constellation geometry. If a hiker walks across a perfectly flat salt flat for 10 kilometers, satellite elevation jitter may bounce by ±3 meters every second. If an algorithm naively sums every positive upward delta ($\sum \Delta h$), it reports hundreds of meters of “phantom climbing” on dead-flat ground.
Authoritative GPX analyzers apply smoothing algorithms: either a minimum vertical threshold filter (e.g., ignoring climbs smaller than 3 to 5 meters) or moving-average / Gaussian kernel smoothing.
How GPX Distance and Elevation Gain Are Calculated
When traversing steep mountain grades, flat 2D distance underestimates true ground travel. Engineers compute the true 3D Euclidean distance and filtered cumulative ascent:
d_{\text{3D}} = \sqrt{d_{\text{2D}}^2 + (\Delta h)^2}, \quad \text{Gain} = \sum_{i=1}^{n-1} \max(0, h_{i+1} - h_i) \quad [\text{subject to threshold } \tau = 3.0\text{ m}]- Horizontal square: d_2D^2 = 120.0^2 = 14,400 m²
- Vertical square: (Δh)^2 = 50.0^2 = 2,500 m²
- Sum of squared dimensions: 14,400 + 2,500 = 16,900 m²
- 3D True Distance: d_3D = sqrt(16,900) = 130.00 meters
- Distance difference vs 2D: +10.0 meters (+8.33% longer than flat horizontal map projection)
- Calculated Grade / Incline: (50.0 m / 120.0 m) * 100 = 41.67% slope (22.62° incline)
- Cumulative Ascent Contribution: +50.0 meters added to cumulative climb
Accounting for the steep 41.7% mountain slope reveals hikers walked 130 meters rather than 120 meters, with the 50-meter climb validated by exceeding sensor noise thresholds.
GPX Elements Reference (Table)
Consult this comprehensive structural matrix detailing GPX element semantics, data schemas, and sensor extension tags:
GPX 1.1 XML Elements & Sports Telemetry Extension Architecture
Evaluation of XML containment, temporal sequence semantics, typical point densities, and extension capabilities.
| GPX XML Element | Temporal Sequencing | Primary Cartographic Purpose | Typical Point Density | Associated Child Tags / Telemetry |
|---|---|---|---|---|
<wpt> (Waypoint) | Unordered point collection | Marks notable standalone geographic points of interest (campsite, summit, trail junction) | 1 to 50 points per GPX file | <name>, <sym>, <desc>, <ele> |
<rte> (Route) | Ordered sequence of steering points | Pre-planned navigational itinerary guiding the user from turn to turn | 10 to 200 route points (<rtept>) | Turn instructions, distance-to-next |
<trk> (Track) | Strictly chronological breadcrumb trail | Exact historical recording of where the GPS receiver physically traveled over time | 1,000 to 50,000 track points (<trkpt>) | <time>, <ele>, <speed>, <course> |
<trkseg> (Track Segment) | Continuous recorded sequence | Groups uninterrupted recording intervals; new segments indicate GPS signal loss or pause | 1 to 10 segments per track | Preserves journey continuity |
<extensions> (Garmin TrackPointExtension) | Per-trackpoint biometric metadata | Stores fitness telemetry: heart rate (hr), cadence (cad), power (watts), water temp | Synchronized 1 Hz sample rate | Garmin GPX extensions v3 schema |
GPX Viewer Accuracy: GPS Drift and Gaps
Understanding consumer GPS limitations helps users interpret recorded tracks accurately:
- Vertical vs Horizontal Dilution of Precision (VDOP vs HDOP): Because GPS satellites are always located in the sky above the horizon (never beneath the Earth), vertical geometry is inherently unbalanced. Consequently, vertical elevation error is systematically 2 to 3 times greater than horizontal positional error. Barometric altimeters (which measure atmospheric pressure) provide far superior relative elevation smoothing.
- Multipath Reflection & Urban Canyons: In narrow mountain gorges or downtown skyscraper corridors, satellite signals bounce off rock walls and glass facades before reaching the antenna. This creates “GPS multipath drift,” causing recorded tracks to zigzag wildly across cliffs or highway medians.
- Smart vs 1-Second Recording: Many watches default to “Smart Recording,” logging points only when heading or velocity changes. While conserving battery, this clips sharp switchback corners, artificially reducing recorded total trail distance by 5% to 15%. For maximum navigational accuracy, configure devices to 1-second interval logging.
- GPX coordinate attributes (lat and lon) must be in signed decimal degrees (WGS 84); degrees-minutes-seconds formats violate the GPX 1.1 XML schema.
- Files lacking <time> timestamps cannot compute speed, pace, moving time, or stopped duration metrics.
- Raw elevation gain from non-barometric GPS watches should always be smoothed with a minimum threshold filter (3–5 meters) to eliminate phantom climbing jitter.
Related Outdoor, Navigation & Vector GIS Tools
Complement your GPX routes with elevation profilers, KML viewers, and distance calculators:
Quick facts about the GPX viewer
| Fact | Value | Notes |
|---|---|---|
| Format Standard | GPX 1.1 XML Schema | GPS Exchange Format |
| Parsed Entities | Trackpoints (<trkpt>), Elevation (<ele>) | Sequential GPS trail points |
| Hardware Compatibility | Garmin, Apple Watch, Strava, Wahoo | Universal sports GPS format |
Edge cases and exceptions
GPS Drift & Tunnel Gaps
Raw GPS trackpoints recorded in tunnels or dense urban canyons may exhibit erratic jumps (multipath errors). Our parser tracks sequential distance.
The GPX viewer: worked examples
Half-Marathon Route Review
Scenario: Uploading a 21.1 km race track recorded on a GPS running watch.
Outcome: Displays the complete race track path with elevation checkpoints across the course.
Frequently asked questions about the GPX viewer
What is a GPX file?
GPX (GPS Exchange Format) is an open XML standard used by GPS devices and fitness apps to store waypoints, tracks, and routes.
What is the difference between a track, a route and a waypoint?
A track is the recorded breadcrumb path, a route is a planned path, and a waypoint is a single saved place.
How is distance calculated from a GPX?
The tool adds the geodesic distance between consecutive points. Noisy tracks can add extra distance.
Why does elevation gain differ from my watch?
Different sources and smoothing yield different totals. Barometric altimeters, GPS height and map models rarely agree exactly.
How do I export a GPX from Strava or Garmin?
Open the activity on the website and choose Export GPX, or use the menu in the app.
Is my track kept private?
Yes. The file is processed in your browser and not uploaded.
Can I view a GPX elevation profile?
The viewer parses elevation; for a custom line between points use the elevation profile tool.
Why is my GPX track jagged?
GPS noise, tall buildings and tree cover cause jitter, especially when moving slowly.
Can I merge or edit tracks?
This viewer is read-only. Use dedicated GPX editors for merging and trimming.
What units does the viewer use for distance and elevation?
Distances appear in miles and kilometers and elevations in feet and meters. GPX files themselves store meters and decimal-degree coordinates.
Keep exploring
What to do with this result
- Elevation Profile ToolUse this to draw an elevation profile.
- GeoJSON Viewer & Map InspectorUse this to view a GeoJSON file.
- KML Viewer & Google Earth Map InspectorUse this to view a KML or KMZ file.
- Multi-Stop Route Distance CalculatorUse this to total a multi-stop route.
- What Is My Elevation?Use this to check your current elevation.