One unofficial app can do this. The list of saved objects will appear when you click the search bar. https://osmapp.org/

To clarify, they would still need to be separated eventually. Eg indoormark:code:navilens=yes + indoormark:qr_code=yes for newer ones with both, and indoor:code:navilens=only for older ones filled with colored dots entirely.

Could be for example indoormark:beacon=qr_code for showing they have that for navigation. It’s unfortunate the meaninglessly suffixed beacon:type= got pass voting, alongside other subpar choices. osm.wiki/Tag:indoormark=beacon

Navilens frames a standard QR code inside their proprietary colored dots now, so =qr_code is still correct. They are advertising it as QR code, made accessible, or enhanced. https://www.navilens.com/accessibleqrcode/

navilens=yes is not ideal for organizing. The necessity for a generic term for these other 2D dot matrix codes should be discussed. For comparison, there are a dozen payment:barcode=yes , and barcode= content.

Alternatively, a simpler method might be qr_code= eg =navigation , as qr_code=yes already exists. Although some are using it to store the content directly. that can be moved to other solutions. As a stopgap to the above issue, it could also be qr_code=navilens / qr_code:navilens=yes if it’s interpreted as a Navilens-augmented QR code, or we accept QR code as a generic term in the meantime. osm.wiki/Proposal_talk:Information=qr_code

However, to pray for having some compatibility, blind=yes + blind:description=Has Navilens codes should still be added at the same time. The latter text is supported by at least OSMAnd. https://taginfo.openstreetmap.org/keys/blind:description#projects

@BCNorwich How is that relevant? This is about them going to use OSM, not advertising to customers.

Has automatic generation of styles been considered? osm.org/user/tyr_asd/diary/405486

Thank for the personal notification. OSM does email you for both diary and changesets. You can see the “unsubscribe” button on the top-right here. Unfortunately the website itself doesn’t notify us. When it was discussed, it seemed there are some concerns about changeset replies being annoying potentially

Can query= load Overpass Turbo permalinks directly?

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 osm.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 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, 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,