That’s type=superroute

Thanks for that. I had a quick look the other day but they don’t appear to come through my osm2pgsql imports. I need to investigate some more.

Generally speaking OSM doesn’t have “book only routes”

If only. In the Highlands I see many usually taken from some obscure only published in German guides. Or someone’s itinerary for a walk. They tend to be marked LWN, so I’ve long since given up putting them on my map.

In a similar vein. We also get an occasional spate of someone’s wildcamp spots appear as tourism=camp_site along the WHW (for example),

Maplibre

Thanks for that too. Interesting bunch of stuff.

In my area we have a number of relations of the form: “Cape Wrath Trail (Letterewe - Carnmore - Larachantivore)”. But none with just Cape Wrath Trail. (Hmm can you have a super-relation?) And this being Scotland there are no signs, at all. It’s not a national trail, not adopted by any official body. Hence in places there are multiple routes for a variety of reasons.

As a renderer it gets tricky to work out how frequently to put in route names that work for everything. Allow mapnik to overlap text and you get a mess. Not allowing overlap, or layer ordering gets compromised, and long names seldom appear. Naming convention isn’t always consistent so pre-processing names for the root trail name needs to cope with the ever changing vagaries of mappers. Not that Ordnance Survey are consistent either, sometimes you get English / Gaelic names, and the other way round.

And then the other day I caught a mapper adding the trail name to multiple paths and tracks which already had a suitable relation. It wasn’t obvious enough in the editor (iD).