GPX

GPX
Name	GPX
Operating system	Cross-platform
Genre	File format

GPX

The GPX format is an XML-based file specification for exchanging GPS-derived geographic data among devices, applications, and services such as Garmin, OpenStreetMap, Google Maps, Strava, and Mapbox. It was created to permit interoperable storage of waypoints, routes, and tracks so that users of devices from manufacturers like Sony, TomTom, Magellan or software such as QGIS, ArcGIS, Garmin BaseCamp, Apple Maps could share pathing information across platforms. GPX files are commonly used in scenarios involving hiking, cycling, geocaching, surveying, and marine navigation.

Overview

The specification defines a schema rooted in XML that represents geospatial items produced by satellite navigation receivers including devices by Garmin and datasets contributed by projects like OpenStreetMap and Wikiloc. GPX was developed in the context of interoperability efforts involving vendors, standards organizations, and open-source projects such as GPSBabel and TrackMaker. Designers aimed to harmonize exchange among formats used in applications like Google Earth (KML), MapInfo (TAB), and AutoCAD (DWG) while maintaining ease of parsing for libraries such as libxml2 and programming environments like Python and Java.

File Format and Structure

A GPX document is an XML tree beginning with the XML declaration and a root element that carries metadata, waypoints (), routes (), and tracks (). Elements commonly include latitude/longitude attributes and child nodes such as , , , and . The schema supports namespaces to interoperate with extensions defined by organizations like Garmin and communities such as OpenStreetMap. Validation is typically performed against an XML Schema Definition (XSD) using tools like xmllint or libraries native to C#, JavaScript, and Ruby.

The format distinguishes between a route—a sequence of routepoints intended for turn-by-turn guidance as used in TomTom and Garmin nüvi—and a track, which is a time-ordered record of a device’s path as produced by receivers made by Trimble, Holux, or smartphones by Apple and Samsung. Time stamps use ISO 8601 and coordinate reference is geographic coordinates in degrees of latitude and longitude on the WGS 84 datum.

Data Elements and Extensions

Primary GPX elements include (author, link, bounds), (waypoint details), (route with ), and (track composed of and ). Optional elements like , , and enable richer semantics. The container has been used by proprietary vendors such as Garmin and by projects like OpenStreetMap to embed device-specific tags, elevation corrections, heart-rate data from Polar or Garmin Forerunner, cadence from SRM power meters, and sensor feeds from Bosch or Bosch eBike Systems.

Extension vocabularies include GPX-specific vendor schemas, the SensorML-style encodings used in environmental monitoring networks, and ad hoc tags that integrate with platforms like Strava and Komoot. Software reading GPX must often be tolerant of unexpected namespaces and foreign elements to preserve interoperability with services such as AllTrails and RideWithGPS.

Software and Tools

A broad ecosystem supports GPX import, export, editing, and visualization. Desktop GIS applications such as QGIS and ArcGIS provide native GPX support, while lightweight utilities include GPSBabel for conversion among formats and Viking or Merkaartor for editing. Web mapping libraries like Leaflet and OpenLayers parse GPX for overlaying routes on tile services from Mapbox, Stamen, or HERE Technologies. Device manufacturers supply utilities—Garmin BaseCamp, TomTom MyDrive—and mobile apps such as Gaia GPS, ViewRanger (now part of Outdooractive), and Strava support GPX exchange. Developer ecosystems include language bindings in Python (gpxpy), Node.js (togpx, gpx-parse), Java (geotools), and .NET (SharpMap).

Interoperability testing uses tools from communities like OpenStreetMap validators and continuous integration pipelines hosted on GitHub and GitLab repositories for open-source parsers and converters.

Applications and Uses

GPX underpins consumer and professional workflows: planning and sharing routes for events such as Tour de France training rides, creating trail guides for organizations like The National Park Service, logging track data for scientific expeditions in conjunction with institutions like NOAA or USGS, and exchanging waypoint collections for recreational activities like geocaching coordinated via Geocaching.com. Emergency response teams associated with entities such as FEMA use GPX exports from mapping tools to coordinate search grids. Photographers use GPX to geotag images in workflows with Adobe Lightroom and ExifTool.

Limitations and Compatibility

GPX’s simplicity and XML verbosity produce larger files compared with binary logging formats used by some Garmin devices, and proprietary vendor extensions can reduce cross-platform fidelity when tools ignore nonstandard tags. GPX is limited to WGS 84 geographic coordinates and lacks native support for complex geometries or rich styling present in formats like GeoJSON or KML. Time precision and accuracy depend on receiver hardware—models by u-blox, SiRF-based devices, or smartphones—so downstream analyses with tools like R or MATLAB must account for sampling bias and timestamp drift.

Despite these constraints, GPX remains widely supported by device vendors, mapping platforms, and open projects such as OpenStreetMap and GPSBabel, ensuring continued utility for route planning, tracking, and data interchange.

Category:File formats