GPX — Standalone Waypoints Only
Five `wpt` elements for the towns of the territory, with names, symbols and descriptions but no track or route. It is the GPX equivalent of a point layer, and the third of the three top-level GPX content types.
<?xml version="1.0" encoding="UTF-8"?>
<gpx version="1.1" creator="Novus Examples geospatial fixtures" xmlns="http://www.topografix.com/GPX/1/1">
<metadata>
<name>Kestrel Bay Coast Road</name>
<desc>Synthetic GPS trace over an invented territory.</desc>
<time>2026-01-01T09:00:00Z</time>
</metadata>
<wpt lat="47.064" lon="-12.482">
<name>Kestrel Bay</name>
<sym>City</sym>
<desc>Population 4820, reference KB</desc>
</wpt>
<wpt lat="47.112" lon="-12.3915">
<name>Marram</name>
<sym>City</sym>
<desc>Population 1180, reference MR</desc>
</wpt>
<wpt lat="47.018" lon="-12.551">
<name>Holloway</name>
<sym>City</sym>
<desc>Population 2670, reference HW</desc>
</wpt>
<wpt lat="46.9725" lon="-12.4402">
<name>Ninepin</name>
<sym>City</sym>
<desc>Population 640, reference NP</desc>
</wpt>
<wpt lat="47.0885" lon="-12.6135">
<name>Quillan Cross</name>
<sym>City</sym>
<desc>Population 310, reference QC</desc>
</wpt>
</gpx>
Specifications
- Crs
- WGS 84 (EPSG:4326)
- Encoding
- UTF-8
- Line Endings
- LF
- Seed
- 20260807
- Jitter Sigma Degrees
- 0.000025
- Start Time
- 2026-01-01T09:00:00Z
- Sample Interval Seconds
- 15
- Format
- GPX 1.1
- Waypoints
- 5
- Tracks
- 0
- Routes
- 0
- Has Symbols
- true
- Has Time
- false
Testing contract
Expected to pass- Scenario
- Import the file and compare the points with the town features in the master GeoJSON.
- Expected result
- Five waypoints load with their names and symbols; coordinates match the master territory towns to six decimal places.
What is a .gpx file?
GPX (GPS Exchange Format) is an XML schema for GPS data, storing waypoints, routes, and tracks with coordinates, elevation, and timestamps. It is the standard interchange format for GPS devices and fitness and navigation apps. Track points capture recorded movement over time.
How to use this file
Use an example GPX file to test GPS track parsing, elevation and timestamp handling, and tools that import routes or visualize recorded activity.
How to use this file for testing
“GPX — Standalone Waypoints Only” is a deterministic Novus Examples fixture for Geospatial, Conversion testing, Data import. GeoJSON, GPX, and KML files with points, lines, polygons, and tracks — for testing map tools, route parsers, and geo importers.
Documented properties for this file: seed 20260807 · UTF-8 · LF. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.
Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.
Geospatial fixtures publish one invented territory across formats, with the coordinate reference system and feature counts documented in specs. Convert or reproject and diff against the twin in the same group; edge-case geometries state exactly which assumption they are built to break.
Code examples
import gpxpy # pip install gpxpy
with open("gpx-waypoints.gpx") as f:
gpx = gpxpy.parse(f)
print(sum(len(t.segments) for t in gpx.tracks), "segments")Related files
- gpkgGeoPackage — Aspatial Attributes Table (no geometry column)A GeoPackage holding an `attributes` table with no geometry at all — the standard's own answer to a lookup table you want to ship alongside your layers. Its gpkg_contents row has null bounds and a null SRS, which is what readers that assume every row is spatial trip over.

- gpkgGeoPackage — Three Feature Layers in One SQLite ContainerThe territory as an OGC GeoPackage: an ordinary SQLite database with the three required metadata tables and three feature layers whose geometry columns hold GeoPackage binary blobs. Unlike a shapefile it carries several geometry types, long column names and real typed columns in one file.

- osmKestrel Bay Territory — OpenStreetMap XML TwinThe towns and roads in OSM XML: tagged nodes, three highway ways sharing the junction node at Kestrel Bay, and a route relation over them. All object IDs are negative — the convention for objects that have never been uploaded — so nothing here can be mistaken for real OSM data.

- kmlKML — LineString Placemarks With tessellateThe three roads as LineString Placemarks with `tessellate` set, which tells a globe renderer to drape the line over terrain rather than drawing it as a straight chord. Converters that drop the flag produce lines that tunnel through hills.

- kmlKML — Point Placemarks With DescriptionsFive town Placemarks with plain-text descriptions and no styling — the smallest useful KML and the baseline for the rest of this subcategory. Coordinates match the master territory, so a KML-to-GeoJSON conversion can be diffed against a known answer.

- kmzKMZ — Bundled Icon Referenced by a Relative PathA KMZ whose style points at `files/markers/town.png` inside the same archive. Resolving that relative href against the archive rather than the filesystem is the whole job of a KMZ reader, and it is where extract-then-parse implementations break.

Generated by generation/geospatial.py. Free for any use, no attribution required — license.