Tag trail_visibility: Proposed Improvements for this Descriptive Tag

The Swiss have organized their hiking network in a node like fashion on administrative governmental level. The SwissTopo map shows only routes where there are paths on the ground. They do not show routes where there are just markers. Most of the hiking routes have paths up to the demanding_mountain_hiking sac_scale value.

Not so in Austria or Germany. Hiking paths are managed by local organisations on their own thinking. There is a bit of governance, when tourism agencies want a special seal of quality. These are all paths on the ground. Many of them show in the ÖK50, the official map of the country.

Outside of this managed network, there are lots of paths in OSM that are mountaineering routes, they do not show in any official maps. In OSM they are often tagged sac_scale T6. There are notes in the area, where people that walked by did not see the path. Of course not! This is just a route out of a guide book with hundreds of routes, some blazed, some not, that somebody happened to drop a GPX of his ramblings there. But what can you do? It follows policy up to the letter, trail_visibility=no.

PS: I once argued on the principle of reproducibility. Little interest in that. I must say, I belong to the kind of people, that see paths everywhere. Very useful in remote areas. Not helpful in discussing OSM issues.

It would be kind of disheartening to learn, that these routes can be claimed “trail_visibility=excellent|good” in case the next cairn can be seen from the current one|has to be searched out for" (possibly loosing 100m height?)

This point keeps getting brought up on this thread, but is there anyone who actually uses the tag this way, or thinks that it would be a good thing if people used it this way? Don’t people just mentally fill in the blanks?

For comparison, here is how iD shows them (differences to Wiki highlighted):

Excellent: unambiguous path or markers everywhere
Good: markers visible, sometimes require searching
Intermediate: few markers, path mostly visible
Bad: no markers, path sometimes invisible/pathless
Horrible: often pathless, some orientation skills required
No: pathless, excellent orientation skills required

Effectively the iD tagging scheme has already implemented the suggestion of

This is probably a good idea if it prevents people from tagging every marked trail as good or excellent. The way they’ve done it is not ideal if you ask me, because if you take it very literally, it implies that any path with markers needs to be at least intermediate. I’m just copying it here to show that people probably don’t take the Wiki so literally, nor should they.

A few cairns spaced far apart are only useful on a sunny day and even then the path between the cairns may not be visible and that should be taken into account. That’s why I suggested that

In the real world, ignoring for a moment what the Wiki says, isn’t it more like this?

For comparison, the Wiki page on trailblazed is very explicit that the tag should not be used on route relations. I interpreted “describes trail visibility (not route visibility)” on the trail_visibility page the same way. But it’s perfectly possible that I’m the only one who was interpreting it like this!

But… shouldn’t that be the point of complete documentation? I’m not against trail_visibility being what it is now, but IMO some explanation of it incorporating both a trail surface and markers should be up top and not just in the ratings criteria.

That depends on how well it’s cairned. Silver Creek is an abandoned trail that is somewhat well (informally or many decades ago officially) cairned although there are times when cairns have fallen over or been destroyed be deadfall etc and the trail itself will disappear for hundreds of meters / thousands of feet at a time. IMO not an issue as I’m following a creek so w/e, but I added the following to that track. I suppose in an ideal world I would have tried to find every existing patch of trail and recorded where it started and stopped and made a bunch of segments to illustrate ground truth, but it was my first time doing it and we had a lot of ground to cover with more uncertain terrain ahead.

name=Silver Creek Trail

In this case trailblazed:visibility=intermediate means “next trail marker is sometimes visible and sometimes hard to find” which is true. trail_visibility=horrible means “Often pathless” which I took at the time to be the surface/visibility of the trail/path itself.

If I had to smush them into an overall trail_visibility it wouldn’t be intermediate despite there being some cairns - which is “Path mostly visible”, I’d go with bad “Path sometimes invisible, route partly pathless”. The trail surface is horrible, markers are intermediate, the path as a whole is bad.

It’s worth pointing out that “Path sometimes invisible, route partly pathless” to me doesn’t seem to indicate that it is referring to route relations. I read it as when the path you are on is sometimes not visible the route you are on is hence pathless. There are areas with no trail surface and no markers, which makes it a pathless route at times in my mind - that’s separate from larger routing issues.

On the trail_visibility page it just says This key describes attributes regarding trail visibility (not route visibility) and orientation. Route visibility to me is different from the visibility of the trail, and that’s not explicitly referencing to route relations (which path to take from a path). As we’ve beaten to death, it’s semantics, but if there are semantic differences or lack of clarity they should be addressed directly. There’s very knowledgable people that I’ve asked for help that had a similar interpretation as me in terms of mapping intermittent trails.

One thing I find interesting is a lot of people keep saying that we don’t need a trail_surface_visibility tag because trail_visibility covers that use just fine. trailblazed:visibility also falls under trail_visibility however, and I have yet to hear a strong case made for why marker visibility is more critical than the visibility of the trail surface itself. :slight_smile:

It’s worth pointing out that trail_visibility=no as originally intended was probably meant to be used for paths that had some markers on them, not just for trails that don’t have any visibility. That seems like a case where the shift in meaning of the key has led to unintended consequences.

IMO those should be redone as node_networks with minimal key nodes vs “paths”.

I’m personally against creating paths out of random off-trail GPX recordings. A lot of times there might be a key section to an off-trail route, but the rest is pretty open to personal route finding and can change based on snow levels, etc. Having them there as a path just promotes the creation of more informal trails/erosion and people staring at their phone instead of reading terrain. Probably around half my backpacking is pathless and markerless, but I don’t think it’s appropriate to create an OSM path out of the routes I’ve taken even if they worked well. I’ve deleted a few paths that were pathless and markerless (and happened to have poor routefinding as well) that I’ve come across.

In regards to the principle of reproducibility there’s a big difference between seeing a possible route, and seeing a trail which has been caused by repeated traffic over the same location - that’s the “ground truth” where I would draw the line at making something an informal path vs node network of loosely spread out markers. This is getting pretty off-topic however.

I’ll copy and paste from a discussion elsewhere:

Having routes be a set of numbered waypoints would have some clear upsides:

  • less impact created by people focusing on an arbitrary track and creating a trail where none existed
  • less confusion by people that expect a trail when it shows up in a mapping client
  • clarity that it is meant to be an XC route leading to some location (usually a peak or named feature)

I can easily see this getting out of hand - if people create node networks for every possible navigable path in the backcountry (like how some people create huge cairns to regularly mark a strong flowing outlet to a lake in a remote backcountry basin) the map becomes a cluttered mess of people “finding” routes that have been used for many decades in a fairly similar fashion.

IMO most off trail passes in the Sierra only need a top, a small minority need a bottom… but where is the bottom? it’s hiking up from a lake shore or something, or would that be the nearest trail, or would it be a final push to the ridge where things are steepest and it’s most critical to be “on route”? I would put the passes that need a middle node on one hand, but I’m also experienced at routefinding and others might want a node every couple hundred of feet.

For informal routes I’d be wary of marking cairns (there’s some XC cuts, like Simpson Meadow to East Pinnacles I’ve done three times, differently, none terrible, and encountered a few cairns each time lol) - I feel like there could be a good mentality of putting a few extra nodes on a route with a description field (after this pond turn right to stay on Class 2, don’t go down the grassy ramp for Class 4) but leave someone getting from the top of the pass to that midway point on their own - they can pinball from side to side looking for easier drops on shelves, or drop down more directly if they’re comfortable with simple unexposed climbing

I destroy hundreds of (non-digital) cairns a year and make less than 5. It has to be one weak area of an otherwise strong abandoned trail, or something informal where missing that one non-intuitive spot is a genuine issue of safety. Finger Col ledge being the only Class 2 option out of a Class 4 area felt fair to me (though I knocked down random branching ones below it I built up the existing cairn by the ledge) or the two Class 3 options out of Class 4 drops on Valor Pass I chose to leave the cairns undisturbed as I didn’t encounter any for what up to that point is “walk up, nearly anywhere, from nearly anywhere on the shore of this lake”. There could literally be hundreds of routes for the same off trail pass.

I personally rarely even share waypoints when writing up an off-trail route - I normally describe it and use photos, trying to abstract my experience into something general and being clear where decisions I made felt critical vs arbitrary. For example there’s a LOT of people that always go a certain way around a backcountry lake (10422?) up into Ionian Basin because Secor wrote it that way - the opposite shore worked quite fine and was more direct. :stuck_out_tongue:

I think it’s time to create a topic on this, if there isn’t one existing that can be revived.

@erutan It seems you’ve been reading the original description of trail_visibility on the wiki here Key:trail_visibility - OpenStreetMap Wiki while my proposal for a clarified text is on the wiki talk page here Talk:Key:trail visibility - OpenStreetMap Wiki What do you think of the revised version? Is it better? Can it be improved?

When reading the original text, the reference to both path and markers confused me (and not only me). My first idea was that it makes logical sense to split these into path visibility and markers visibility, but the discussion here convinced me it doesn’t make practical sense. A map user would like to have an idea of what to expect from a path he sees on the map before he decides to take it: how (physically) difficult it is to hike (which sac_scale describes), and how easy it is to follow (not to get lost). With trail_visibility we are trying to describe the last. Here I don’t think it makes any practical sense to separate markers from any other visual clues: anything that helps to follow the mapped trail (the thin dashed line on the map is what I mean by “path” or “trail”) should be taken into account.

Until this discussion, I didn’t know this tag existed, I’ve never added it to the map, and maybe I won’t ever. But I can imagine a hiker would like to have some info on how easy it is to follow the itinerary he planned to follow by following the trail blazes. So trailblazed:visibility only really matters when he has to make a choice between different paths, i.e. at junctions. There it could be useful info (to know how much attention he needs to pay, to know how much time he might need to spend on finding trail markers and on walking down the wrong path, etc.).

Here I don’t think it makes any practical sense to separate markers from any other visual clues: anything that helps to follow the mapped trail (the thin dashed line on the map is what I mean by “path” or “trail”) should be taken into account.

I disagree, there is a difference. If the trail visibility is good and it refers to the physical path, one will expect to see it on aerial imagery, or similarly if it is bad to not see it. People will map accordingly. It should be clear what this refers to, and there should be a way to express whether the trail is visible on the ground

Aerial imagery fails for this. A trail can be very visible on the ground, but due to trees, not very visible from aerial imagery.


I wouldn’t throw aerial imagery in the discussion about on the ground visibility.


Aerial imagery fails for this. A trail can be very visible on the ground, but due to trees, not very visible from aerial imagery.

sure, this is very frequent until you reach a certain height. Still many hiking trails can be seen very well in aerial imagery, also on rocky ground, for the parts that aren’t hidden by canopy, that’s why I mentioned it.

Yes! I agree and that’s why I think Richard’s suggestions are good. That’s very similar to your Solution 1.

I think they’re both equally important because the two combined make it easier to follow the path/trail.

I have nothing against breaking down trail_visibility further into trailblazed:visibility and trail_surface_visibility. It could be useful for renderers, they might want to show an indistinct but well-signposted path differently from a well-worn but unmarked one. It’s just that I can’t see myself using trail_surface_visibility much: we’re debating edge cases here but for the vast majority of paths I imagine the value will be identical to that of trail_visibility.

That is also how I see it. I think it all boils down to the question what the key is going to be used for. What I have in mind is that hiking apps can use it to show a warning message such as “the planned route leads over faint and indistinct paths and requires good navigation skills”, general-purpose pedestrian routers can avoid them and renderers can show them less visibly. Practically, what matters most to me is if I’m going to get lost, especially if the weather takes a turn for the worse (which is when trail visibility becomes most important.)

This is directly related to the navigation skills required. (It doesn’t take navigation skills to follow a well-marked path even if it’s not visible on the ground.)

This is better, and essentially describes a path_visibility replacing the original intention of what I’d call trail_surface_visibility.

The key is not about route visibility (how easy it is to choose the right trail at a trail junction)

Route visibiliity sounds strange - I would change it to routing (and mention the more formal term route relations). Pathless paths are often called routes as a route is just the specific path you are doing or want to do regardless of any physical conditions around it, where routing is trying to get from one place to another. This really has very little to do with the trail, and more to do with junctions & signposts as the parenthesis makes clear. It could be worth adding a link to

Path sometimes invisible, route partly pathless

Here you are using the definition of route I am referring to - unless this somewhat means that routing between paths is mostly pathless? That doesn’t make any sense to me. Using the word route does not automatically make something about routing, which seems to confuse people that are used to thinking about general map routing.

trail_visibility=no can be useful to indicate that a route is passable, but no path is visible.

This is awful. I can literally make hundreds of routes that contain “passable” terrain to the same location - do we really want OSM full of paths that are just “passable terrain”? See Tag trail_visibility: Proposed Improvements for this Descriptive Tag - #80 by erutan

Is there a formal movement away from using “ground truth” to map paths? I had thought this was a core tent of OSM, but perhaps I’m wrong.

If the overall path visibility is “no” then it should be a node network of digital “markers” to keep people on key points or decisions. IMO it is no longer a path, by definition it is “pathless”. If someone can’t routefind on their own they shouldn’t just be staring at a random person’s GPX track creating new trails by packing use on a concentrated area. If nothing else they will never be accurate enough to truly routefind in semi-technical terrain (even ± 3 meters can get you in trouble). I guess we could make a highway=pathless lol

Doesn’t the original definition of trail_visibility (which was accepted at the time) also help when trying to find an intersection? If you have no markers but an excellent clear trail surface junctions are straightforward, if you have no trail surface but a lot of markers and a larger marker at a junction (plus further markers heading in more directions) junctions are straightforward. Is there a clear argument as to why only the latter is important and the first case isn’t?

In terms of pure routing, overall path visibility is what matters. Trail surface, marker visibility, and overall path visibility don’t always add up - I gave a recent example where surface visibility is horrible, markers are intermediate, that sort of averages out to the overall experience of the path visibility is bad. I can honestly see an argument for just simplifying things and relying on the new trail_visbility and trailblazed without the related :visibility but at the point where people are arguing that trailblazed:visibility is important I can’t see why trail surface is somehow irrelevant.

It’ll come down to a regional thing, as well as how often people are hiking on abandoned or informal trails.

In areas of heavy vegetation, dirt, or sand you will tend to have paths that express themselves by solely trail_surface_visibility unless you are briefly crossing a streambed or something (wet or dry) in which case there will be markers. In areas of long stone slabs (alpine granite, desert slick rock / sandstone) or consistent snow/ice coverage paths will tend to be driven by markers. In the past few weeks I’ve hiked on areas that were excellent on one and no on the other, and vice versa.

One interesting case are trails that have a good surface visibility, and are occasionally marked where surface visibility is poor so the overall visibility of the path is still excellent. In that case I think just having trailblazed=cairn, trail_surface_visibility=good, and trail_visibility=excellent would tell the story pretty clearly - you will lose the trail at times, but if you look for a marker you can find yourself back on the path again.

In the past few weeks I’ve also hiked on multiple pathless paths that I created from my own routefinding, but that I think are not appropriate for OSM or any general use mapping. I shared some screenshots of my personal waypoints with a local that enjoys off-trail, and he may share them with people he knows and trusts, etc and that’s fine but I wouldn’t put them up as a “path”. His “route” will be slightly different from the one I had taken as we have difference preferences for terrain, directness, exposure, etc… that’s part of the fun IMO.

I just deleted a path (after reaching out to the creator) that looked like it could be a path using imagery (it followed a wash and some game trails) but in reality was no stronger or weaker than many areas around it. It also violated the LNT off-trail ethos of the area it was in as some of those game trails that were more direct had living biological crust around hoof prints, so I ignored it and kept to washes, but was curious if it actually had some historical basis. It didn’t.

That said tracing old jeep roads or tails based on imagery vs relying on a bunch of smoothed GPX tracks or old USGS lines makes sense.

1 Like

Yes, in my opinion, when trail_visibility is a combination of markers and surface, there are only very limited use cases for entering a path with trail_visiblity=no into OSM at all. We could add a warning about ground truth and verifiability to the entry for the no value.

1 Like

One thing that I’ve found useful and has come up in the #trails channel in slack is using node networks for these routes that are pathless. I think node networks cover the limited use cases while being more true to the spirit and skills required.

This is already a commonly accepted practice in the general alpine off-trail community (don’t share tracks but waypoints, don’t create new trails, etc). While I personally think the proliferation of acronym routes is a bit overdone and I think defeat the purpose of XC, this image is an example of how a “route” can be loosely described https://andrewskurka.com/wp-content/uploads/kchbr-map-11x17-scaled.jpg

I’ve done portions of that independently, and the marker saying to keep on the W shore of South Guard lake is poor advice early season when there’s steep snowbanks along it, but that’s the nature of routes and why people should be able to improvise based on conditions. If “connecting the dots” is too hard for them, they should stick to paths or do simpler routes until they have that skillset.

I had to look that up. There are quite some Silver Creek Trails on OSM, I found this, Earlier today, I found a different one, but this seems just approriate as well.

I am in awe about the vastness of wasteland that is on offer in the US! Do the USGS references say, that the trail is officially sanctioned as something existing on the ground? Mooving troops? What would be the reason?

West of the rockies the US has a lot of amazing wilderness - there’s a lot of truly wild (and gorgeous) land to explore. East of there I’d say there’s more wasteland, or at least cattle ranges and farms heh.

That particular trail appears on USGS maps, and was maintained at one point but the lower elevations of Sierra NF were more heavily used in the past when more people used pack animals, the area has a lot of abandoned trails due to lack of funding and lower use (most recreational backpackers want to get to sub-alpine or alpine environments), I’m not sure if it was part of the old cavalry trail network (they’d mostly run out shepherds that were responsible for the decimation of a lot of the high meadows over a century ago).

We did it on day 8 of a 10 day trip crossing over to the big Margaret lakes area from a trailhead on the eastern side of the range, improvising the ridge Sharktooth mountain as a pass (the pass we were planning on using had really sketchy loose large talus) and then over Sharktooth Lake Pass (which is now completely pathless but was a trail many decades ago, aside from the very occasional informal cairn and two cut logs we saw one of which was rotting).

Here’s a junction sign along it lol

Was going to add a photo of an old blazed tree and about as strong as the trail got next to it, but I can only embed one photo per post. :slight_smile:

I’m not pointing fingers in any particular direction, however, I’ll say I am personally not a fan of the word “wasteland.” At least for anywhere on Earth. Even nuclear waste dumps, toxic landfills and vast deserts have something to teach us…to offer to either some living thing or greater knowledge for humanity.

We might discover other (potentially habitable?) planets in our present or future and declare some of them “less desirable for potential human habitation,” but really, calling anywhere “wasteland” is pretty harsh.

I hike and camp (and love) wilderness. These are some of the most important places we have. It’s nice to see the respect for history and mapping (and knowledge of environments…) in this thread, but…“wasteland?” Really?

If English is not your first language, that is something that might be mentioned, as I am constantly amazed by the English-as-a-second-language (or more!) usage I see in this project. (Thanks to all who study English! My mother was an ESL teacher for 45 years). If you mean “wilderness” or “wild and untamed land,” the w-word “wilderness” is much preferred (by me, anyway) to the w-word “wasteland.” Thanks.

Yeah, he’s from Austria as he said earlier in this topic - I assumed he meant desolate or undeveloped and wasn’t going to call him on it (not pointing fingers, but it’s pretty clear who you were referring to heh). Europe is heavily developed and doesn’t have much true “wilderness” though it has some incredible mountain scenery - you can’t really dispersed camp in many mountain areas, many valleys have villages in them, etc.

I have a friend that used to manage a small ranch in Idaho who had some guides in the Swiss Alps ask where he was from. He was like, pssh, Idaho is embarrassing next to the Alps but they got super excited and mentioned they go to Idaho for a month every year to have actual “wilderness”. I’ve seen similar reactions in Germans when we drove through long stretches of untamed forest in BC (well aside from the clearcut sections).

Thanks for your reply.

True wilderness is certainly a wonder to behold!