Reading on the issue: https://github.com/gravitystorm/openstreetmap-carto/issues/180 It appears the biggest reason it's not rendered is about styling (whether people want to see that much detail). The fact that it isn't approved is not as important (lots of OSM features never went through the process) However reading there and on the forum, there seems to at least be fair consusus that area:highway=* is for linear features and area=yes is for omnidirectional features.

Note that linear ways with an outline in addition should be area:highway=footway (or whatever kind of way), while pedestrian areas with omnidirectional movement is highway=footway + area=yes. (OSM carto doesn't render the former) The difference is outlined here: osm.wiki/Key:area:highway

Unfortunately Chicago's lakefront parks have lots of these mistaggings ("tagging for the renderer"), and can also break routing at times (for example pedestrians will be routed down this cycleway: osm.org/way/1124504884)

Which classification standards are these? A least on the draft for the Illinois standards it says that certain primary roads may be primary: osm.wiki/Illinois/Highway_Classification

I don't believe Historic US-66 really belongs in ref=*, nor should it really be considered for highway classification, given that is is primarily a tourist route.

Hi, I don't believe that this section of Oakton avenue / capitol drive is actual part of WI 190

Hi Hoffmand002,

Are you certain these ramps exist? The Upon my last visit to the area there where no signs of construction for such overpasses and tunnels (and the geometry does not seem quite right...)

Also for future changesets it can be helpful to shortly describe your changes (this way a person reviewing them can know what to look for)

Thanks!

Note that in general, in the US, Trunk is about network connectiveness, so Trunk "spurs" should generally be avoided: osm.wiki/United_States/2021_Highway_Classification_Guidance

Yeah I'd say you can simply remove them from the ref=*.

Jetzt habe ich oneway von diesem Stückchen entfernt. Ich bin aber noch nicht sicher, ob das tatsächlich erlaubt ist oder als (sehr kurzes) Geisterradeln zählt :)

What do you mean it would change the object type to bollard?

If you know the dates it's open, you can add it as a conditional restriction (For example bicycle:conditional=permissive @ (Nov 1 - Mar 1))

fee=yes ist jetzt entfernt. Und ja, das heißt Parkscheibe (dieses Taggingschema habe ich hier: osm.wiki/Street_parking#Time_limits gefunden.

LG,
Alex

Fixed, thanks for pointing that out

Hi, for for buildings should only be used for the name (and not descriptions) Instead of name="Office Building" you can change the building type to building=office (as I did for you in this case). Happy Mapping and feel free to reach out if you have any questions!

Hi! I don't believe this section of road actually forbids non-motor traffic. Access restrictions only concern legal restrictions: the high speed limit, multiple lanes and lack of a sidewalk already indicate it is probably hostile to peds or bikes.

Ah, I see where the issue was, there were already two Chequamegon-Nicolet National Forests with the same boundaries, and I removed the landuse=forest from the second one (as not the entire forest is landuse=forest) and didn't notice this was already duplicated. Anyway, it appears this has now been sorted out.

What routing engines have an issue with it? At least the default ones here just ignore it (osm.org/directions?engine=graphhopper_bicycle&route=42.94178%2C-88.00443%3B42.94405%2C-87.99441#map=17/42.94281/-87.99957) Anyway, given the legal ambiguity, this makes sense to leave unset.

Hi PixelDubs,

highway=* tags should be on the individual ways, not on the route relation.

Happy mapping,
Alex

Hi!

Could you tell me the purpace of the nodes with the tag done=yes? (for example osm.org/node/10262869354)

Thanks!

Heh, it appear that this was added by mistake to the from the neighborhood map at UWM (it doesn't appear in the map index). Funnily enough, this is an interesting example of the places where OSM data is used: https://www.niche.com/places-to-live/n/zoo-milwaukee-wi/ (I wonder what "young professionals" are living in the zoo...