On Tue, May 1, 2012 at 6:04 AM, Martin Koppenhoefer <dieterdre...@gmail.com> wrote: > 2012/5/1 Pieren <pier...@gmail.com>: >> Not only mine. I'm still waiting at least a single example where a >> closed way for platforms is not an area (and rendering issue cannot be >> fixed by splitting the way for instance). > > > our data model should not need hacks like "split the way to fix > rendering issues". It should be clear whether an object is an area or > not (that's why I prefer explicit area=yes/no for cases which might be > ambiguous).
What about closed ways tagged with barrier=* and some other ambiguous *=* (e.g. barrier=hedge & amenity=marketplace). I guess you could just put the amenity=marketplace on a multipolygon, and keep the barrier=hedge/area=no. So the official behavior of routers/renderers/etc on closed ways ambiguously not tagged as area=yes/no is undefined, though it is strongly suggested that data users assume area=no for highway=* and barrier=*. Maybe we even carve out an exception for highway=* and barrier=*, though I'd just as well we tag them explicitly too, whenever they are closed. Yes, I think this is a good solution. _______________________________________________ Tagging mailing list Tagging@openstreetmap.org http://lists.openstreetmap.org/listinfo/tagging
