Also I usually don’t use thumbs-down. That obviously might be perceived as harsher. https://community.openstreetmap.org/t/proposal-to-add-the-emoji-as-a-reaction/107167/3

Sorry that it comes out like that. At least I tried to explain what it should have. It doesn’t look different from what you received elsewhere. https://www.mail-archive.com/tagging@openstreetmap.org/msg59283.html Making a proposal is usually challenging. But it doesn’t help to add confusion and distractions to the already long debate that surely most don’t read fully. The standard is the same whether you are new or old.

• 94 https://taginfo.openstreetmap.org/tags/cuisine=wine

• 44 https://taginfo.openstreetmap.org/tags/bar=wine_bar (seems redundant, but could emphasize)
• 13 https://taginfo.openstreetmap.org/tags/bar=wine
• Unfortunately https://wiki.openstreetmap.org/wiki/Key:drink:*#Tag_values isn’t usable directly for eg =main or =only now. There are also interface problems with takeaway= and sells:*= for the format. Needs more thinking.

@jimkats That’s irrelevant. The situation is summarized clearly in DWG’s email.

Are you serious? Not a day has passed for your “never”.

Why do you think the discussion “has nothing to do with OSM” when you are discussing it? Accusing others of stalking and “banning” you with “friends” or a cartel is creepy.

It’s part of history. The origin is from drawing streets and roads. Arguably the unique advantage in trails has outgrown the framework and competition later.

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 https://wiki.openstreetmap.org/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, 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, 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 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 https://wiki.openstreetmap.org/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 https://www.openstreetmap.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!