Hallo ÖTK, du hast hier einige Tracks doppelt übereinander angelegt und dabei die Relationen unschön verteilt. Kannst du dir das nochmal anschauen?
Beispiel:
way/1507871305
way/1507878417

Thanks! I missed the name *eyerolling-to-self*

Grüß dich! Hier ist irgendwas schief gelaufen, die secondary ist hier einige Male doppelt übereinander: way/1500786061

Ein Full Revert brauchts sicher nicht und bringt auch aktuell bereits schon 9 Konflikte. Danke dir!

Postalische Adressen wiederhergestellt.

Gebäudeumriss wiederhergestellt.

Öffnungszeiten, Telefonnummer und Name laut WIki-Dokumentation korrigiert.

building=yes wurde wieder ergänzt - POI separiert.

Vandalismus revertiert.

Vandalismus revertiert.

Danke dir! Bing und Esri zeigen die Gebäude nach wie vor an, da schadet es aus meiner Sicht nicht den Lifecycle-Prefix noch etwas länger stehen zu lassen.

Does that mean the import guidelines weren't followed?
osm.wiki/Import/Guidelines

Vielleicht hast du den hier verwechselt? way/1360567345

Ich bin's gerade nochmal abgefahren, dort gibt es noch keinen Radweg: https://panoramax.openstreetmap.fr/#focus=pic&pic=355222b6-8599-4cda-af70-610e825b3045

Ich habe es wieder zurück auf proposed gesetzt, das Landratsamt informiert schriftlich, wenn es hier los geht :)

Hi, is there a community discussion about this import? Could you share the link with me? Thank you and have a nice day!

Thanks for outlining the options — that helps clarify the direction.

From the wiki and how the tag is used in practice, I would strongly lean toward:

→ removing the tag entirely on admin_level=2

I think there is still a misunderstanding about what `default_language` is meant to represent.

The wiki is quite explicit:

> “This tag is set to the most likely language of the `name=*` tags in the region … It does not indicate … the official languages of the region.”

and importantly:

> “It is the majority of the other, smaller locations is what causes localization problems.”

So the key point is: **it is about the language of the actual `name=*` values across the dataset**, not about a symbolic or politically neutral country name.

For Switzerland, the vast majority of `name=*` tags (settlements, streets, POIs, etc.) are **not in Latin**. They are in German, French, or Italian depending on the region. Latin is essentially **absent from real `name=*` usage**.

Because of that, setting `default_language=la` does not reflect reality and gives misleading signals to data consumers. A consumer interpreting this tag would reasonably assume that names in Switzerland are primarily in Latin, which is clearly not the case.

Regarding your use case:

> “The default <language> allows users to select the name:<language> for the country (name:la that is) …”

This is not how the tag is intended to be used. `default_language` is **not a selector for which `name:xx` should be preferred for a specific feature (like the country name)**. It is a heuristic to help choose between `name=*` and `name:xx=*` **based on the dominant language of the dataset in that region**.

Using it to force `name:la` for Switzerland effectively repurposes the tag away from its documented meaning.

So in summary:

* The existence of *Confoederatio Helvetica* does not justify `default_language=la`
* Latin is not the language of `name=*` tags in Switzerland
* The tag should reflect actual data usage, not a neutral naming convention for one object

If the goal is to expose or promote `name:la`, that should be handled directly via `name:la=*` (which already exists for the country), not by redefining `default_language`.

Laut Wiki wird tunnel=yes bei waterway's für größere, begehbare Tunnel verwendet. Siehst du diesen Tunnel als begehbar an?
way/48952532

Und bist du dir hier sicher mit "amenity=water_point"? node/7396069334
Siehe Wiki: amenity=water_point beschreibt eine Einrichtung, an der man größere Mengen an "Trinkwasser" für die Füllung eines Süßwasser-Tanks erhalten kann.

Wohnmobile dürfen gar nicht bis zum Wetterkreuz fahren, für wen ist dann die Abfüllung von großen Mengen dort bestimmt?

Hi, am Weg way/5117642 hast du sidewalk:both=no aber gleichzeitig sidewalk:right=yes eingetragen. Wie soll das interpretiert werden?

Hi, bist du dir hier sicher?
way/1360570266

Ich bin erst gestern von Grasbeuren nach Ittendorf auf der K 7782 gefahren und konnte dort keinen Radweg auf der linken Seite sehen.

The argument about Latin is mixing up two different things. According to the OSM wiki, "default_language" is defined as:

> “the most likely language of the "name=*" tags in the region … It does not indicate which languages are spoken in the area, or the official languages of the region.”

In Switzerland, the "name=*" tags are clearly not in Latin, but in German, French, Italian (and sometimes Romansh), depending on the region. Latin is not used for place names, street names, or any other on-the-ground naming.

The wiki also explicitly states:

> “Always use just one language code per region”

and

> “This tag should never be set to multiple semicolon-separated values … because it has no meaning to the data consumer.”

So using "la" here is not appropriate:

* it does not reflect the language of the actual "name=*" tags
* it is based on the Latin form "Confoederatio Helvetica", which is unrelated to how names are tagged in OSM

For Switzerland, the situation is admittedly complex due to multilingual regions. However, the correct conclusions are:

* "default_language=la" is clearly incorrect
* "default_language=de" for the whole country is also questionable
* the most consistent approach is either:

* no "default_language" on admin_level=2, or
* handling it on sub-regions where a dominant language exists

Could you clarify what data consumer benefit you expect from setting "default_language=la"?