Key:default_language

From OpenStreetMap Wiki
Jump to navigation Jump to search
Public-images-osm logo.svg default_language
Osm element key.svg
Description
The most likely language of the name tags in the region. Edit or translate this description.
Group: Names
Used on these elements
should not be used on nodesshould not be used on waysmay be used on areasmay be used on relations
Useful combination
Wikidata
Status: unspecified

This tag is set to the most likely language of the name=* tags in the region (e.g. a country). It helps data consumers decide which name or name:xx tag to use when drawing localized maps. This tag does not indicate which languages are spoken in the area, or the official languages of the region. It only applies to the name=*, alt_name=*, and the other similar tags.

  • Use the largest possible admin region for this value, e.g. a country relation with admin_level=2.
  • Do not set it on any smaller sub-regions unless their default language is different.
  • A region may contain a sub-region with a different default_language.
  • Always use just one language code per region (see multi-lingual regions below)
  • In some rare cases, additional non-admin regions might be required for the default_language. Try to avoid it if possible.

Multilingual Regions

This tag should never be set to multiple semicolon-separated values, e.g. default_language=fr;en, because it has no meaning to the data consumer. Having two or more language codes does not tell the language of any specific name tag, and therefor should not be used.

If a region uses mixed languages in all of its name tags, e.g. separated by a dash -- "[name_in_en] - [name_in_zh]", you could set default_language=en - zh, but this is not ideal. Please look at all name tags in the region with this Overpass Turbo Query. If you see that the majority of all tags are in a single language, please use that language (unless you can identify sub-areas with different languages). It is ok for the country or city name to have multiple languages in the name - they usually have many other names defined, so localizing them is not a problem. It is the majority of the other, smaller locations is what causes localization problems.

replace last zeros in area() with region's relation ID, but keep initial 3600... - there must be 10 digits. quick link

[out:csv("name")]; area(3600000000)->.boundaryarea;
( node(area.boundaryarea)[name];
  way(area.boundaryarea)[name];
  rel(area.boundaryarea)[name];
); out;

Examples

See also


Sophox query