I don't see as many issues in your exemple... If École or Musée is part of the name, I don't see why we shall invent a truncated name. It's not because the type is part of the name that we shall remove it. Let's take a more famous example: 'Arc de Triomphe' is the name of a landmark in Paris but it is also an 'Arc' (Arch in English). Same for 'Tour Eiffel' (which is a Tour, i.e. a Tower, but also an antenna). I don't see any solution in renaming them Eiffel or Triomphe. Instead we use the name for the 'name' and add their types (a Tower, an arch, a landmark, an antenna...) in attributes. And if one needs to list all Lakes in a given country then you have your answer: If it is on a geological basis, then he will look for attributes others than 'name'. If it is on a 'per use' basis, i.e. he wants to know which water area is called lake no matter if it is really one or not, then he will look in the name considering all possible translations. If I live next to a place called 'Hudson Bay' then I put name='Hudson Bay' even if some may argue it may not be a Bay. Consequently I don't see a real issue there. Yours LeTopographeFou
Martin, this is already the case. At least it should be like this, if you see places where the name tag is abused for descriptions you should fix it. I admit, it is not always possible to clearly tell which is the correct name, for some kind of things, not even in the real world. The name tag is abused very often and systematically. Let's take at look at this spot in the centre of Paris You can see category names displayed everywhere there, e.g. musium, hotel, school (in French). As a result when you query OSM database for some category items you have to apply algorithms for clearing category names from the name field to get just proper names. Regards, Eugene ср, 5 дек. 2018 г. в 20:25, Martin Koppenhoefer <dieterdre...@gmail.com>:
| ||
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org https://lists.openstreetmap.org/listinfo/tagging
