To follow a GPX line off-road without rerouting, load it as a track, not a route, into an app that shows the line as drawn and warns you when you leave it instead of recalculating. Prepare the file at home: confirm it is a track, trim it, split long days. Then mount the phone where a glance is enough.

That sounds obvious until a navigation app takes your carefully drawn forest loop and sends you down the county road beside it. Here is why that happens and how to stop it.

Why road routers break enduro tracks

A router is built to get you somewhere over a network of ways it knows. Give it a file and it will often treat the points as stops, then work out its own path between them. Off-road, that goes wrong in three ways.

None of these apps is broken. They are doing the job they were built for, and a trail line is a different job.

Track vs route: what the GPX file holds

The GPX format has two different ways to store a line. The GPX 1.1 schema defines a track as “an ordered list of points describing a path” and a route as “an ordered list of waypoints representing a series of turn points leading to a destination”. One is the line itself. The other is a set of turns that an app is expected to connect.

Track Route
Tag in the file trk rte
What it stores The line, point by point Turn points to connect
What a router does with it Many apps show it as drawn; some convert it Recalculates between points
Good for trails Yes Only if the points are very dense
Typical source A recorded ride, a club file A road trip planner

If you are not sure which you have, open the file in any text editor and search for <trk> and <rte>. Our GPX track vs route guide goes into the export settings of common planners.

What line-following does instead

Line-following skips the calculation. The app draws your line on the map, gives you turn hints along it, and raises an off-route alert when you drift away from it. That is all, and off-road it is what you want.

In Ridekin, an off-road GPX line is followed exactly as drawn. It is not snapped to roads and there is no rerouting, because there is no route planner behind it. If the alert fires, ride back to the line or stop and decide with the group. The line is on your phone, so following it keeps working without a phone signal.

What it does not do matters just as much. Ridekin has no trail database and no legality check. It does not know whether the line crosses private land, a closed bridleway or a nature reserve. It follows the file you gave it.

Preparing the GPX at home, step by step

  1. Get the track, not the route. Ask whoever made the file for a track export, or use your own recording from a previous ride.
  2. Check the file. Search it for <trk>. If you only find <rte>, export it again from the planner as a track.
  3. Trim the ends. Cut the bit where someone recorded the drive to the café. The line should start where you unload.
  4. Simplify very large files. A recording with a point every second can carry tens of thousands of points. A tool such as the GPSBabel simplify filter reduces the count while keeping the shape.
  5. Split long days. One file per loop, plus a short file for the way back to the van, is easier to manage than one 200 km file.
  6. Check access. Look at every section that is not an obvious forest road and confirm it is open to motorcycles. The Tread Lightly principles call this “Educate yourself”.
  7. Send it the night before. Everyone imports at home on Wi-Fi, so nobody is downloading at the trailhead.

Phone mounting and how to read the line

Mount the phone on the bars, not the tank bag, so the line sits in the same glance as the trail. On a single-cylinder bike, a mount with a vibration damper is worth the money. Turn screen brightness up, and if the mount has power, set a long screen timeout so the line is there when you look down.

Read the line at junctions, not in the middle of a rocky descent. With the off-route alert watching the line, you do not need to check the screen every ten seconds. When it fires, the right move is almost always to stop, look, and go back a few metres. For the group side of this, see riding enduro in a group.

From the road

Picture a common version of this story: a rider downloads a club’s 90 km loop as a route file and imports it into a road navigation app the night before. On the day, the app sends the group along a tarmac lane parallel to the first trail section for 6 km before anyone notices. Exported again as a track, the same loop showed every switchback. Nothing about the trail changed; the file type did.

Common mistakes

  • Importing a planner route. The app recalculates between points and the trail disappears. Export a track.
  • Trusting a shared file for access. A line drawn three years ago says nothing about a closure posted last month.
  • One giant file. A full weekend in one track is slow to scroll and easy to follow in the wrong direction.
  • Importing at the trailhead. Do it at home. The enduro pre-ride checklist covers the rest of the night-before list.
  • Chasing the line through the scenery. If you missed a turn, go back to it rather than cutting across.

Sources