[Tagging] Combining "locked=yes" with various access tags

[Warin]

On 23/2/23 11:29, Andrew Harvey wrote:
> Actually thinking about this in the context of the scenario at 
> https://github.com/graphhopper/graphhopper/issues/2757#issuecomment-1435081431 
> I think we need a tagging solution to indicate that bicycle/foot may 
> bypass the gate rather than having to travel through the gate. Because 
> while in this situation there is a bypass available, other situations 
> there may not be, and some gates may not be so simple to climb 
> under/over.
>
> Using another highway=path to go around the gate feels wrong as there 
> is really just one highway=track here, there is no separate path 
> running alongside it, so mapping it with one feels like mapping for 
> the router. My thoughts:


The locked National Park swing gates I come across all have a bypass 
using bollards (at least most of them use bollards, some have natural 
features that perform the same task). So for these a short path with 
foot=yes, bicycle=yes should free up the navigation for these. I have 
not bothered to map them as I take the view that the road is tagged 
access=private, foot=yes, bicycle=yes. I don't recall if I have tagged 
locked on the se gates. In any case I don't use routing for them - they 
are my local area.

If you must climb over or go under a barrier then I think you are 
subverting the purpose of the barrier.