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

Yuri Astrakhan yuriastrakhan at gmail.com
Tue Apr 24 20:08:31 UTC 2018


Adding a language=xx to each feature seems excessive, and will be forgotten
most of the time, unless there is some extensive tool support for it.
Adding it to admin regions seems like a better approach.  Some utility
could then calculate a clean translation map, using admin_level number as
the deciding factor in case of multiple values.

On a side note, a validation tool can than be used to check if "name" has
the same value as "name:xx", where xx is taken from that calculated map.
(I'm sure in many cases it won't match because some places use "lang:local
- lang:en" style of naming for the name tag.

On Tue, Apr 24, 2018 at 10:48 PM, Jo <winfixit at gmail.com> wrote:

> I thought we were already indicating which language name is in, with the
> name:language=:iso tag?
>
> Hmm, apparently not:
>
> https://wiki.openstreetmap.org/wiki/Proposed_features/
> Language_information_for_name
>
> Polyglot
>
> 2018-04-24 21:29 GMT+02:00 Richard Fairhurst <richard at systemed.net>:
>
>> Paul Norman wrote:
>> > If there's agreement that there is a problem here, I could look
>> > at preparing a mechanical edit or MapRoulette challenge to add
>> > name:* tags, e.g. adding name:en to objects in the US with
>> > other name:* tags, and adding name:zh in China. As an
>> > estimate, this would be 115k changes in China, touching 28%
>> > of roads there.
>>
>> This is pretty fragile too, though. Two minutes after the mechanical
>> edit, a
>> newbie will come along and change the name= tag on a random American road
>> from MLK Boulevard to Martin Luther King Boulevard, without knowing they
>> now
>> have to change the name:en= tag as well. Bang, inconsistent data. Fast
>> forward two years and a bunch of history-losing way splits, and it's no
>> longer clear which is the accurate street name and which is the original,
>> mistaken TIGER-imported one.
>>
>> In theory you could bake support for this into editing software (at the
>> expense of complicating the interface), but even if JOSM, iD, Vespucci and
>> P2 all add support, the name= tag is probably the most likely to be
>> changed
>> by minority editors (e.g. mobile or 'quick fix' apps) and it's unlikely
>> they'll all add the same logic.
>>
>> Mateusz Konieczny wrote:
>> > This language=en tag would be placed on a administrative
>> > relation, right?
>>
>> If I read Frederik's proposal right, the language=en tag would be placed
>> on
>> the object with the name tag, though putting it on admin relations is an
>> interesting idea.
>>
>> Richard
>>
>>
>>
>> --
>> Sent from: http://gis.19327.n8.nabble.com/General-Discussion-f5171242.
>> html
>>
>> _______________________________________________
>> talk mailing list
>> talk at openstreetmap.org
>> https://lists.openstreetmap.org/listinfo/talk
>>
>
>
> _______________________________________________
> talk mailing list
> talk at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/talk
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/talk/attachments/20180424/758c4b0e/attachment.html>


More information about the talk mailing list