We've got beautiful name:LANGUAGE tags, they work, I say let's use them. The English speaking community is well started into this practice (just look at the 1.3 million name:en tags [1]!) - now let's have the rest of us get in on the fun too ;-)
Frederik's called upon the local-first rule a couple of times. It's a really useful principle for deciding conflicting edits, and I read it as "local observation wins". This is good, but it shouldn't mean if you can't read the name of a thing at its place in a specific language it doesn't have one - just like so many other things that aren't labeled in the real world in the local language. In regards to relying on Wikidata for translations: OpenStreetMap is so much bigger than the people who pay attention to the mailing list. If we changed the standing practice of name:LANGUAGE tags and punted translations to Wikidata - how would the average mapper know about it? Would we write Wikidata integration for iD and JOSM to allow for seamless editing of Wikidata translations, then migrate name:LANGUAGE tags off to Wikidata? This seems a lot of effort for unclear gain. [1] Others have already compared the usage of name:en vs name:ru http://taginfo.openstreetmap.org/search?q=name%3Aen http://taginfo.openstreetmap.org/search?q=name%3Aru On Fri, May 29, 2015 at 8:27 AM, SomeoneElse <li...@atownsend.org.uk> wrote: > On 29/05/2015 12:58, moltonel 3x Combo wrote: > >> On 29/05/2015, SomeoneElse <li...@atownsend.org.uk> wrote: >> >>> I'd say that whether or not a name is actually usable to help navigate >>> to a place is a pretty important piece of information. >>> >> True. And that what "name" should give you. The "name:CC" tags should >> not be a hindrance, at most they should be given alongside "name" by >> your satnav. >> >> For example, >>> when processing OSM data for my own use I'll try and drop unsigned names >>> and refs from roads (there's no point in saying "turn left on Foo >>> Street" if "Foo Street" does not appear on the sign). >>> >> That's really neat. How do you know wether a street is signposted or >> not ? I don't know of any tag that gives that info. I can't imagine a >> good heuristic using name:CC. I've added quite a few unsignposted >> street names by asking locals. >> > > I've used name:signed=no (though this is by no means an accepted tag, and > if anyone can come up with a more accepted version that does the same job > I'm all ears). > > Maybe something like "name:signed=en;cy" might solve the "name > verifiability" problem for Abergavenny? > > It's the same >>> principle here - if there are 300 names for a place, are you really >>> suggesting that I have to do an external check to some other database to >>> find that as it's in South Wales, signs are likely to be in Welsh and >>> English, so it's those language names that I need to look out for? >>> >> What's wrong with "name" ? What's the UK policy on the content of >> "name" for places with Welsh and English names ? If you want to see >> Welsh names as often as possible but still make the local name more >> prominent, use "local name (welsh name if different)" in your map >> generating script. >> > > The problem here is that there are two* equally valid and correct "name"s > (in on-the-ground verifiable terms) for Abergavenny. > > Obviously there are more complicated places too - > http://www.openstreetmap.org/node/52241235 and > http://www.openstreetmap.org/node/267762522 immediately sprung to mind > (re the former I thought that it was "An Daingean" that appeared on the > official signs these days?). > > Cheers, > > Andu > > * or possibly three if you count Latin. It wouldn't surprise me if that > wasn't on a "Welcome to Abergavenny" sign somewhere. > > > > _______________________________________________ > talk mailing list > talk@openstreetmap.org > https://lists.openstreetmap.org/listinfo/talk >
_______________________________________________ talk mailing list talk@openstreetmap.org https://lists.openstreetmap.org/listinfo/talk
