GeoPackage to GPX Converter
Export database track vectors as GPX files.
Export GIS data back to navigation devices. This upcoming translator extracts coordinate lines from database tables and converts them into standardized GPX XML track logs.
Drag file here to convert, or select file
Supported file extension: .gpkg • Max 50MB
Specification Rules
- Load custom routes designed in GIS software onto standard GPS navigators
- Import facility boundary lines into mobile navigation systems
- Convert regional maps into simple path tracking logs
- Table layers must represent coordinates in sequence order (lines or points)
- Strictly outputs points, tracks, or route files based on database geometry
- Advanced database table relationships cannot translate to XML properties
GDAL Direct Equivalent Terminal Command
When to use this conversion
Convert when GIS-edited routes or waypoints need to upload to a GPS device (Garmin, smartphone GPS app) or a fitness service (Strava, Komoot) that consumes GPX. Useful for hand-designed running routes or off-trail navigation tracks.
Technical Details
GPX is typically 1.5–2.5× the size of the source GeoPackage layer. XML markup inflates every coordinate; expect a 1 MB GeoPackage track to become a 2 MB GPX.
Common Errors & Fixes
- Polygons silently dropped: GPX accepts only Point and LineString. Fix: convert polygons to their boundary lines first with ST_Boundary in QGIS or ogr2ogr SQL.
- CRS not WGS 84: source layer in a projected CRS. Fix: ensure GeoPackage layer reprojects via -t_srs EPSG:4326 during conversion.
- Standard attribute mapping wrong: "elevation" column not mapped to <ele>. Fix: rename the column to match GPX schema before conversion.
- Output file accepted by GPS device but tracks not visible: track has no name. Fix: ensure each track has a non-null "name" or "trk_name" attribute.
Alternative Tools
- QGIS: select features, then File → Export → Save Features As → GPX
- ogr2ogr CLI: ogr2ogr -f GPX output.gpx input.gpkg layer_name
- gpsbabel for converting through intermediate formats with rich attribute control
- Custom Python script with gpxpy for full attribute mapping
Frequently Asked Questions
What geometry types does GPX accept?
GPX files only accept Point and LineString geometries. Polygon coordinates must be converted to boundary lines to export successfully.
How are track names assigned?
The converter matches specified columns in the source database to assign track names automatically.
Will coordinates be reprojected?
GPX explicitly requires standard coordinates. Coordinates are implicitly reprojected during the extraction.