STANDARD Layer in OSM not showing UNPAVED Linetypes anymore

Awhile ago, UNSURFACED roads had a DASHED Linetype, but currently they look like SURFACED roads. Can you change it back to DASHED LINES, so us mappers can see ERRORS quickly whitout having to start ID editor.

Example

https://www.openstreetmap.org/way/8762936

They are still dashed, if they taged with highway=track. If they taged with other highway, they will look like that highway tag.
And it isn’t always an error: for example, this is how one highway=trunk used to look back in mid 00s, before reconstruction :smiley:

Why can’t HIGHWAY=RESIDENTIAL, SURFACE=UNPAVED show as a DASHED LINETYPE?

It is STILL DIRT and should be indicated as such.

I do not want to start changing all the dirt roads around my area to TRACK just to see DASHED LINES on the OSM STANDARD MAP.

That sounds like a rendering problem and from everything I have read you shouldn’t tag for the renderer. If you change it to track it could affect routeing. The Wiki lists track as “Roads for agricultural or forestry uses etc, often rough with unpaved/unsealed surfaces, that can be used only by off-road vehicles (4WD, tractors, ATVs , …) .” I use Openfieltsmap Lite and OSM generic routable new and they both show unpaved roads.

The correct question is “Why can’t HIGHWAY=RESIDENTIAL, SURFACE=UNPAVED show as a DASHED LINETYPE in Mapnik render?” Because there some renders that do show unpaved surfaces upon residential, unclassified and etc. roads, like UniRS render for OsmAnd Android app:

(Compare to mapnik version)

The last time I checked, mapnik authors stated, that there is no way in current version to effectively draw lines that depends on many tags instead of one… So implementing acess=* on higways=* was already some kind of high-level magic. There also promises that those pats of codes will be rewritten eventually, so mapnik will be able to render any number of tags in one line, and everyone will be happy forever after.

Yes, that would be a stupid thing to do, 'cause “Don’t tag for the renderer”

I am using Openstreetmap.org and using STANDARD LAYER and UNSURFACED roads are suppose to be DASHED LINES (according to the MAP KEY), but they are being drawn SOLID and look like PAVED roads.

How do I get UNSURFACED roads to look like DASHED lines, like the MAP KEY defines.

Greg

Oddly, it appears that the map key for the “standard” layer (which I think is https://github.com/openstreetmap/openstreetmap-website/blob/068471fc0e797428c48b8917d62fe7db0331cc65/config/key.yml is incorrect). That contains entries for both “unsurfaced” (which I’ve not encountered before) and “byway” (which definitely isn’t rendered).

I’ve created an issue at the website: https://github.com/openstreetmap/openstreetmap-website/issues/882 - keep an eye on that to see progress (arguably the “bug” is that the process of updating the openstreetmap-carto style doesn’t include a step to update the map key - so that bug may get closed and linked to one in a different repository).

Note that there is already an issue in the openstreetmap-carto repository that says “we ought to render unpaved roads differently somehow”:

https://github.com/gravitystorm/openstreetmap-carto/issues/110

Just repeating that statement won’t make it happen because pretty much everyone agrees that in principle it’s a good idea - the problem is how to do it in a way that doesn’t confuse someone reading the map. A number of the suggestions (such as dotted casing) clash with existing map features.

There may, of course, already be map renderings that render non-paved roads.

SERVICE ROADS that are UNPAVED show up as DASHED LINE using STANDARD LAYER in OSM.

But HIGHWAY=RESIDENTIAL, SURFACE=UNPAVED still have solid linetypes. Why do Service Roads look ‘correct’ (dashed lines), but Residential Roads are still ‘incorrect’ (solid lines)?