Hello,
thank you for your considerations. I was aware of the time issue and did an additional call for comments a few weeks ago on the forum to solve that. Seems like I forgot to do one on the mailing list as well, what is an oversight indeed. The forum didn't really bring any new input so I went into voting.
As I don't propose an automated edit I see no issue using the appropriate types of zebra:*. The areas that use various types of zebra markings are usually the ones that tagged crossings without zebra markings as crossing=zebra as well, so you need to review them all anyway.
Crossing:markings=yes is indeed mentioned as a replacement option in the proposal but I would prefer reviewing the crossings. Maybe I can add a warning about other zebra types post voting.
Regards,
Bauer33333
Am 10.05.25, 08:33 schrieb Marc_marc via Tagging <tagging@openstreetmap.org>:
Hello,
Le 09.05.25 à 23:02, bauer33333--- via Tagging a écrit :
> Voting has started for "Deprecate crossing=zebra in favor of
> crossing:markings".
> https://wiki.openstreetmap.org/wiki/Proposal:Deprecate_crossing%3Dzebra_in_favor_of_crossing:markings
> As there have been significant changes to the proposal since the start
> of the RFC I encourage you to read it again before voting.
Thanks for the time you spend on it.
But with an RFC that is more than a year old, it would no doubt have
been interesting to launch a call for comments before the vote for last
year's absentees.
As far as I'm concerned, while I'm very much in favour of deprecate
crossing=zebra, for which I'd already found traces of proposed
deprecations almost a decade ago, the proposal for change it into
crossing:marking=zebra is unfortunately wrong (as was pointed out in
vain when this key was proposed) because crossing:marking=zebra means
that there is only one series of markingss, information which is not
present in crossing=zebra (it could be zebra:double, zebra:paired,,
zebra:bicolour, zebra:rainbow)
To solve this, the meaning of crossing:marking=zebra would have had to
be one or more mandes and a new value crossing:marking=zebra:single
would have had to be created for the current meaning.
But as you can't change the definition of a key used, that's it.
It would be a good idea that a suggested
fix is set to crossing:marking=yes or the different
crossing:markings=zebra* values if we check them one after the other.
and ideally suspend the vote, reissue the call for comments for this
change and vote on the proposal so as not to validate a proposal because
an error has been detected
Regards,
Marc
_______________________________________________
Tagging mailing list
Tagging@openstreetmap.org
https://lists.openstreetmap.org/listinfo/tagging
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
