GPX GPS Data
Maps & GPSGPX stores waypoints, routes and recorded tracks as XML. A planned route differs from a recorded sequence of track points. Time or elevation may be absent; a displayed line alone does not establish an accurate travel log or navigable route.
- What it is used for
- Exchange of waypoints, planned routes and recorded tracks
- What the file contains
- Text
All sections, questions and sources
Content reviewed: · Editor:Kai
Opening steps
Choose your environment or purpose to see its steps.
Menu labels and support vary by app, OS and version. Preserve the original before making changes.
Troubleshooting by symptom
- No route: check track/route support and selected layers.
- Jumping line: inspect segment breaks/missing points; avoid joining disconnected spans.
- Time shift: compare timestamp offsets and display time zones.
- Nothing visible: inspect layer selection, extent and actual point content.
- Time differs by hours: compare stored time and display timezone.
- Navigation takes another road: distinguish track display from route recalculation.
GPX → KML / GeoJSON / coordinate table
- Select required points/tracks and use a supported GIS export.
- Compare locations, counts, segments, times and elevation.
- Validate point counts, segmentation and time fields, not only locations.
Vendor extensions, times, sensor data and segmentation may change; a map image does not replace the GPS records.
Identify waypoint, route and track roles
Inspect element types rather than treating every imported object as the same path.
Inspect segment breaks and recording provenance before joining tracks.
Source for these steps:Topografix · GPX 1.1 Schema Documentation / QGIS Project · Opening Data
Review location and time before sharing
Review recorded locations and timestamps and prepare only the required sharing extent in a copy.
Compare start/end points, segments, times and point counts at the destination.
Source for these steps:Topografix · GPX 1.1 Schema Documentation / QGIS Project · Opening Data
Related-format differences
| Format | Main role | What to check |
|---|---|---|
| GPX track | Recorded path | Segments/times |
| GPX route | Route points | Routing behavior |
| KML / GeoJSON | Other geographic data | Attribute/time preservation |
Handling and security
Tracks can reveal homes, workplaces and travel times; inspect endpoints/timestamps and export only the intended public extent.
Questions and answers
Does it contain a map image?
Usually it holds records; the app supplies the background map.
Are routes and tracks identical?
Distinguish planned routes from recorded points.
Does it always include time?
Time and elevation may be absent.
Which layer should I choose after GPX import?
Choose waypoints, routes or tracks according to the stored content and purpose.
Can every GPX provide accurate speed?
Check times, sampling and GPS errors; without time data, elapsed-time speed is unavailable.
Format facts: name, steward and MIME type
- Formal name
- GPS Exchange Format
- Steward / specification
- Topografix
- MIME type
- Depends on the producer or server; an extension alone does not establish a MIME type.
Primary and official sources
- Official documentationGPX 1.1 Schema Documentation
Defines waypoints, routes, tracks and WGS84 coordinates.
Topografix · Link checked: - Official documentationOpening Data
Load vector and GPX data as layers.
QGIS Project · Link checked: