• =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 route=road , and any route=bus affected?

1. opening_hours= is usually not considered on roads. This may be a case where 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 highway=motorway for compatibility. Furthermore, due to how overriding works, you need to specific *:conditional=no @ (Mo-Fr 05:00-10:00) for each mode, as access:conditional=no @ (Mo-Fr 05:00-10:00) or motor_vehicle:conditional=no @ (Mo-Fr 05:00-10:00) will be overrideen by hov=designated etc. So it’s still not as simple as you think, and there’s advantage in 2 except for suffixing *:backward:*= .
2. hov:minimum:conditional=2 @ (Mo-Fr 05:00-10:00) is not required. 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= / man_made=tunnel and indoor= / building=, as well as how to model the levels. The use of building=train_station + location=ground + building:levels:underground= for underground rail stations in general has been discussed before. Kamppi already has the basics added around osm.org/node/1378007259#map=19/60.16902/24.93236 with tunnel=. Rendering of highway=pedestrian + 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 amenity=training + training=. Expanding amenity=school isn’t a good idea, which might be why all the 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 *=城市公交 etc. For networks, there is a network:area= in the wild to bridge network=*cn for non-motorized modes, hierarchical eg =JP:national for roads, and branding eg 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 osm.wiki/Key:service#Train_Routes or osm.wiki/Key: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.

1. osm.wiki/JA:Key:building:levels You can use building:levels= to count the number of floors, without adding building:height= directly. Both are used in 3D renders, eg https://osmbuildings.org/ and https://demo.f4map.com/ (and other applications).
2. osm.wiki/JA:Key:lanes More convenient to add lanes= at first, but measuring width= on GSI map is also easy (especially for lane_markings=no).

You can ask questions on OSM Help.

website= would link a general page/tab in a website, perhaps showing basic info and route. To explicitly to link some particular info (especially on different sub-page / tabs), better use *:url=. There’s already opening_hours:url=, and it’s not a different website. Eg interval:url= if needed.

departures_board=delay actually means the headway/interval to show service frequency, not disruption delays. Mistranslation in the original.

@H@mlet
On the other hand, I don’t want to disable too many roads during daytime. I do use the “most of the time” criteria with deciding motor_vehicle= default =yes or =no. In this case, it’s nighttime and on weekends.

@xyzl It’s not Tagging For Router if it is correct data. (Moreover many renderers only considers access=)

For visibility, ask questions on OSM Help. Diary is more for showing your thoughts or solution. Not as many read this I assume.

You need to know comma and semi-colon have different meanings. Simplified explanation: , is for additional rules; ; for overriding rules.

The correct tag could be motor_vehicle:conditional=no @ (Fr,Sa, PH -1 day 20:00-24:00, Sa,Su 00:00-05:30; PH 00:00-05:30). The critical difference is =*, PH -1 day 20:00-24:00*. Verify https://openingh.openstreetmap.de/evaluation_tool/?EXP=Fr,Sa, PH -1 day 20:00-24:00, Sa,Su 00:00-05:30; PH 00:00-05:30&lat=51&lon=0&mode=0&DATE=1650020460000 (set to England on Good Friday) by playing around with the date and syntax.

That’s a long discussion for a diary. I will simply mention one of my recent observations on angled intersection geometry: Make a right-angle by considering a perpendicular line normal to the give-way / stop / signal line (as a tangent).