Scenic Drive — 114 km

Driving · 113.66 km · 2695 m gain · 2h 5m · 3,000 points · 307 KB

About this route

A 114-kilometre scenic drive down California's Highway 1 through Big Sur at road speeds, winding over the coastal headlands for a couple of thousand metres of cumulative climb. The higher speeds trigger driving auto-detection and a driving-tuned heat-zone palette. It is the reference file for the driving metric set.

This route follows real roads and paths in Big Sur, California Highway 1, 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

Driving auto-detection via the 95th-percentile speed and road-speed heat-zones.

What's inside

3,000 track points
1 track segment
timestamps (2h 5m)
elevation (2695 m gain, 2663 m loss)
307 KB · GPX 1.1

File preview

First 20 lines of scenic-drive-120km.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>Scenic Drive — 114 km</name>
    <desc>Sample track for gpxviewer.app — Driving auto-detection and highway-speed heat-zones. The route follows real public roads and paths in Big Sur, California Highway 1, 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="35.846049" minlon="-121.938273" maxlat="36.552558" maxlon="-121.405567"/>
  </metadata>
  <trk>
    <name>Scenic Drive — 114 km</name>
    <trkseg>
      <trkpt lat="36.552001" lon="-121.922700"><ele>59.5</ele><time>2024-06-01T07:00:00Z</time></trkpt>
      <trkpt lat="36.552343" lon="-121.922702"><ele>60.2</ele><time>2024-06-01T07:00:02Z</time></trkpt>
      <trkpt lat="36.552556" lon="-121.922543"><ele>61.6</ele><time>2024-06-01T07:00:05Z</time></trkpt>
      <trkpt lat="36.552555" lon="-121.922117"><ele>62.4</ele><time>2024-06-01T07:00:07Z</time></trkpt>
      <trkpt lat="36.552554" lon="-121.921692"><ele>62.9</ele><time>2024-06-01T07:00:10Z</time></trkpt>
      <trkpt lat="36.552555" lon="-121.921266"><ele>62.0</ele><time>2024-06-01T07:00:12Z</time></trkpt>
      <trkpt lat="36.552556" lon="-121.920841"><ele>61.3</ele><time>2024-06-01T07:00:14Z</time></trkpt>

Common questions

Why does this detect as driving?

Its 95th-percentile speed clears the driving threshold, so the viewer selects driving metrics and colour bands.

Why the 95th percentile and not the top speed?

A single GPS spike can read very high; using the 95th percentile stops one bad fix from mislabelling the activity.