<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Lionel,<br>
</p>
<div class="moz-cite-prefix">On 17/01/20 10:52, Lionel Giard wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CA+D7pWxh8sYwPjkWYFq-FwB5wHo3m1rbOWjY8JA0Up8F+xO-9A@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>
<div>Alesandro,</div>
<div><br>
</div>
<div>The thing is that disabled=designated is an access (so
regulated by law), and would depend because each country's
law vary (not every country enforce restriction for disabled
parking or other type of vehicle...). Thus, it may be wrong
to tag an access when it doesn't exist.</div>
</div>
</div>
</blockquote>
<p>If the parking_space with specific symbology is regulated by law
and only accessible by disabled persons (like in Italy), I think
the tag disabled=designated express exactly that, and should be
used.</p>
<p>If a parking space is not limited to disabled persons, what is
the purpose to add a capacity:disabled=1? Maybe I'm missing your
point... Could you please share and example where a parking space
should have a capacity:disabled=1 but is not access-regulated?</p>
<p>Ale<br>
</p>
<blockquote type="cite"
cite="mid:CA+D7pWxh8sYwPjkWYFq-FwB5wHo3m1rbOWjY8JA0Up8F+xO-9A@mail.gmail.com">
<div dir="ltr">
<div>
<div>While a tag that's only an attribute describing what type
of parking exist, is unambiguous. It may be parking_space=*
or access:*=* , both are "good" for that as they are
unambiguous in their meaning. The only advantage of the
second is that it is already used for amenity=parking and
seems coherent to use for the parking_space in my opinion
(even if it is only 1 place). The wiki page already mention
all the different type because there are many other than
disabled (like parent, women, electric charging,...) : <a
href="https://wiki.openstreetmap.org/wiki/Key:capacity"
moz-do-not-send="true">https://wiki.openstreetmap.org/wiki/Key:capacity</a></div>
</div>
<div><br>
</div>
marc,
<div><br>
</div>
<div>The capacity:*=* tag should not be used alone (as described
for any parking), it is an addition to the capacity=* tag. For
example, a place marked as "capacity=1" and
"capacity:disabled=1" means that the 1 capacity is disabled. A
better example is for an amenity=parking, you have a parking
with "capacity=12" and "capacity:disabled=3" it means 3 of the
12 parking space are disabled. </div>
<div>Theoretically, all parking_space should be capacity=1 (and
if necessary capacity:*=*) but the advantage (as mentioned
above) is that it would use the same tagging than for
amenity=parking. Thus we wouldn't use two different scheme for
the same thing. </div>
<div><br>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">Le ven. 17 janv. 2020 à 09:52,
PanierAvide <<a href="mailto:panieravide@riseup.net"
moz-do-not-send="true">panieravide@riseup.net</a>> a
écrit :<br>
</div>
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div>
<p>Hello Lionel,</p>
<p>I totally agree with that, I never understood this
special treatment of amenity=parking_space, and so I'm
using capacity:*=* with that. My use case is for disabled
people parking spaces : just look for capacity:disabled=*
and you're good to go, whatever it is a parking or
parking_space.</p>
<p>Best regards,<br>
</p>
<pre cols="72">Adrien P.</pre>
<div>Le 17/01/2020 à 09:36, Lionel Giard a écrit :<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hello everyone,
<div><br>
</div>
<div>I saw that on the parking_space wiki page it says
that we shouldn't use capacity:*=* on parking_space,
and instead use the access tag. But why is this the
case? It seems logical to use capacity:disabled=* on a
parking_space for disabled people or
capacity:charging=* on a parking_space for electric
vehicles that are charging. And there is not always
legal access linked to these "special" parking spaces
(e.g. I don't think there are many places regulating
parking on parents' parking spaces in the law). <br>
</div>
<div>It seems strange to forbid this, while promoting
the tagging of "capacity=*". ^_^</div>
<div><br>
</div>
<div>I therefore propose to change this description to
favour this tagging (when useful) instead of
prohibiting it. What do you think about this?<br>
</div>
<div><br>
</div>
<div>Kind Regards,</div>
<div>Lionel</div>
</div>
<br>
<fieldset></fieldset>
<pre>_______________________________________________
Tagging mailing list
<a href="mailto:Tagging@openstreetmap.org" target="_blank" moz-do-not-send="true">Tagging@openstreetmap.org</a>
<a href="https://lists.openstreetmap.org/listinfo/tagging" target="_blank" moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/tagging</a>
</pre>
</blockquote>
</div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank"
moz-do-not-send="true">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging"
rel="noreferrer" target="_blank" moz-do-not-send="true">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
Tagging mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Tagging@openstreetmap.org">Tagging@openstreetmap.org</a>
<a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/listinfo/tagging">https://lists.openstreetmap.org/listinfo/tagging</a>
</pre>
</blockquote>
</body>
</html>