SummitGPX Help Centre

Understanding GPX

How SummitGPX processes route files

Follow an import from validation to the public route and downloads.

SummitGPX turns a supported file into a course map, statistics, elevation profile and current downloads. This happens within the event you selected.

What happens during import

  1. Validation: SummitGPX checks the file, size, route data and account capacity. It needs at least two usable course positions.
  2. Conversion: KML and FIT sources are converted into GPX route data. GPX tracks are preferred to route points when both exist.
  3. Elevation: useful original heights are retained; unsuitable or missing heights can be generated from terrain. New terrain areas may need background processing.
  4. Metrics: distance, ascent, descent, high/low points and the profile are calculated.
  5. Checkpoints: suitable named GPX waypoints can be imported on initial route creation. Review them before sharing.
  6. Serving: the hosted page and eligible embeds/downloads use the processed course once ready.

Your review is still needed

Processing cannot confirm that a course follows the intended race line or that an aid station is open. Check direction, line, elevation and checkpoint information, then test the download runners will receive.

When the course changes

Replace or edit the existing route to keep its public link. The latest processed version becomes current, while accessible version history records earlier courses. Checkpoint matching and split points need review after geometry changes. Runner emails require a separate explicit send.