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

[Mateusz Konieczny]

Feb 21, 2023, 15:24 by zeev.stadler at gmail.com:

> I would like the help of the list to clarify the meaning of having a "locked=yes" tag on a barrier node together with some allowed access tags.
>
> The introduction to the "locked" tag wiki page > https://wiki.openstreetmap.org/wiki/Key:locked>  says:
>
>> access <https://wiki.openstreetmap.org/wiki/Key:access>>> =*>>  is used to describe the legal permission to travel through a barrier but does not indicate in emergencies what the physical access is
>>
>
> Therefore, my understanding is that 
> As far as non-emergency routing, the "locked" tag should be ignored.
> A "locked=no" tag indicates that a legal access restriction is not enforced by a lock and therefore could be overcome in case of an emergency.
> A "locked=yes" tag indicates that the legal access restriction is enforced by a lock and therefore cannot be overcome in case of an emergency.
>
In general I agree.

---------------------------------------------------------------------------------------------------------------

It may be nitpicking but I would phrase it "cannot be overcome by just opening it"

Depending on exact barrier it may be relative easy to cross, and depending on
exact emergency, customs and local law barrier may be destroyed by responders,
in some cases quite easily.

In some cases for example gate may be locked by you can get around it easily.



> The "How to map" description in the wiki page seems to assume a gate or a barrier with a simple "access=no". It is not clear with respect to any permitted access methods. 
>
>  For example, barrier node with the following tags:
>
>
>
> tag
> value
> barrier
> gate
> motor_vehicle
> no
> locked
> yes
> bicycle
> yes
> foot
> yes
>
>
>
> I think this tagging says: 
> There is a locked gate that blocks motor vehicles
> There are no access restrictions for pedestrians and bikes
>

I agree but I cannot imagine such barrier.

> This is not the interpretation of other people, as seen in a discussion on a GraphHopper routing issue
>   > https://github.com/graphhopper/graphhopper/issues/2757#issuecomment-1434806229
> There you could also find a picture of such a barrier.
> Please help us resolve the differences
>
That is better mapped by mapping path around barrier, at least in my opinion.

See say https://www.openstreetmap.org/way/1079963925

This can be more easily understood without elaborate hard to interpret tagging

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20230221/d54371ec/attachment.htm>