[OSM-talk] Name:* tags in the local language

Daniel Koć daniel at xn--ko-wla.pl
Thu Apr 26 11:35:10 UTC 2018

W dniu 26.04.2018 o 11:51, Mateusz Konieczny pisze:
> It is not handling
> - regions with more than one widespread language
> - features that have name tag in an atypical language

In my opinion there's no single solution for atypical cases, yet it's
sane to start with defaults. It can be used on many levels and region
can have more than one language defined, just like Janjko has shown:

Country A - official_language=hr
Region B - official_language=hr;it
City C - official_language=it

When a data consumer tries to find what is the official language for
street D, she finds that city C uses "it", so it's enough to know that
the street should be also in "it". Speaking of regions this is the
proper handling in my opinion - in region B you can for example use both
languages or choose the one you prefer, it's up to you.

But we don't have to stop with level 2, 4, or 6. If - for some reason -
part of the city is different and we have no way to show the borders of
the area, one can add official_language=* for the streets or objects in
this particular area. Of course instead of official_language we may use
default_language=* or common_language=* tag or something similar, the
same as the users have to choose common name for name=*.

This way we can always assume some language for the (administrative)
area, but if it's not true locally, we can be more specific, up to the
single objects.

"My method is uncertain/ It's a mess but it's working" [F. Apple]

More information about the talk mailing list