Why route distance differs between apps

The underlying number

A GPX line does not carry one compulsory distance total.

The standard GPX structure stores ordered positions for a route or track. It does not require one authoritative total distance for every receiving app to display. An app can calculate the lengths between successive points, use distance values supplied by another recording format, or process the geometry before it reports a total.

That makes distance a result of both the data and the method. Even when two apps receive the same original file, their processing choices can produce slightly different answers. When two exports merely look like the same route, they may already contain different point counts or line shapes.

The headline distance is evidence about the line. It is not the line itself.

Where totals diverge

Geometry and processing both leave a mark.

• Point densityDistance is commonly measured along straight connections between points. Sparse points can cut across the inside of bends and miss detail between samples.
• Smoothing and outliersA service may remove implausible jumps, smooth GPS noise or correct points that appear to stray from the path. Each method changes the line being measured.
• Map matchingA route planner may snap sparse shaping points to its own road or path data. Different maps or routing rules can select different geometry.
• Segments and pausesA recorded track can contain pauses, gaps or separate segments. Apps may include, exclude or bridge those intervals in different ways.
• Stored versus recalculated dataSome activity services accept a distance stream written by a device. Others recalculate from the GPS coordinates they receive.
• Display and roundingUnit conversion, decimal precision and rounding can make equal or near-equal calculations look further apart.

GPS-derived distance generally connects horizontal positions and does not reproduce every rise, dip or small movement across the surface. Elevation gain is a separate calculation, so matching distance totals do not mean that ascent totals will also match.

A fair comparison

Hold the input steady, then inspect the geometry.

1. Source

   Use the same original file.

   Two separate exports can be simplified or generated from different underlying route data.

2. Ends

   Confirm start, finish and direction.

   A short approach, finish spur or duplicated return section can explain more than the calculation method.

3. Shape

   Inspect bends, gaps and shortcuts.

   Zoom into switchbacks, junctions and segment breaks where small geometry changes accumulate.

4. Basis

   Check what each number represents.

   Planned route distance, device-recorded distance and post-processed activity distance are related, but they are not interchangeable.

Decision value

Use the number in proportion to the day.

There is no universal acceptable difference. A small percentage may be irrelevant on a short urban walk and material on a long, time-sensitive route. Investigate any gap large enough to change transport, daylight, water or turnaround planning.

For preparation, favour the file whose visible line matches the intended route and whose source you trust. Keep reasonable margin rather than treating one app's distance as survey-grade truth. If the line itself differs, resolve that before navigation.