Minor detail: the value for the key addr:country=* is just the country code, not the spelled out name. Thus it would be addr:country=TH instead of addr:country=Thailand

Petit détail: La valeur pour la clé addr:country=* est en général que le code pays, pas le nom entier. Donc addr:country=FR au lieu de addr:country=France

Petit détail: La valeur pour la clé addr:country=* est en général que le code pays, pas le nom entier. Donc addr:country=FR au lieu de addr:country=France

Petit détail: La valeur pour la clé addr:country=* est en général que le code pays, pas le nom entier. Donc addr:country=FR au lieu de addr:country=France

I had looked at the wiki page you linked above, but didn't see a mention of the forum discussion or an explanation about this. Even in the forum, I don't see the difference between an OSM level and a value in level:ref being addressed (beyond one being numeric). If I missed it, please quote it.

Your explanation could lead readers to think that mappers simply have to use "1" instead of "1. OG" (or "0" instead of "EG"). This is different from what is explained at wiki.openstreetmap.org/wiki/Key:level and it seems not to have changed materially since 2024.

For locating a defibrillator in an emergency, "level" is probably not even useful, one would want to stay with "level:ref" (or "addr:floor").

https://opening-hours.pages.dev/schweiz-suisse-svizzera-svizra/zug has a few entries from this CS for minor formatting issues.

You might want to use the tool to fix them, but the data may no longer be relevant.

That seems to be what you wrote there, but why?

How would the users of that app have known that 1.OG is level=1 and not level=2 in OSM? I think they just reproduce whatever is signed in the building and the OSM key for that is level:ref or addr:floor, not level.

level:ref=EG
or
addr:floor=EG

would have been preferable. One can't be certain that EG = OSM level 0.

A few of the mailboxes showed up on
https://opening-hours.pages.dev/schweiz-suisse-svizzera-svizra/z%C3%BCrich
for minor formatting issues.

You might want to use that tool to fix them.

Please see note/5421310 about node/12104424899/history/1

relation/11546354 could be a model to follow

Thanks. I meant "Mo-Fr 08:00-17:00", it's just unlikely that this type of office is open on weekends.

Thanks. Not my tool BTW: https://community.openstreetmap.org/t/announcing-an-opening-hours-validator/145214

Bonjour srouge1204. Merci pour la contribution.

Comment on peut vérifier sans se fier à votre publication? "streetlevel imagery" me semble difficile.

official_name is the key for official name tags.

Let's not forget that we try to map reality, not copy an official map.

Please see changeset/164113191

> you merged those perspectives together.

Isn't that natural? Maybe I misunderstand the point of having alt_name=* and old_name=* . Depending on the context, time period and focus, different names are used for a region with a given spatial extent. Also the name can change over time. We should try to generalize the region type.

If the article https://de.wikipedia.org/wiki/Appenzellerland had a section about the history of the region, it would include most of what is now in "Kanton Appenzell" or what HLS/DHS writes about. HLS/DHS/DSS usually writes about administrative areas, thus the cut-off. I don't see a problem with using its key on this feature. Nobody can guarantee any possible interpretation. HLS/DHS/DSS will always be about the history of a place with a cut-off somewhere in the past.

If you need a separate relation for your purposes, please feel free to create it. Splitting it just to match Wikipedia isn't desirable and potentially an endless quest, in my view. Even having three distinct relations is conceivable. Please share your view on how to map these.

node/14014504302/history/1 showed up since, but maybe the report is just too strict. BTW Shouldn't it be Mo-Fr ?

changeset/186225542 Please delete way/1185891197 if that is gone too.

It looks more like personal annotations, possibly not even meant for publication here.

That could explain the edit summary too.