gpx3.4 KB

GPX — Track Split Into Two Segments by a Pause

The same 24 points split into two `trkseg` elements with a ten-minute gap between them — what a receiver writes after a stop or a signal loss. Tools that concatenate segments without noticing the boundary report a moving average dragged down by a pause that never happened on the move.

Geospatial Time-series data Error handling

Preview — first 50 linesgpx

<?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>
  <trk>
    <name>Coast Road run with a stop</name>
    <trkseg>
      <trkpt lat="47.064024" lon="-12.482008">
        <ele>12.1</ele>
        <time>2026-01-01T09:00:00Z</time>
      </trkpt>
      <trkpt lat="47.066181" lon="-12.478086">
        <ele>18.9</ele>
        <time>2026-01-01T09:00:15Z</time>
      </trkpt>
      <trkpt lat="47.068297" lon="-12.474186">
        <ele>24.8</ele>
        <time>2026-01-01T09:00:30Z</time>
      </trkpt>
      <trkpt lat="47.070538" lon="-12.470269">
        <ele>30.5</ele>
        <time>2026-01-01T09:00:45Z</time>
      </trkpt>
      <trkpt lat="47.072646" lon="-12.466428">
        <ele>36.7</ele>
        <time>2026-01-01T09:01:00Z</time>
      </trkpt>
      <trkpt lat="47.074851" lon="-12.462489">
        <ele>41.5</ele>
        <time>2026-01-01T09:01:15Z</time>
      </trkpt>
      <trkpt lat="47.077037" lon="-12.458586">
        <ele>46.1</ele>
        <time>2026-01-01T09:01:30Z</time>
      </trkpt>
      <trkpt lat="47.079139" lon="-12.45468">
        <ele>49.4</ele>
        <time>2026-01-01T09:01:45Z</time>
      </trkpt>
      <trkpt lat="47.081317" lon="-12.45079">
        <ele>53.1</ele>
        <time>2026-01-01T09:02:00Z</time>
      </trkpt>
      <trkpt lat="47.083558" lon="-12.446942">
        <ele>56.3</ele>
        <time>2026-01-01T09:02:15Z</time>
      </trkpt>

… 112 lines total — download for the full file.

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
Tracks: 1
Segments: 2
Trackpoints: 24
Gap Seconds: 600
Has Elevation: true
Has Time: true

Testing contract

Expected to pass

Scenario: Compute moving time and average speed over the track.
Expected result: The 600-second gap between segments is excluded from moving time; a tool that ignores segment boundaries reports a duration around 945 seconds instead of 345.

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 — Track Split Into Two Segments by a Pause” is a deterministic Novus Examples fixture for Geospatial, Time-series data, Error handling. 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-track-multi-segment.gpx") as f:
    gpx = gpxpy.parse(f)
print(sum(len(t.segments) for t in gpx.tracks), "segments")