beacen.

GPX fundamentals field answer 007

GPX tracks, routes and waypoints explained

Reading time
6 minutes
Reviewed
Scope
Tracks, routes and waypoints

The short answer

A GPX waypoint is one location. A route is an ordered set of route points that describes an intended journey. A track is one or more segments of densely ordered track points, often representing a recorded or precisely drawn line. Apps may handle all three differently, so the element type affects what imports and how it appears.

The distinction

Point, plan and trace serve different purposes.

<wpt>Waypoint

One latitude and longitude pair. It can carry a name, symbol, description, elevation, time and other optional details.

<rte>Route

An ordered list of route points leading towards a destination. The points express an intended course rather than a recorded history.

<trk>Track

An ordered list of track points, divided into one or more segments. It commonly preserves a detailed trace or planned line.

These definitions come from the GPX 1.1 specification. The format defines the data structure, but it does not force every app to present or use that structure in the same way.

What the order means

A list of places is not automatically a route line.

A waypoint stands on its own. Ten waypoints may identify useful places, but the GPX structure does not necessarily say that they form one journey. This is why a waypoint-only file can open successfully in one tool yet fail to provide a navigable line in another.

Route points and track points are ordered. That order gives the receiving app a direction from the first point to the last. A route may contain relatively few shaping points. An app can decide how to draw or calculate between them. A track often contains more points and can preserve the supplied geometry more closely.

Tracks can also contain separate segments. A segment boundary can represent a pause, a recording restart or a genuine break. Software must decide whether to show that break, join it visually or treat each segment separately.

Coordinates can be identical while structure changes their meaning.

Across apps

The exporting and receiving apps both shape the result.

  • Export choiceA service may offer a route, track or reduced-point export. Choose the option that preserves the line you actually planned.
  • Point reductionAn exporter may simplify a dense line to reduce file size. Fewer points can make bends appear straighter and can alter calculated distance.
  • Optional detailsElevation, time, names and descriptions may be present, absent or stored in extensions. A receiving app may ignore fields it does not support.
  • Several linesOne document may contain multiple routes or tracks. Confirm which line was imported when the source file holds more than one.

beacen accepts a GPX route or track for route navigation. A file containing only waypoints does not provide the ordered line needed for that purpose.

A useful review

Judge the result by its line, not its label.

  1. Open

    Import the original GPX.

    A renamed file or screenshot cannot replace the structured route or track data.

  2. Trace

    Follow the line from start to finish.

    Look for straight shortcuts across bends, unexpected gaps, duplicated sections and the wrong direction.

  3. Compare

    Check key places against the source.

    Confirm that junctions, summits, crossings and the finish sit where you expected.

  4. Prepare

    Complete the normal route checks.

    Review access, conditions and offline readiness before relying on any imported line.

Sources & scope

What this answer is based on.

The GPX standard defines the elements. Export, rendering and navigation behaviour remain implementation choices for each app.

Continue with GPX