A GPX track is a recorded line: thousands of points tracing exactly where someone rode. A GPX route is a short list of waypoints that your app or sat-nav joins up with its own road routing. Load a track when you want to ride the same line; load a route when you want the device to pick roads between stops.

Most GPX trouble on group rides comes from mixing the two up, so the definitions come first.

What is the difference between a GPX track and a route?

The GPX format itself defines them. The GPX 1.1 schema describes a route as “an ordered list of waypoints representing a series of turn points leading to a destination”, and a track as “an ordered list of points describing a path” (Topografix GPX 1.1 schema). A third element, the waypoint, is “a waypoint, point of interest, or named feature on a map”.

In riding terms:

Track Route Waypoint
What it stores The full line, point by point A few turn points One named spot
Typical size Hundreds to thousands of points A handful to a few dozen One
Who decides the roads Whoever recorded or drew it The app that opens the file Nobody, it is a single point
Good for Riding exactly the same way Letting a sat-nav plan between stops Fuel, food, the hotel

The practical difference is who chooses the roads. With a track, the choice was made when the file was made. With a route, the choice is made again by every app that opens it, using its own map and its own idea of a good road.

Why does a track imported as a route go wrong?

Some apps and devices convert whatever you give them into a route, so their navigation can recalculate. To do that, they thin the thousands of track points down to a few via points and let their router fill the gaps. The router does not know why the original rider chose that lane over the main road. It picks what its settings call best.

A rider on the MyRoute-app forum summed up the result: importing a GPX “as a route is chaos but as track it goes well”. The same poster noted the cost of the track option: “you loose the waypoints” (MyRoute-app forum, undated post). Furkot’s help pages describe the same conversion for the Scenic app, which turns imported tracks into routes (Furkot help).

Off-road it gets worse. Routers are built for public roads, so a line through a forest is either snapped to the nearest tarmac or drawn straight across the terrain. An e-MTB forum user described one planner drawing “a dead straight line from one place to another” unless a “Match Route to known ways” setting was turned off (emtbforums).

Which one should you export from your planner?

Most planners can export the same plan as either type. Before you hit export, run through this:

  1. Ask what the receiving app does with the file. An app that follows a line wants a track. A sat-nav that recalculates may accept either.
  2. For a line-following app, export a track. The roads are fixed at export, and everyone sees the same line.
  3. For a Garmin or similar device, check its advice. Rever’s 2019 tips for moving planned rides onto a Garmin recommend the Track export option and switching Auto Recalculate off, because with it on the device ignores the planned line (Rever, 2019).
  4. Off-road, always export a track. A route through trails is an invitation for the router to improvise.
  5. Keep your stops as waypoints. If the app drops them, write the fuel and lunch stops in the group chat as well.
  6. Open the file once before you send it. Load it into the app you will ride with and check the line follows the roads you meant.

How do you share a ride file with friends?

There are two ways, and they suit different jobs. A GPX file dropped into the group chat lets each rider import the same line into their own app. A share link opens in a browser and shows the line on a map, which is better for the rider who just wants to see where you are going, or for someone staying at home.

Either way, send it the night before. Mixed apps are the usual problem. An ADVrider member moving a file between apps found headers “that garmin doesn’t like”, and another concluded that “ideally, you’d each have the identical mapset” (ADVrider, pre-2023). You will not get six riders onto identical maps, but you can give them all the same track. Our pre-ride planning checklist has the rest of the night-before list.

Following a line vs being rerouted: what is the difference on the bike?

A navigation app that reroutes recalculates when you miss a turn. On roads that can help: it finds you a way back. It can also take you somewhere the planner never intended, and on a group ride that means two riders on two different roads.

A line-following app does less. It shows the line, gives a hint before each turn, and tells you when you have left the line. Getting back is up to you. That suits group rides, where the point is that everyone rides the same way, and it suits off-road tracks, where a router has nothing useful to offer.

Ridekin works the second way. You load a GPX, it shows the route line with turn hints and an off-route alert, and it does not calculate a new route. Off-road lines are followed as drawn, not snapped to roads, and there is no trail database or legality check, so confirm access yourself. After the ride, export your own recording as GPX or send it as a share link. For more on this, see how to follow a GPX line off-road without rerouting.

From the road

The MyRoute-app thread above is the short version. Here is the longer one, as an illustration rather than any one rider’s account: a rider plans a ride, exports it, loads it on a different app, and the line that was a careful run of back lanes turns into a few points joined by main roads. Nobody notices until the first junction where the app says straight on and the planner meant left. The fix the MyRoute-app poster landed on was the dull one: import it as a track and accept losing the waypoints. Writing the stops into the group chat covers the rest. If you are heading further out, our off-grid ADV navigation guide and the enduro pre-ride checklist cover backups for when files and phones let you down.

Common mistakes

  • Sharing a route and expecting identical lines. Every app fills a route with its own roads.
  • Exporting a route for an off-road ride. The router will snap the line to tarmac or draw it straight.
  • Not opening the file before sending it. Two minutes on the sofa saves an argument at the first junction.
  • Relying on waypoints surviving. Some imports drop them. Keep the stops in the group chat too.

Sources