Or at least variable, calculating for the distribution regionally in each low-zoom tile. So the symbology will still be non-universal.

I talked about the perception of frequency below osm.wiki/Talk:Key:interval#Rendering 15min may be frequent in the (even urban) West, but only so-so in Asia and elsewhere. For worldwide, needs to be a dynamic vector overlay to adjust for the relative headways in view.

Would agree it should use pipeline= similar to =surge_tank if it’s a pipe. But the public sewer mains itself is a culvert; and usually in partially filled open-channel flow (with free surface), not fully filled pipe flow. pipeline= means equipment on a pipe, not that the feature is a pipe.

Should consult the community, and check how routers order the rules.

Typo there. Yes, https://wiki.openstreetmap.org/wiki/Tag:hov:conditional=designated @ (05:00-10:00) could be more reliable. I forgot to consider this. Still, it doesn’t show the default of HOV being allowed during its usage nicely. In other cases where it applies the majority of time, https://wiki.openstreetmap.org/wiki/Tag:hov=designated will be used as the default. So for better understanding,

• =no @ (Mo-Fr 10:00-05:00) may be overridden Need to check routers to confirm.

JOSM parallel tool is fast. What’s slow may be including them in the https://wiki.openstreetmap.org/wiki/Tag:route=road , and any https://wiki.openstreetmap.org/wiki/Tag:route=bus affected?

1. opening_hours= is usually not considered on roads. This may be a case where https://wiki.openstreetmap.org/wiki/Tag:highway:conditional=motorway @ (Mo-Fr 05:00-10:00) is correct, as the separate roadway doesn’t exist outside those times. Unfortunately, you still need https://wiki.openstreetmap.org/wiki/Tag:highway=motorway for compatibility. Furthermore, due to how overriding works, you need to specific https://wiki.openstreetmap.org/wiki/Tag:*:conditional=no @ (Mo-Fr 05:00-10:00) for each mode, as https://wiki.openstreetmap.org/wiki/Tag:access:conditional=no @ (Mo-Fr 05:00-10:00) or https://wiki.openstreetmap.org/wiki/Tag:motor_vehicle:conditional=no @ (Mo-Fr 05:00-10:00) will be overrideen by https://wiki.openstreetmap.org/wiki/Tag:hov=designated etc. So it’s still not as simple as you think, and there’s advantage in 2 except for suffixing *:backward:*= .
2. https://wiki.openstreetmap.org/wiki/Tag:hov:minimum:conditional=2 @ (Mo-Fr 05:00-10:00) is not required. https://wiki.openstreetmap.org/wiki/Tag:hov:minimum=2 @ (Mo-Fr 05:00-10:00) is always true.

You can use osm.wiki/OSM_Smart_Menu#More_examples_for_advanced_method_using_custom_code

Showcasing them requires more than the layers currently shown. You need overlays, buttons, and detection. Clickable shapes for per-building view, since level= currently shown for all buildings may not match. Essentially changed entirely.

Both “OpenStreetMap doesn’t yet have support for such multi-levelled maps” and “ Most of this world underground isn’t yet seen in OpenStreetMap.” are not entirely true. There is already Indoor= and OpenLevelUp, alongside JOSM’s built-in level= filtering. The question is where do you draw the line between tunnel= / https://wiki.openstreetmap.org/wiki/Tag:man_made=tunnel and indoor= / building=, as well as how to model the levels. The use of https://wiki.openstreetmap.org/wiki/Tag:building=train_station + https://wiki.openstreetmap.org/wiki/Tag:location=ground + building:levels:underground= for underground rail stations in general has been discussed before. Kamppi already has the basics added around node/1378007259#map=19/60.16902/24.93236 with tunnel=. Rendering of https://wiki.openstreetmap.org/wiki/Tag:highway=pedestrian + https://wiki.openstreetmap.org/wiki/Tag:area=yes above everything else has been discussed in Carto for tunnel= https://github.com/gravitystorm/openstreetmap-carto/issues/529 and building= https://github.com/gravitystorm/openstreetmap-carto/issues/688 with https://github.com/gravitystorm/openstreetmap-carto/pull/3872 closed.

You scared me there. Thought it’s spam before looking at the user name!

crossing:light= and light_source= are good stuff. There’s luminous= to show a feature itself is emitting light, unlike the 3rd-person lit=.

More of a they don’t know where their maps are from case. Applications have a part in informing credits to ask for attribution.

Is it simple enough you can make a bookmarklet ver?

You should specify “Chinese (traditional)” is localized for PRC to clarify it is based on Simplified (assuming from the flag). On top of “ some terms is not the same” for Taiwan Mandarin, Cantonese (viz Hong Kong, which is yet different in Macau and Guangdong) uses an entirely different language as well. @Supaplex There is a “Chinese (TW)” now.

You have not discussed https://wiki.openstreetmap.org/wiki/Tag:amenity=training + training=. Expanding https://wiki.openstreetmap.org/wiki/Tag:amenity=school isn’t a good idea, which might be why all the https://wiki.openstreetmap.org/wiki/Key:amenity_school appeared in the first place.

I’m not sure any driving course would be considered post-secondary. Despite the many meanings of “college”, a bachelor offering institution is likely a =university.

ISCED has Fields, aside from Programme (and Attainment). Furthermore, The reason why “Programme” is suggested over “Level” is exactly because additional categories such as “Professional Bachelor” isn’t a “Level”. Only “Bachelor equivalent” is a level. There is also issue with mixing different categories.

If a rural route crosses the municipality border slightly, tagging it as =intercity looks misleading as a true city–city route. As seen in your example 1 and 2, this leads to a mix of them; and semi-colon multi-value is something to be wary of.

Something like designation= on roads for the official classification of routes would be nice, to directly tag https://wiki.openstreetmap.org/wiki/Tag:*=城市公交 etc. For networks, there is a network:area= in the wild to bridge https://wiki.openstreetmap.org/wiki/Key:networkcn for non-motorized modes, hierarchical eg =JP:national for roads, and branding eg https://wiki.openstreetmap.org/wiki/Tag:network=JR for transit.

For a tentative local-only solution, suffixing *:CN-SH= is possible.

There was already osm.wiki/Proposed_features/Differentiation_for_routes_of_public_transport (most of it needs to be improved); and service=*#Train_Routes or passenger=* for railways.

Route is route. Network is network. Slightly mismatching to put them together. Using network:route:*= (not to mention the pitfalls of *:type=) makes me think the network is within a city or intercity, rather than only a route. =city, =urban, and =town are unclear. A general problem with the =suburban terminology is it is unclear whether the route is radial city–suburb, or circumferential or local within the suburbs only. (or even cross-city suburb–city–suburb)

Thanks for your effort. Sorry I didn’t get any reply in email for my report, so I ended up nagging you.