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

2023-02-22 Thread Andrew Harvey
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

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

2023-02-22 Thread Andrew Harvey
> > >1. As far as non-emergency routing, the "locked" tag should be ignored. > > As Andy points out you may have legal access but the gate is still locked preventing physical access. Therefore routers shouldn't just ignore the fact that the gate is locked, they should either avoid the route or

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

2023-02-22 Thread Zeev Stadler
Here is my summary of the discussion so far: This tagging combination example was shown by several people to be appropriate for the "state on the ground" of certain barrier structures. Therefore the question of the appropriate interpretation is a valid question. My interpretation was generally

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

2023-02-22 Thread Peter Neale via Tagging
Hi @Mateusz, Thank you for clarifying the meaning of "=permit".  I will have to think again how to tag these ways.  If I have used Taginfo correctly there are "only" 1503 ways with "description=redway", which I might have tagged like this!  Regards,Peter(PeterPan99) On Wednesday, 22 February

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

2023-02-22 Thread Mateusz Konieczny via Tagging
Feb 21, 2023, 22:05 by tagging@openstreetmap.org: > They can also be removed by maintenance workers operating with permission > from the local Council  (I have tagged the access rights of the ways with > "motor_vehicle=permit" > =permit is for cases where permit is routinely granted to all