[Tagging] Can OSM become a geospacial database?

Sergio Manzi smz at smz.it
Thu Dec 6 01:27:14 UTC 2018


Joseph, I take note of your opinion (/but I beg to differ as I was thinking in a general/theoretical way and not specifically to the example brought on by Eugene/).

Just let me clarify that in my examples the English tag were always present (/there were always water=pond/): *that was on purpose* as I never thought about features tagged by language-specific tags *only*.

Cheers,

Sergio


On 2018-12-06 02:16, Joseph Eisenberg wrote:
> It’s difficult enough that Indonesians have to understand English to use OpenStreetMap effectively, or at least have to find English-based tags that match Indonesian words. But if we encourage inventing tagging things in hundreds of languages it will become even more difficult to use this global database.
>
> I’d suggest that the original poster, Eugene Podshivaliv, or other Russian language speakers, talk about what defines the difference between the two types of pond, “пруд” and “копанка”, and then make a new subtag for pond=*
> If there is no better word we could even use pond=копанка for example, but I suspect that it could be translated.
>
> If there is no consistent difference between the two words, then a new tag should not be used.
>
> For example, in America we can call a waterway=stream a “brook”, “creek”, “run” and several other things. These waterways will be tagged waterway=stream or =river (depending on size) with name=“Bull Run”, =“Walker Creek”, =“Johnson’s Brook”, etc. 
>
> We don’t use waterway=creek or waterway=run because there is no consistent difference between these. In fact in Standard British English a Creek is often a tidal channel in a salt marsh or mangroves.
>
> OSM tags should have a consistent definition.
>
> On the other hand, a name can contain whatever the feature is called locally, and this can include pond, lake, mere, tarn, brook, stream, creek, run, etc.
>
> So it would be best to use one of the many existing name tags to include the local term, which is often considered part of the name. 
>
> Eg, alt_name:ru=, loc_name=, official_name= etc, as appropriate based on local usage.
>
> -Joseph
>
> On Thu, Dec 6, 2018 at 9:47 AM Sergio Manzi <smz at smz.it <mailto:smz at smz.it>> wrote:
>
>     I mean, in a more general way and going back to the pond case,
>
>         object 1:
>
>             natural=water
>             water=pond
>             water:RU=пруд
>
>         object 2
>
>             natural=water
>             water=pond
>             water:RU=копанка
>
>     would respect both *our *sensibility to "see" the two objects as ponds and *their *sensibility to "see" the two as whatever they think they are.
>
>
>     On 2018-12-06 01:37, Sergio Manzi wrote:
>>
>>     In this case I think the "alt_name:ru" tag solution could be a very good solution (/but I leave this to our Russian friend to decide.../), but why do you see that preferable to the water:ru=озеро solution?
>>
>
>
> _______________________________________________
> Tagging mailing list
> Tagging at openstreetmap.org
> https://lists.openstreetmap.org/listinfo/tagging
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20181206/e414f7fb/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3675 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://lists.openstreetmap.org/pipermail/tagging/attachments/20181206/e414f7fb/attachment.bin>


More information about the Tagging mailing list