Elevation Profiles

Every SummitGPX route includes an elevation profile linked to the route map. Runners can use it to understand climbs, descents, checkpoints and the overall effort of the course.

What the Profile Shows

• Elevation changes across the route.
• Total ascent and total descent.
• Highest and lowest points.
• Checkpoint markers where checkpoints exist.
• The selected point on the map as runners move across the profile.

Elevation Sources

SummitGPX uses the original GPX elevation when it is complete and useful. If a GPX file has missing, flat or unreliable elevation, SummitGPX can generate elevation from SummitGPX Core terrain data.

The route page shows whether the elevation came from the original GPX file or was generated by SummitGPX.

Terrain Data

Generated elevation uses terrain data for the route area. If the required terrain data has not been prepared before, SummitGPX may need extra processing time during upload. Later uploads in the same area are usually faster.

When SummitGPX generates elevation, it keeps the original route geometry and replaces or adds elevation values. The course line itself is not redrawn by the terrain process.

For pre-upload elevation checks and repair, use the GPX Health Check workflow.

Ascent and Descent

Ascent and descent totals are calculated from the route profile and may differ from watches, planning tools or mapping platforms. Different services use different elevation sources and smoothing methods.

SummitGPX also reduces obvious terrain noise so ascent and descent figures are more useful to runners and organisers.

Interactive Profiles

Runners can move along the profile and see the matching location on the map. This makes it easier to understand where climbs, descents and checkpoints occur.

Checkpoints and Playback

Checkpoint markers appear on the elevation profile when checkpoints are available. This helps runners plan pacing, food, water and cut off management.

Checkpoint labels on the chart are linked to the map. Hovering or selecting a checkpoint marker highlights the related point, including repeated checkpoints such as C2/C6 on loop routes.

On Pro routes, playback can move through the map and profile together so runners can preview the route progression.

Best Practice

• Review the elevation profile after every upload or route update.
• Check for unusually high or low ascent totals.
• Run the GPX Health Check if the source file has suspicious elevation.
• Review checkpoint positions against the profile after route edits.
• Use the Typical Organiser Workflow before making the route public.

Frequently Asked Questions

Why is the elevation different from another platform?

Different platforms use different elevation models and calculation methods. Some use device barometer data, some use map terrain data and some smooth the profile differently.

Does SummitGPX change my route line when generating elevation?

No. Generated elevation adds or replaces elevation values for the existing route points. It does not redraw the route.

Why did ascent change after a route update?

Changing the route line, replacing elevation data or restoring a version can all affect ascent and descent values.