City Run — 10 km

Running · 9.99 km · 2 m gain · 52m · 1,600 points · 158 KB

About this route

A flat 10-kilometre loop along a city riverside, the kind of route you would run before work. The pace holds steady with only gentle rises over the bridges. It is a clean baseline for checking distance, moving time and average pace on an easy effort.

This route follows real roads and paths in Amsterdam city loop, 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

Running auto-detection and a steady average pace with little elevation.

What's inside

1,600 track points
1 track segment
timestamps (52m)
elevation (2 m gain, 2 m loss)
158 KB · GPX 1.1

File preview

First 20 lines of city-run-10km.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>City Run — 10 km</name>
    <desc>Sample track for gpxviewer.app — Baseline running file — steady pace on flat ground. The route follows real public roads and paths in Amsterdam city loop, 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="52.352147" minlon="4.868857" maxlat="52.370446" maxlon="4.916651"/>
  </metadata>
  <trk>
    <name>City Run — 10 km</name>
    <trkseg>
      <trkpt lat="52.367610" lon="4.904087"><ele>1.5</ele><time>2024-06-01T07:00:00Z</time></trkpt>
      <trkpt lat="52.367579" lon="4.904010"><ele>1.5</ele><time>2024-06-01T07:00:02Z</time></trkpt>
      <trkpt lat="52.367548" lon="4.903932"><ele>1.2</ele><time>2024-06-01T07:00:04Z</time></trkpt>
      <trkpt lat="52.367562" lon="4.903860"><ele>1.0</ele><time>2024-06-01T07:00:05Z</time></trkpt>
      <trkpt lat="52.367601" lon="4.903793"><ele>1.0</ele><time>2024-06-01T07:00:07Z</time></trkpt>
      <trkpt lat="52.367640" lon="4.903727"><ele>1.0</ele><time>2024-06-01T07:00:09Z</time></trkpt>
      <trkpt lat="52.367680" lon="4.903661"><ele>1.0</ele><time>2024-06-01T07:00:11Z</time></trkpt>

Common questions

What activity type does this detect as?

Running — its average speed sits in the running band, so the viewer selects running metrics and pace.

Why is the elevation gain so small?

It is a flat riverside loop; only the bridge crossings add a little climbing, which is what the 2-metre hysteresis filter keeps.