Proposal talk:Deprecate maxspeed:seasonal:winter
Jump to navigation
Jump to search
Response to: Deprecate maxspeed:seasonal:winter only is nonsense
from https://lists.openstreetmap.org/pipermail/tagging/2023-June/067359.html
I agree that deprecating all of maxspeed:<actually covered by conditional syntax>:* would be better. Probably the proposal author only considered maxspeed:seasonal:winter because other combinations do not have any significant usage. As it appears that it has to go back into the RfC phase to be "correct", I'd suggest to amend the proposal in this way. --Westnordost (talk) 11:55, 8 June 2023 (UTC)
- I felt that the other conditional type keys had sufficiently low usage (and I can't find any projects using them) that they could be changed by mass edit. I am going to propose that after this vote, either including or excluding this key depending on the outcome. I asked on the forum if such keys should be discouraged and no-one seemed to want to stick with them.
- There is at least maxspeed:winter, maxspeed:summer, maxspeed:seasonal:winter, maxspeed:seasonal:summer, seasonal:winter:maxspeed, maxspeed:wet, maxspeed:children_present, maxspeed:flashing, maxspeed:night, maxspeed:snow, maxspeed:school_days (unclear what that should change to though, is it all day on school days?), and some of these also with :forward or :backward. All of these other than maxspeed:seasonal:winter have fewer than 1000 uses worldwide, and other than the last one there are obvious conditional values they can be changed to. --Arrival-spring
Pages affected
"Features/Pages affected" should include Conditional restrictions. At the moment, seasons such as "winter" are not among the documented conditions. --Tordanik 09:23, 9 June 2023 (UTC)
- Thank you, and seeing as "winter" is already in use as a condition I have added it to that page. --Arrival-spring (talk) 12:31, 9 June 2023 (UTC)