<div dir="auto"><div>If it is used in Italy to describe pavement markings (and only the pavement markings) then I see no reason that these should not be retagged to crossing:markings=zebra over time.</div><div dir="auto"><br></div><div dir="auto">On the other hand, if Italy has a standardized "zebra crossing" (similar to how I described for the UK) then whatever this means in Italy should be documented on the wiki (signage, priority, etc.).</div><div dir="auto"><br></div><div dir="auto">Alex<br><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">Volker Schmidt <<a href="mailto:voschix@gmail.com">voschix@gmail.com</a>> schrieb am So., 24. Juli 2022, 00:20:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div dir="ltr"><br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sat, 23 Jul 2022 at 12:50, Alexander Kane <<a href="mailto:1998alexkane@gmail.com" target="_blank" rel="noreferrer">1998alexkane@gmail.com</a>> wrote:<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 dir="ltr"><div>I updated the proposal saying that using crossing_ref to describe pavement markings should be depricated. </div></div></blockquote><div><br></div><div>Please do not do that. This tag is used in that sense, in Italy alone, 32k times. <br></div><div><br></div><div>Volker<br></div><div><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 dir="ltr"><div>The biggest effect of this is that crossing_ref=zebra should be reverted to its original definition. Currently, the page for crossing_ref=zebra mentions only the road markings, while the key page for crossing_ref=* states that it is the local name for the crossing type, and that (in the UK) crossing_ref=zebra implies more than just zebra markings, but also Belisha beacons, zig-zag markings, and pedestrian priority.</div><div><br></div><div>Crossing_ref certainly needs an overhaul imo (maybe something like crossing:designation=GB:zebra or the like) but this would probably be best as a separate proposal. In any case, removing info only about the road markings will help make crossing_ref more useful.</div><div><br></div><div>Alex<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Mateusz Konieczny via Tagging <<a href="mailto:tagging@openstreetmap.org" target="_blank" rel="noreferrer">tagging@openstreetmap.org</a>> schrieb am Mo., 11. Juli 2022, 10:56:<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>
<div><br></div><div><br></div><div><br></div><div>11 lip 2022, 10:07 od <a href="mailto:minh@nguyen.cincinnati.oh.us" rel="noreferrer noreferrer" target="_blank">minh@nguyen.cincinnati.oh.us</a>:<br></div><blockquote style="border-left:1px solid rgb(147,163,184);padding-left:10px;margin-left:5px"><div>Somehow railroad crossings managed to escape the trap of shortsighted classification tagging. The rail regulators in my region classify level crossings on a linear scale. For example, the presence of flashing lights **of course** implies a bell, a saltire, and the requirement for the train to blow its horn. [5] But I see no problem in filling out a detailed form about crossing:saltire, crossing:bell, crossing:light, and crossing:horn. The extra checkboxes benefit regions where these fundamental laws of the universe do not hold. There can always be a preset for each common combination for mappers' convenience.<br></div></blockquote><div dir="auto"><br></div><div dir="auto">Yes, and crossing tagging should be decoupled into such separate tags.<br></div><div dir="auto"><br></div><div dir="auto">Otherwise it will never solve of problems that in different regions different<br></div><div dir="auto">things come in a different sets (zebra markings / traffic lights etc)<br></div><div dir="auto"><br></div> </div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" rel="noreferrer noreferrer" target="_blank">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank" rel="noreferrer">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div></div>
_______________________________________________<br>
Tagging mailing list<br>
<a href="mailto:Tagging@openstreetmap.org" target="_blank" rel="noreferrer">Tagging@openstreetmap.org</a><br>
<a href="https://lists.openstreetmap.org/listinfo/tagging" rel="noreferrer noreferrer" target="_blank">https://lists.openstreetmap.org/listinfo/tagging</a><br>
</blockquote></div></div></div>