• Route planner
  • My activities
  • Blog
  • FAQ
Instagram Buy me a coffee
Connect with Strava
All posts

Gravel routing: most roads don't say what they're made of

12 November 2026

Also available in: Deutsch · Français · Nederlands

If you ride gravel, you know the feeling: the route looked great on the map, a nice thin line through the fields, and in real life it's either fresh tarmac or a rocky ditch you have to walk down. Gravel routing is hard, and the main reason is surprisingly boring. Most roads on the map don't say what they're made of.

The missing surface problem

RouteCycle, like most cycling apps, uses OpenStreetMap for the road network. In OpenStreetMap, the surface of a road is a separate tag called surface: asphalt, concrete, compacted, fine gravel, gravel, dirt, grass, sand and so on.

The problem is that this tag is optional, and on a huge number of roads nobody has added it. In some countries it's well mapped. In others it's missing on most roads. The United States is a good example: most roads there have no surface tag at all, so a road that looks perfect on the map can turn out to be a dirt road in real life, or the other way round.

Without a surface you also usually don't have the other useful tags: smoothness (how rough it is), tracktype (how solid a farm or forest track is), or whether a track is even open to bikes.

For a road bike, the safe assumption for an untagged road is "probably paved". For a gravel bike that assumption is useless. Half of what you want to find is exactly those untagged tracks.

Working out the surface when nobody tagged it

So a big part of building gravel mode was filling these gaps. There's no single trick. It takes several kinds of evidence, and a lot of algorithms to combine them:

  • The road type itself. A track through a forest is very likely unpaved; a residential street in a town is very likely paved. On its own this is a guess, but a useful starting point.
  • Neighbouring roads. Surfaces tend to continue. An untagged piece of road between two gravel sections is probably gravel too. A short untagged link in the middle of an asphalt road is probably asphalt.
  • Imagery and machine learning. There are machine learning models that look at street-level photos and satellite imagery and classify what the road surface looks like. They're not perfect, but they cover millions of kilometres that no mapper has ever tagged.
  • Other tags. When a road has tracktype or smoothness but no surface, those still say a lot about what you'll ride on.

Each of these is wrong sometimes. Together they're right much more often than any of them alone. And whenever a mapper adds a real surface tag, it wins over every estimate.

Rideable gravel vs "gravel on the map"

Knowing the surface is only half the problem. The other half is that a lot of things that look like a gravel track on the map are not rideable on a gravel bike: technical MTB trails, hiking paths, firebreaks straight up a hill, steep loose descents.

Gravel mode in RouteCycle tries to stay off those. In practice it means:

  • it looks for real unpaved surfaces first (gravel, compacted, dirt tracks) and uses tarmac mostly to connect them,
  • it avoids technical trails, footpaths, firebreaks and steep loose descents,
  • it keeps busy roads out, the same as road mode,
  • the ride time estimate uses gravel speeds, not road speeds.

Every route, in both road and gravel mode, shows its paved and unpaved split right next to the distance and the ascent. So you can see before you go whether "gravel" means 70% unpaved or 15%.

It's still a work in progress

I'll be honest: this is the part of RouteCycle where the map data limits me the most. In a well-mapped area gravel routes are good. In an area with almost no surface tags, the estimates do most of the work, and they can be wrong.

There are two ways you can help:

  1. Report bad routes. If gravel mode sends you down something you'd never ride, right-click the map to copy the coordinates and send them with the feedback button. That's the most useful feedback I can get.
  2. Fix the map. If you know the surface of a road near you, add it in OpenStreetMap. It takes a minute and it helps every cycling app, not only this one. I explain how in why some roads look wrong on the map.

To try gravel mode, open the route planner, switch the bike type to Gravel, and pick a start and a distance. No account needed.

Read next

  • Why some roads look wrong on the map, and how you can fix them
  • How do you know a road is quiet? Where cycling traffic data comes from
  • How hard is this ride? Reading the climb chart

Want a quiet ride from your door? Pick a start and a distance, and RouteCycle builds the loop.

Open the route planner
FAQBlogRoutesTerms & ConditionsPrivacy Policy