SummitGPX Docs

Route Versions

Route versions provide a history of changes, allowing organisers to track updates and maintain a record of how a route has evolved over time.

What are Route Versions?

A route version is created whenever a new GPX file is uploaded to an existing route.

Each version contains its own:

  • GPX file
  • Route statistics
  • Elevation profile
  • Checkpoints
  • Update notes

The latest version is automatically displayed on the public route page.


Why use Route Versions?

Route versions help organisers:

  • Track route changes over time
  • Keep a record of previous uploads
  • Provide transparency when routes change
  • Maintain a clear audit trail of updates

This is particularly useful when routes are updated multiple times before an event.


Viewing Route History

Open the route and navigate to the route version history.

The version history displays:

  • Version number
  • Upload date and time
  • User who uploaded the version
  • Update notes
  • Key route statistics
Screenshot of the SummitGPX route version history list

This allows you to quickly see what has changed between versions.


Comparing Versions

When reviewing route history, compare:

  • Distance
  • Total ascent
  • Total descent
  • Checkpoint locations
  • Update notes

This can help identify significant route changes before they are published to runners.


Public Route Pages

Public route pages always display the latest published route version.

When a new version is uploaded:

  • The route page is updated automatically
  • Route statistics are recalculated
  • Elevation profiles are regenerated
  • Checkpoint information is updated

Runners do not need a new route link.


QR Codes and Embeds

One of the key benefits of SummitGPX route versioning is that existing sharing tools continue to work.

When a route is updated:

  • Existing QR codes remain valid
  • Existing embed codes remain valid
  • Public route page links remain unchanged

This means organisers can confidently update routes without needing to redistribute links or replace printed QR codes.


Best Practice

When uploading a new route version:

  • Add clear update notes
  • Review the route map before publishing
  • Check route statistics for unexpected changes
  • Confirm checkpoints are displayed correctly

Keeping accurate version history helps runners understand when and why routes have changed.