How to tag an overgrown path that is part of a hiking route relation?

While on a hike in the high mountains, I came across a “path” that is part of a hiking route relation and is marked as such on the ground, but that is completely overgrown by mountain pine so it is an impenetrable jungle (you would need a chain saw to get through).
In one way it exists because it is marked (there are painted markings at the beginning and end of it telling you to “turn left/right here”) but on the other hand it doesn’t exist because the path itself is not visible and can’t be walked. I added trail_visibility=no, but that probably won’t stop routing apps from sending hikers on this path… An access tag is not applicable because there is no legal restriction to use the path.

How would you tag such a path so that for hikers using an OSM-based map, it is clear that although marked, it doesn’t really exist and can’t be followed?

Maybe use the lifecycle tagging on it. Instead of highway=path use abandoned:highway=path. Abandoned isn’t quite right as is says the feature visible but it does say it is for things that have fallen into serious disrepair that will take considerable effort to put back into service.

3 Likes

Of course, should have thought of that myself! :blush:

It might be interesting to check with the operator of the route. Maybe the route goes through totally different paths nowadays. Maybe they are (very) late in their maintenance schedule.

Very very likely! I made contact with them some time ago about the Bulgarian E3 long distance hiking route for which they are responsible, but all they had on the location of the route were 1:200,000 paper maps from 1990… :cry:

I wouldn’t use lifecycle tags unless the path really has been diverted. If it is just overgrown, I’d tag it as that.

1 Like

Surely there must be some point at which a path is so overgrown that it can no longer be said to exist? The below description seems have reached that point in my mind.

5 Likes

If it’s part of a recognised route someone will eventually be along with a chainsaw, or take your own :slight_smile:

As a minimum report it to those responsible.

A chainsaw may be a bit extreme, but a pair of secateurs is a standard part of my walking kit.

2 Likes

I think “abandoned” describes the path well: it must have taken a decade or two to be overgrown like it is now, with interlocking 10 cm diameter trunks of adjacent mountain pine bushes. Looks like this (image from Wikimedia Commons)


There is an alternative track that can be easily followed, so I don’t expect that cutting a path where there used to be one has any priority.

2 Likes

I know this has been marked as solved, but just thought I’d add…

I’ve created a wiki page to document the overgrown key. I also found a similar option: the obstacle=vegetation tag.

3 Likes

Please make the overgrown page a link to the obstacle one!

PS: I see, too late for my plea, you already have gone full speed. Too bad, such is life.

I have a similar question about tagging a path that is overgrown with brambles.

The path was traversable, though lots of care was needed to avoid the brambles. How well supported is the overgrown key by routers including Komoot? Basically, I want to tag it in a way that says: “here be brambles!”

Ideally it would be a tag that is detected by QA systems that are connected to the operators’ incident system. In France there is an incident system named Suricate, we’d like at some point to feed it with information from OSM, e.g. “this way is overgrown”, “this bridge is down”, etc

I tagged the path I started this thread for as abandoned:highway=path. Maybe you could tag it as disused:highway=path because you can still get through and it doesn’t need tools to make a new path.

The standard “third party use of OSM data” answer applies, I suspect - you’ll have to ask Komoot directly whether they use that tag. Relatively few (if any) commercial sites are listed at taginfo, and almost none of the data consumers listed there use that tag (yet).

obstacle=vegetation is way more popular and also handled by multiple third parties (like brouter).