You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A local user whom I know is quite affine to click iD-editor validator suggestions without much looking at what the problem is recently "upgraded" dozens of bus_stops and crossings:
Everywhere there is a "marked" crossing, there now also is "crossing:markings=yes" specified. I did ask. They told me, this is not wrong, as it makes it even more clear, that there are markings there.
I read the documentation - https://wiki.openstreetmap.org/wiki/DE:Key:crossing:markings - there it says: yes means unknown type of markings - so yes is wrong, the type of markings might be unknown to the validator - but it can be seen on the aerial without much trouble.
Please reconsider: Any bot can make such edits. iD should use the human work-force more constructively. Mapper time may be free, but it can be used to perform actual improvements to the data instead of being wasted.
Screenshot(s) or anything else?
No response
Which deployed environments do you see the issue in?
No response
What version numbers does this issue effect?
2.30.2
Which browsers are you seeing this problem on?
No response
The text was updated successfully, but these errors were encountered:
URL
No response
How to reproduce the issue?
A local user whom I know is quite affine to click iD-editor validator suggestions without much looking at what the problem is recently "upgraded" dozens of bus_stops and crossings:
Everywhere there is a "marked" crossing, there now also is "crossing:markings=yes" specified. I did ask. They told me, this is not wrong, as it makes it even more clear, that there are markings there.
I read the documentation - https://wiki.openstreetmap.org/wiki/DE:Key:crossing:markings - there it says: yes means unknown type of markings - so yes is wrong, the type of markings might be unknown to the validator - but it can be seen on the aerial without much trouble.
Please reconsider: Any bot can make such edits. iD should use the human work-force more constructively. Mapper time may be free, but it can be used to perform actual improvements to the data instead of being wasted.
Screenshot(s) or anything else?
No response
Which deployed environments do you see the issue in?
No response
What version numbers does this issue effect?
2.30.2
Which browsers are you seeing this problem on?
No response
The text was updated successfully, but these errors were encountered: