Trail Run — 18 km

Running · 18.44 km · 2525 m gain · 2h 10m · 2,600 points · 263 KB

About this route

An 18-kilometre trail run through steep wooded foothills above Interlaken, climbing and descending repeatedly for well over two thousand metres of gain. Pace stretches out on the sharp pitches and quickens on the runnable descents — a good file for seeing how moving pace and gradient interact on real terrain.

This route follows real roads and paths in Wooded foothills above Interlaken, 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

Pace that visibly slows uphill and recovers downhill, plus meaningful elevation gain/loss.

What's inside

2,600 track points
1 track segment
timestamps (2h 10m)
elevation (2525 m gain, 2525 m loss)
263 KB · GPX 1.1

File preview

First 20 lines of trail-half-marathon.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>Trail Run — 18 km</name>
    <desc>Sample track for gpxviewer.app — Pace variation on climbs — pace slows on the ascents. The route follows real public roads and paths in Wooded foothills above Interlaken, 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="46.519578" minlon="7.903204" maxlat="46.544405" maxlon="7.932961"/>
  </metadata>
  <trk>
    <name>Trail Run — 18 km</name>
    <trkseg>
      <trkpt lat="46.523393" lon="7.915292"><ele>1872.5</ele><time>2024-06-01T07:00:00Z</time></trkpt>
      <trkpt lat="46.523441" lon="7.915357"><ele>1872.0</ele><time>2024-06-01T07:00:02Z</time></trkpt>
      <trkpt lat="46.523493" lon="7.915415"><ele>1868.9</ele><time>2024-06-01T07:00:03Z</time></trkpt>
      <trkpt lat="46.523546" lon="7.915472"><ele>1865.9</ele><time>2024-06-01T07:00:04Z</time></trkpt>
      <trkpt lat="46.523599" lon="7.915529"><ele>1862.8</ele><time>2024-06-01T07:00:05Z</time></trkpt>
      <trkpt lat="46.523652" lon="7.915586"><ele>1859.8</ele><time>2024-06-01T07:00:06Z</time></trkpt>
      <trkpt lat="46.523704" lon="7.915644"><ele>1856.8</ele><time>2024-06-01T07:00:07Z</time></trkpt>

Common questions

Why does the pace swing so much?

The generator makes speed depend on slope — slower uphill, faster downhill — so pace tracks the terrain.

Does it show gradient?

Yes. Running files with real elevation surface average and maximum gradient in the metric set.