[Tagging] Rethinking Map Features

Joseph Eisenberg joseph.eisenberg at gmail.com
Sun Aug 4 15:39:04 UTC 2019

You're right, I was a little confused. Almost all the features on Map
Features have a wiki page (and those that don't should get a page or
more likely be removed), so I understand that they have an OSM
wikibase entry, now, and creating the data item isn't an issue.

But I still can't figure out how to add description in another language?

I tried to get the Indonesian translation by:
1) Open the English wiki page (eg from the link on Map Features in this case)
2) Click on the little pencil to edit the OSM wikibase data item
(which I can't see, because I have images disabled, but I just hunt
3) Click on "edit" next to description
4) Click "all entered languages" - wait, how do I add Indonesian?

Maybe I don't see Indonesian because I'm using a satellite internet
connection from Australia and I haven't edited Indonesian before. I
try clicking on "Configure" next to "In more languages"

I don't see Indonesian there either. So perhaps I have to make a new
wikibase entry for my language? Unfortunately I don't see a link to
make a new wikibase item.

Ok, let's try again with Spanish (EspaƱol), that's on the list...

I still can't figure it out. How do I add a description in another language?

Fortunately I can just make a stub wiki page by:

1) Open the English language page
2) Click on edit
3) Copy the url, add "id:" in front of the page name
4) Copy and paste the ValueDescription / KeyDescription box content
5) Edit the description to Indonesian

It looks like that will still be fewer clicks and fewer mouse strokes
than editing the OSM wikibase data items, and has the benefit of
creating a visible wiki page rather than just editing an obscure data


On 8/4/19, Yuri Astrakhan <yuriastrakhan at gmail.com> wrote:
> Joseph, could you clarify what you mean by "Map Features entry" ?  If you
> only refer to keys/tags/relations/relation roles, than those things are
> automatically created -- an editor only needs to translate them.
> I do agree that if we want to store more diverse data items, we need
> specialized UI, at least for the initial item creation. Luckily, there is a
> large Wikidata community that has already done many such custom UIs. For
> example, Wikidata now stores language data (all lexems), and there is a
> community-created tool to add such words --
> https://tools.wmflabs.org/lexeme-forms/  (I'm not sure if this tool checks
> for duplicates, please check first if you want to add new data). There are
> many other tools we can model after.  Best thing -- those tools don't have
> to be part of the wiki, but can reside anywhere else, and could be in pure
> client-side JavaScript.
> On Sun, Aug 4, 2019 at 2:05 AM Joseph Eisenberg
> <joseph.eisenberg at gmail.com>
> wrote:
>> So far, I've found it very difficult to create and edit new wikibase
>> entries. I don't think it will be easier for Indonesian mappers to
>> create a wikibase entry for every Map Features entry, rather than
>> creating a stub page with a description.
>> The advantage of translating wiki pages for each features is that then
>> there is a human-readable page which can be updated and expanded over
>> time, and also it's clear where the list of feature descriptions are
>> coming from.
>> If you want everyone to create wikibase entries instead, there needs
>> to be a much easier, friendlier interface, available in all languages,
>> and I think such a major change should be discussed and be implemented
>> only if there is consensus that this would be a clear improvement for
>> most language communities.

More information about the Tagging mailing list