johnw wrote:
>Access=disabled would be good for this situation, but
In this the "disabled" is a group, i.e. a mode of transport as the
wiki page calls them, and should be in the key and not in the value;
otherwise some areas would get access=disabled;seniors;pregnant ,
which is awkward.
Also the
TL;DR:
capacity=* (and access=*) need to better match reality and have more values -
and have existing popular values (including iD presets) documented.
> On Aug 1, 2015, at 7:50 PM, Lauri Kytömaa wrote:
>
> In this the "disabled" is a group, i.e. a mode of transport as the
> wiki page calls
sent from a phone
> Am 01.08.2015 um 14:29 schrieb John Willis :
>
> I want to say that only disabled vehicles can gain access through a barrier
> or use a parking isle.
access=no
disabled=yes
cheers
Martin
___
Tagging mailing list
Tagging@opens
It makes sense to me to go more by physical attributes than the official
primary/secondary/tertiary rating. Among other reasons, medium-term
conditions such as construction projects may mean that the quickest route
from point A to point B involves the use of a lower-rated roadway to bypass
a ch
Sent from my iPhone
> On Aug 2, 2015, at 4:25 AM, Martin Koppenhoefer
> wrote:
>
> access=no
> disabled=yes
___
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
(btw. I don't see any problems with capacity:x=* tags, just the access=* values)
John Willis wrote:
>access=customers
Either access=destination or access=permissive, depending on local
laws an practices. (or motor_vehicle=*)
>access=emergency
rather access=no + emergency=yes
> a legally separate
> On Aug 2, 2015, at 8:49 AM, Lauri Kytömaa wrote:
>
>> access=customers
> Either access=destination or access=permissive, depending on local
> laws an practices. (or motor_vehicle=*)
Access=customers is an established (and documented*) and well used tag (100K
uses), and a preset in iD.
The
