Multi-Segment Run

Running · 13.36 km · 204 m gain · 1h 13m · 1,500 points · 152 KB

About this route

A 13-kilometre run on the paths of Central Park, New York, recorded in three track segments with a pause between each — the pattern you get when you stop the watch at a crossing and restart. It checks that the viewer joins multiple <trkseg> blocks correctly and that the paused gaps are handled in the timing.

This route follows real roads and paths in Central Park, New York, generated with the BRouter engine over OpenStreetMap data. The timestamps are synthetic, so it is a demonstration file rather than a personal recording. Route geometry © OpenStreetMap contributors, ODbL 1.0.

What this file demonstrates

Correct handling of multiple track segments and paused gaps.

What's inside

1,500 track points
3 track segments
timestamps (1h 13m)
elevation (204 m gain, 203 m loss)
152 KB · GPX 1.1

File preview

First 20 lines of multi-segment-run.gpx:

<?xml version="1.0" encoding="UTF-8"?>
<gpx version="1.1" creator="gpxviewer.app-samples" xmlns="http://www.topografix.com/GPX/1/1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:gpxtpx="http://www.garmin.com/xmlschemas/TrackPointExtension/v1" xsi:schemaLocation="http://www.topografix.com/GPX/1/1 http://www.topografix.com/GPX/1/1/gpx.xsd">
  <metadata>
    <name>Multi-Segment Run</name>
    <desc>Sample track for gpxviewer.app — Pause/resume segments test (3 trkseg). The route follows real public roads and paths in Central Park, New York, generated with the BRouter engine over OpenStreetMap data; the timestamps are synthetic and there is no personal GPS recording. Route geometry © OpenStreetMap contributors, ODbL.</desc>
    <author><name>gpxviewer.app</name></author>
    <copyright author="OpenStreetMap contributors"><license>https://opendatacommons.org/licenses/odbl/1-0/</license></copyright>
    <time>2024-06-01T07:00:00Z</time>
    <bounds minlat="40.764333" minlon="-73.982387" maxlat="40.799562" maxlon="-73.948843"/>
  </metadata>
  <trk>
    <name>Multi-Segment Run</name>
    <trkseg>
      <trkpt lat="40.767992" lon="-73.981398"><ele>38.5</ele><time>2024-06-01T07:00:00Z</time></trkpt>
      <trkpt lat="40.768072" lon="-73.981391"><ele>37.6</ele><time>2024-06-01T07:00:02Z</time></trkpt>
      <trkpt lat="40.768151" lon="-73.981410"><ele>36.3</ele><time>2024-06-01T07:00:03Z</time></trkpt>
      <trkpt lat="40.768226" lon="-73.981449"><ele>34.9</ele><time>2024-06-01T07:00:05Z</time></trkpt>
      <trkpt lat="40.768294" lon="-73.981505"><ele>33.2</ele><time>2024-06-01T07:00:06Z</time></trkpt>
      <trkpt lat="40.768350" lon="-73.981581"><ele>32.1</ele><time>2024-06-01T07:00:08Z</time></trkpt>
      <trkpt lat="40.768395" lon="-73.981670"><ele>31.5</ele><time>2024-06-01T07:00:10Z</time></trkpt>

Common questions

How are the pauses treated?

Total duration spans the whole activity including the pauses, while moving time excludes the stopped segments.

Does the map show three separate lines?

The segments are drawn as one continuous track; the breaks are in the timing, not the geometry.