<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>I am not sure if we understand each other correctly :)<br>
</p>
<p>Variant 1 is for area features. Translating this variant to
parking:lanes (line features) is equivalent to variant 3,
described in column 2. This would mean a fundamental change in the
parking:lane scheme to harmonise it with common access tagging. In
this case, we could use common access tagging on both:
area/polygon parking features (amenity=parking + access) and
linear parking features (parking:lane:* + parking:lane:*:access).</p>
<p>Why should "use the established tags for parking lots also on
street-side parking areas" be impossible? I demonstrated that in
variant 1 (column 4) and have been using this variant for months
without encountering any problems so far (also for complex parking
restrictions).<br>
</p>
<p><br>
</p>
<div class="moz-cite-prefix">Am 03.09.22 um 21:11 schrieb Mateusz
Konieczny via Tagging:<br>
</div>
<blockquote type="cite" cite="mid:NB3krCi--3-2@tutanota.com">
<pre class="moz-quote-pre" wrap="">yes, but how variant 1 would work on parking lanes?
As far as I see
"We use the established tags for parking lots also on street-side parking areas"
is impossible.
Sep 3, 2022, 20:55 by <a class="moz-txt-link-abbreviated" href="mailto:supaplex@riseup.net">supaplex@riseup.net</a>:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">
Variant 1 is the 4th column in the table: > <a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Proposed_features/parking_conditions_on_separately_mapped_parking_areas">https://wiki.openstreetmap.org/wiki/Proposed_features/parking_conditions_on_separately_mapped_parking_areas</a>
Resident only parking sounds like access=permit or better access=private (as these parking lots are not available to the general public) + a tag for the residential parking zone (like parking:residents=<zone>) + an additional tagging to specify different "private" user groups more precisely (like residents, employees). I just posted some "access:private" variants in use for discussion in January, as this is also relevant for regular "surface" parking spaces: > <a class="moz-txt-link-freetext" href="https://lists.openstreetmap.org/pipermail/tagging/2022-January/063825.html">https://lists.openstreetmap.org/pipermail/tagging/2022-January/063825.html</a>
Am 03.09.22 um 18:19 schrieb Mateusz Konieczny via Tagging:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Can you give example how variant 1 works?how would you tag road where anyone can drive and only residents can parkin parking lanes?Sep 3, 2022, 17:12 by >> <a class="moz-txt-link-abbreviated" href="mailto:supaplex@riseup.net">supaplex@riseup.net</a>>> :
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">I think we have a misunderstanding here: There can be no "option 4 - keep things unchanged" because the described problem has simply not been solved or documented yet. Street-side parking areas exist since one and a half years only and the tagging of parking restrictions was not part of the proposal. Therefore, I can't mark any variant that is in use now. As far as I can see, among the few mappers who are engaged in this topic, both variants described for areas are in use. I'm using variant 1 myself. A few days ago I saw a table from another mapper who described variant 2 (via OSM DE Telegram Channel). Variant 3 (complete renewal of the parking lane scheme) would have a very serious impact, especially since StreetComplete released the new parking overlay yesterday (I don't have to tell you that :) PTv2 sends its regards... But to get a documented standard I compared the different options and asking for opinions to follow up on one of the three options. The tagging details can then be discussed there.Am 03.09.22 um 13:42 schrieb Mateusz Konieczny via Tagging:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">Sep 2, 2022, 15:31 by >> >>>> <a class="moz-txt-link-abbreviated" href="mailto:supaplex@riseup.net">supaplex@riseup.net</a>>>>> >> :
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">1. We use the established tags for parking lots also on street-side parking areas (access=*, fee=*, maxstay=*... and their conditional restrictions).
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">impossible, as road access and street-side parking areas may have differentaccess, fee and maxstay statusprefixing would be needed, and at this point this tags are not so establishedanymorein case that I am confused: how in variant 1 you would tag road usable by anyonewith "residents only" parking lane?>> >>>> <a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Proposed_features/parking_conditions_on_separately_mapped_parking_areas">https://wiki.openstreetmap.org/wiki/Proposed_features/parking_conditions_on_separately_mapped_parking_areas</a>>>>> >> seems to not have variant 1 linear examples
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">2. We adopt the parking:condition=*-scheme for street-side parking areas
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">I am not too happy about this, that brings extra complexity where it is notneeded
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">3. We fundamentally resolve this conflict by adopting the common OSM access scheme to the parking:lane/condition scheme.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">I will read it and will comment if I will have anything useful
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">I have illustrated these variants and some of their advantages and disadvantages: > >>> >>>>> <a class="moz-txt-link-freetext" href="https://wiki.openstreetmap.org/wiki/Proposed_features/parking_conditions_on_separately_mapped_parking_areas">https://wiki.openstreetmap.org/wiki/Proposed_features/parking_conditions_on_separately_mapped_parking_areas</a>
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">area features would benefit from marking which variant is used now(second column, right?) and maybe moving it to the first columnhow amenity=parking access=private fee=no would be tagged in a schema 2?
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">...and wonder which variant would have the most support in the community or what you think about it in general. Ideally, we will gain an opinion on which of these variants should be continued/proposed/documented.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">there is also option (4) - keep things unchanged_______________________________________________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>
</blockquote>
<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>
</blockquote>
<pre class="moz-quote-pre" wrap="">
</pre>
<br>
<fieldset class="moz-mime-attachment-header"></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>