[OSM-talk] How to Translate Strings in OSM to other languages

Shrinivasan T tshrinivasan at gmail.com
Fri May 31 17:47:40 UTC 2019

Thanks for the replies.

I understand that if name:ta tag and its value is available, it is
enough to build Tamil maps.

But, the issue we face is there is not enough name:ta values.


The above is the query for my city railways that dont have tamil translations.

Check the json result here.

Like this, we have tons and tons of POIs, Roads, Ways that are only in english.

Now, we have to translate all these strings to Tamil.

For translation, I got few contributors, who can translation if give
the exact content in a excel sheet or in some translation system.
They are not willing to explore osm, jsom, overpass query etc for
translating the strings.

Hence, I am thinking of myself query osm, get name strings that done
have "name:ta" tag, populate them as a google sheet, share the
translators for translating.
Once they did, I will import the strings to osm with name:ta tag.

To make the translator's job easier, I do a google or bing or wikidata
or some machine translation, so that they can skip the correct one.
They can only fix the wrong translations.

The license of translated text will be public domain. so that we can
use for any purpose.

Hope I explained the plan.

My Questions.

Is mass importing of translated strings accepted?
Do I have to get permission before importing?
Where to ask for permission?
Is there any rate limit for importing strings via programming like x
strings per day or per min etc.


More information about the talk mailing list