sent from a phone
> On 29 Nov 2022, at 00:52, Minh Nguyen wrote:
>
> Even if it weren't for iD's long-gone preset, I don't think an ostensibly
> global tag should be defined based on the narrow provisions of a specific
> country's laws.
I don’t think this is about a specific country, altho
Vào lúc 15:18 2022-11-28, Martin Koppenhoefer đã viết:
crossing:markings is just about this, road markings, and while
crossing_ref=zebra wasn’t documented for a long time, people that added it
around here told me it was about the presence of road markings as well.
Crossing=zebra is about a zeb
sent from a phone
> On 28 Nov 2022, at 23:53, Minh Nguyen wrote:
>
> If we keep crossing=zebra around based on the argument [1] that it takes
> fewer keystrokes or clicks than adding crossing_ref=zebra or
> crossing:markings=zebra without using a preset, then this undermines the
> arguments
Vào lúc 04:55 2022-11-28, Martin Koppenhoefer đã viết:
Just because there is a now a way to map crossing markings separate from
other properties, does not imply all the tagging we have is not needed
any more, rather I would see "crossing:markings" as implicit, for
example on a "crossing=zebra".
Am Mo., 28. Nov. 2022 um 13:13 Uhr schrieb riiga :
> With the approval of the crossing:markings=* proposal there is now a
> satisfactory way of tagging whether a crossing is marked or not
> regardless of the crossing being uncontrolled or having traffic signals.
> For signals, there is crossing:si
Hello!
With the approval of the crossing:markings=* proposal there is now a
satisfactory way of tagging whether a crossing is marked or not
regardless of the crossing being uncontrolled or having traffic signals.
For signals, there is crossing:signals=* which fulfills the same role
but has no