Frederik Ramm wrote: > While multipolygons with more than one outer *ring* are uncommon, > those with more than one outer *way* are heavily used where I live
That's all right, everyone where you live uses JOSM anyway. :) The issue from my point of view is one of UI. I can't countenance a UI, or a render, that is any different for tagging shapes depending on whether they have holes in or not. So P2's tagging code would need to get some layer of indirection saying "if this is a multipolygon, the tag panel needs to deal with the relation tags, unless there are already tags on the way. Otherwise it needs to deal with the way tags". Meanwhile, the rendering code would need to render fills differently for items with more than one outer way (which is additionally complicated by the fact they might not all be loaded yet). That's far too much like brainache for me to want to code, especially when that code will need rewriting in a year or so. But if someone else who does come from a land where people use bonkers complicated multipolygons came up with a decent patch, I imagine we'd be very happy to accept it. cheers Richard -- View this message in context: http://gis.638310.n2.nabble.com/osm2pgsql-and-only-named-multipolygons-tp6858105p6862246.html Sent from the Developer Discussion mailing list archive at Nabble.com. _______________________________________________ dev mailing list [email protected] http://lists.openstreetmap.org/listinfo/dev
