-
Notifications
You must be signed in to change notification settings - Fork 819
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
Stop rendering highway=road? #4905
Comments
We have rendered Not rendering it any more would nudge mappers to guess a different road class (see last point above) - which would be counterproductive. Rendering it like Generally speaking i think we should more widely render tagging well established to be specifically used for indicating missing relevant information as such. We are also inconsistent in that regard - see #4906. |
Good point that Dropping priority would be an easy fix. Thee are some other weirdnesses in the priority table that could be addressed at the same time, e.g. why link roads appear well down the table, when I would assume that, say |
No, the z_order is not a significance rating, it defines the drawing order. That links are drawn below all other connecting road types is a fundamental aspect of the way we depict roads. Motorway links do not exclusively connect to trunk roads for example, primary, secondary and tertiary are just as common - like here: https://www.openstreetmap.org/#map=16/48.2482/12.0424 motorway_link to unclassified is more rare but perfectly valid in principle. If |
Thanks for explaining! |
Closing this as declined for the removal of |
Expected behavior
highway=road
is agreed to be poor tagging, at best a "fixme" for a better road type classification. Given that OSM Carto is generally conservative about rendering, it is odd thathighway=road
is both rendered and given a distinctive render.Screenshots with links illustrating the problem
(https://www.openstreetmap.org/#map=17/54.83907/-2.25666)
Note bad join, caused by
highway=road
(grey fill) having same priority as highways with white fill:Usage peaked over 400k in 2012, and has been continually dropping since to just over 50k currently:
(https://taghistory.raifer.tech/#***/highway/road)
Presumably being gradually squeezed out by validators (JOSM at least warns about
highway=road
).Options:
Stop rendering. Provides direct feedback that feature is not "map ready". Simplifies lengthy road code, and frees up some "colour space".
Rendering as unclassified would have most of these advantages, but runs counter to providing mapper feedback.
Just fixing the fill problem by lowering the priority of
highway=road
would be easy, but require a database reload.Option 1 seems the best.
The text was updated successfully, but these errors were encountered: