вс, 9 дек. 2018 г. в 14:10, Marc Gemis <marc.ge...@gmail.com>:
> We have tags for that (waterway=stream, ditch, ... / amenity=school, > college, university, kindergarten), I don't understand why we should > change the usage of name for that. How would you map American "streamlet", "brook", "creek" and "river" to the two generic "stream" and "river" in OSM? Currently they are just putting in the name field, so the only ways to fide all "brooks" is by searching the name fields which is not a proper database approach. вс, 9 дек. 2018 г. в 14:10, Marc Gemis <marc.ge...@gmail.com>: > Alsmost any proper name can be used without it's common name depending > on the context, e.g. if you are discussing "Atlantic ocean" with your > friend you can say just "Atlantic". > > I don't think this is true in all languages. We never do this e.g. for > the North Sea, which is Noordzee in Dutch. We never say "Noord". The > Dutch name for this sea, is never Noord, in whatever context. For some > other objects we might do drop it, e.g. churches (kerk in Dutch). > > On the other hand if we talk about the "Atheneum van Berchem" , local > people will first drop the name of the village (Berchem) and just use > atheneum. They will not say "Berchem". > > > > > So this topic was raised as a suggestion to distinguish between proper > and common names strictly to put only proper names into "name" field and > common names into some other field taking into account that language > specific common names very often differ from the generic categories adopted > in OSM. > > Without that distinction OSM cannot be called a true geospacial database > because there are no fields which let you query data by it's real category > (common name), you currently have to do that by analysing the "name" filed. > > We have tags for that (waterway=stream, ditch, ... / amenity=school, > college, university, kindergarten), I don't understand why we should > change the usage of name for that. The purpose of tags is to indicate > what the thing is. One can add additional tags to the objects if one > wants, but changing the usage of the name field after more than 10 > years would be very difficult to implement. > > m, > > _______________________________________________ > Tagging mailing list > Tagging@openstreetmap.org > https://lists.openstreetmap.org/listinfo/tagging >
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
