[Tagging] Slash, space, or spaced hyphen in multi-lingual names
pelderson at gmail.com
Sat Aug 11 06:43:42 UTC 2018
If I knew about usual abbrevs I would probably expand those. If I was not sure, I would not. Usually, looking at existing names in the area tells me what to do. If there are variants on different signs in an area/language I don’t know, I tend to do nothing at all, but if I had to I would either give them all with slashes, or just pick one which makes the most sense to me, both cases assuming I can tell if the same name is meant.
Spelling errors, if I can see that it’s an error, of course I will correct, but if I can’t be sure and still want to map, giving both is not so bad. Some local mapper will eventually correct it, probably.
In any case, if there is an authoratative source and the local usance is to use that, fine with me, then I would of course not “correct” that to any other scheme.
Apart from naming considerations, a line break indicator in long text fields is not a bad idea, I think.
Mvg Peter Elderson
> Op 11 aug. 2018 om 01:14 heeft Jo <winfixit at gmail.com> het volgende geschreven:
> What if the street sign said:
> St Francis St.
> would you be putting that exactly as is in the name tag?
> I would put
> Saint Francis Street
> in it.
> What if there are 3 signs, one with
> St Francis St.
> Saintt Francis St.
> St Francis Street
> It may be a longer street, it may be that time passed by between when those signs were placed. But this does happen.
> Are you reatlly going to put
> name=St Francis St./Saintt Francis St./St Francis Street
> to cover all your bases?
> It's exactly the same situation. You're allowed to use some amount of your brain power to get from what you find on the signs before adding the contents to OSM.
> Op za 11 aug. 2018 om 01:05 schreef Paul Allen <pla16021 at gmail.com>:
>> On Fri, Aug 10, 2018 at 11:38 PM, Jo <winfixit at gmail.com> wrote:
>>> Fortunately all streets in Brussels are already mapped, based on official data from Urbis. So the person from Biel who would prefer to put / in those names doesn't need to to so anymore.
>>> There are definitely street name signs which are wrong. It would be absurd to copy that wrong text into the name tags. It's not so wrong that is something completely different.
>>> Besides many street name signs in Brussels are like this:
>>> Simon Bolivar
>>> Even if that is a spelling error in itself.
>>> name=Avenue Simon Bolivar - Simon Bolivarlaan
>>> name:nl=Simon Bolivarlaan
>>> words glue together in Dutch, like they do in German.
>> Given that situation I'd say the best way to map it is:
>> name=Avenue Simon Bolivar Laan
>> name:nl=Simon Bolivarlaan
>> name:fr=Avenue Simon Bolivar
>>> Anyway, we don't want to put exactly what is on the street name signs in our name tags.
>> Why not? It's what is on the sign. If that is what is on the sign then that is what is ought to be mapped. Or maybe
>> I should change roads into rivers because I prefer rivers and I don't want to map exactly what is on the ground.
>>> It's simply not practical
>> Why? String length isn't a data problem unless the string exceeds some arbitrary length allocated in the
>> database schema. It takes me a lot less time to type a long bilingual name for a highway than to trace the
>> highway itself.
>>> and it would very quickly become nonsensical.
>> If "name=Avenue Simon Bolivar Laan" is nonsensical then the street sign is nonsensical. Complain to your
>> local elected representative and ask him/her for legislation to change the naming conventions of street signs.
>> I find it hard to understand why some mappers do not want to map reality. Unless it's because they wish the street
>> signs were really monolingual. There are people where I live who object to any use of English, should I cater to
>> their whims by amending all names around here to remove the English text or should I map what is there?
> Tagging mailing list
> Tagging at openstreetmap.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Tagging