Big File — Performance Stress

Cycling · 302.39 km · 6407 m gain · 7h 0m · 25,000 points · 2.5 MB

About this route

A roughly 300-kilometre road loop through the Dolomite valleys around Trento, resampled to a high point density — 25,000 points, about 2.5 MB of GPX. It exists to stress parsing, rendering and replay performance on a large file. Everything should still open and stay responsive.

This route follows real roads and paths in Dolomites valleys near Trento, 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

Parser and rendering performance on a large, dense file.

What's inside

25,000 track points
1 track segment
timestamps (7h 0m)
elevation (6407 m gain, 6407 m loss)
2.5 MB · GPX 1.1

File preview

First 20 lines of big-file-perf.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>Big File — Performance Stress</name>
    <desc>Sample track for gpxviewer.app — Performance stress (~2.5 MB, 25,000 points). The route follows real public roads and paths in Dolomites valleys near Trento, 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="45.900169" minlon="11.08217" maxlat="46.343545" maxlon="11.832527"/>
  </metadata>
  <trk>
    <name>Big File — Performance Stress</name>
    <trkseg>
      <trkpt lat="46.066807" lon="11.122300"><ele>195.0</ele><time>2024-06-01T07:00:00Z</time></trkpt>
      <trkpt lat="46.066798" lon="11.122442"><ele>195.1</ele><time>2024-06-01T07:00:01Z</time></trkpt>
      <trkpt lat="46.066820" lon="11.122596"><ele>195.3</ele><time>2024-06-01T07:00:02Z</time></trkpt>
      <trkpt lat="46.066841" lon="11.122750"><ele>195.4</ele><time>2024-06-01T07:00:03Z</time></trkpt>
      <trkpt lat="46.066863" lon="11.122904"><ele>195.6</ele><time>2024-06-01T07:00:04Z</time></trkpt>
      <trkpt lat="46.066884" lon="11.123058"><ele>195.8</ele><time>2024-06-01T07:00:05Z</time></trkpt>
      <trkpt lat="46.066905" lon="11.123212"><ele>195.9</ele><time>2024-06-01T07:00:06Z</time></trkpt>

Common questions

How large is this file?

About a megabyte, with 25,000 track points — large enough to test performance without being unwieldy.

Should it still be smooth?

Yes. Parsing and replay are designed to stay responsive at this size in a modern browser.