way not used by hiking app


the way was not used by the hinikng app.
I found that the key access was not set- I changed it to yes

does this correct the problem now?


There are many many maps and apps that use OSM data, and we have no idea which hiking app you’re talking about.

Most apps would already assume access=yes, so your recent change wouldn’t change the results. Is your app maybe set to cycle mode or something?

What do you mean by “not used”? Is the path not displayed on the map, or not used for routing? There does not appear to be any problem with the mapping, there is nothing unusual about the tagging.

I agree with Viajero Perdido that adding access=yes is very unlikely to fix the problem. Even if an app does not automatically assume foot access is allowed on highway=path, this was already made clear by the existing access tag: “foot=yes”.

As Viajero Perdido said, it might be useful if you said which hiking app you are referring to. It is even possible that it is an app that is not fully maintained and has not updated its data since a year ago, when this path was created. Perhaps unlikely, but without knowing which app it is, it is a possibility.

The App Locusmap (Android) with newest data from openandromaps
The path is visible at the app. Routing profile is walking-SAC1-SHRP routed by BRouter
It is not an alpine path there are steps not easy because of the height difference.

If I change the routing profile to Hiking Alpine-SAC4 it is working with BRouter

The way https://www.openstreetmap.org/way/832929907 is used by Brouter ( walking-SAC1-SHRP )
But it is very narrow with steep slopes, slippery becaus of dry leafs and should only be uses by people who are family with alpine tracks.

There must be any difference between both tracks and the usability should be changed

OK, it is much clearer from your second message. It is nothing to do with access, rather you need to look at the sac_scale tag.

The first path you linked to has sac_scale = mountain_hiking (T2), so it makes sense that the “walking” profile would not use it. The second way you linked to has no sac_scale set, which explains the different behaviour in the router.

More information on sac_scale here:

You may know this already, but BRouter data needs to be downloaded manually, via the standalone BRouter app, before it can be used by BRouter within Locus. (The subscription version of Locus has an internalized BRouter called LoRouter that downloads data automatically.)

BRouter’s web client is great for debugging.