-
Notifications
You must be signed in to change notification settings - Fork 807
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Render highway=proposed again #4434
Comments
What about some people mapping really vague ideas? From a data purist point of view, it can seem good not to render proposed highways - but from "selling OSM" point of view, we're losing. |
It seems nothing of substance has changed since #1654/#1663 and i don't see any new arguments on the matter either. It is clearly consensus among mappers that proposed roads - for any meaning of proposed - typically are not verifiable. Looking at the data supports this. |
Not rendering
No idea why it would be considered as worth emulating, showing nonexisting way as existing does not seem to be a good idea. Likely Google has simply wrong data in your area (in my region it occasionally even routes along nonexisting roads). |
Expected behavior
highway=proposed is rendered (in some shaded, lighter colour or such).
Actual behavior
It's not rendered anymore.
Links and screenshots illustrating the problem
#1654 removed highway=proposed rendering, mentioning the concerns that all kinds of not-really-feasible "proposals" were being mapped.
In most cases, though, those proposed highways would be very useful to render, as they are coming from official planning documents.
Additionally, not rendering them increases data rot, where there's little motivation to clean up proposals in map data.
This is also something other map providers do, and users do like that - for example: https://twitter.com/kasparsskincs/status/1410953346693935104 .
Mappers would benefit, as they could map streets as proposed, allowing easier transitioning to construction, then to the final tagging.
Other provider review:
The text was updated successfully, but these errors were encountered: