On 2013-07-25 10:54, Martin
Koppenhoefer wrote :
I'm glad that you come back to the heart of the matter which is to know whether a key describes an object or an attribute of an object and that the keys definitions in the wiki should indicate that, so that everyone agree and make a consistent database. And we disagree indeed regarding leisure being an object. IMHO, there is no such object as "a leisure". In my example, we have an object "water=" that is used for "leisure=", which is an attribute of the water. And the type of leisure is further described with fishing. Which of these two forms depends on our decision that an object can be used for one or several types of leisures: water=basin leisure=fishing or leisure=yes fishing=yes in my case water=pool leisure=swimming or leisure-yes swimming=yes in your case Now, regarding the fact that fishing= may mean several things, indeed and why not. Fishing may be an attribute applying to leisure or one to a shop that's selling fishing material. It's up to the wiki to possibly make a list of the allowed attributes for an object or an attribute. And now, regarding my practical issue: Tag en conflitIn my mind, the object is "water=basin", and, although it's not natural, Osmose insists on calling it a natural, "natural=water" with an attribute I can find no better than "water=pond". Then, like you, Osmose comes to say that the object is in fact a leisure: "leisure=fishing". And that, as quite rightly two objects exclude one another, leisure excludes water. How then can we know in what we are fishing: a pond or a river? Can we make a practical decision, to write in the wiki so that I and Osmose can apply it? My 2 €¢ are that it should resemble this: water=basin natural=no leisure=yes (industrial=no) fishing=yes pay=yes Cheers, |
_______________________________________________ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging