Accuracy
The numbers from a recording
Section titled “The numbers from a recording”GPX Explore works only from what the file holds; nothing is invented. Distance is measured from point to point. Moving time, pace, maximum speed, gain and loss follow the rules on Stats: stops are left out, single jumps are ignored, and rises smaller than the recording’s own noise do not count as climbing. A watch that logs a point a second and a receiver that logs one a minute give the same route slightly different distances and climbs, and both differ from what the service that recorded them shows, because every app filters noise its own way.
GPS elevation is often off by tens of meters; a barometric altimeter is better but drifts with the weather. Gain and loss are only as good as the elevation in the file. In a recording that logs a point every second or two, a single height that leaps away from its neighbors for a moment (a fix 20 m low for one second) is left out before the climb is counted. In a sparser file, one wild height (a point at 2,000 m on a coastal ride) adds its climb all the same: select the point and delete it, or replace the track’s elevation with the terrain model’s.
Recording a track
Section titled “Recording a track”When GPX Explore records, with Record a Track or while you ride a route, it keeps only the GPS fixes it can trust. It waits for a good first fix, leaves out fixes that are old or too rough, and drops a fix that jumps off the street and straight back within a few seconds while the phone measured you moving at your own pace. An iPhone’s GPS can do that at a corner or among buildings, and each such jump would add its length to the distance and its height to the climb. While the phone measures you standing still, nothing new is added, and a fix with no measured speed (often a position from Wi-Fi between tall buildings) counts only once it is farther from the last point than its own accuracy: otherwise a few minutes in a store draw a walk of their own. Heights are the iPhone’s GPS heights, noisier than a watch’s barometer, and one the iPhone puts more than 8 m out is left out; the climb is counted by the same rule as any file’s, so the summary, the route card and Apple Health show the same gain.
Elevation for drawn points
Section titled “Elevation for drawn points”Points you draw, trace or add, and Replace Elevation, get their height from our own elevation server at elevationapi.geosq.com: the Mapzen terrain model, worldwide, one value every 30 meters (the same data Geo Elevation uses). This is a model of the ground, not a survey: expect a few meters of difference, more on cliffs, in steep narrow valleys and among tall buildings, and it knows nothing of bridges and tunnels.

Routes, edits and times
Section titled “Routes, edits and times”- Routes come from Apple Maps directions and may not include every trail. Where Maps has no route, the leg is drawn straight and the app says so.
- Simplify and Remove Spikes judge points by geometry and speed; check what they removed on the map, and undo if they took too much.
- Planned times assume a steady pace on the flat, adjusted for grade with Tobler’s hiking function. They are a plan, not a forecast for your legs, the weather or the trail.

