On Nov 26, 2010, at 9:59 AM, Andy Allan wrote: > On Wed, Nov 24, 2010 at 8:33 PM, Dane Springmeyer <[email protected]> wrote: >> I commented on the ticket with my assessment of the problem, basically that >> only lines are being created as the tag matching for polygons is not robust >> enough in the osm plugin. Look forward to others feedback on how to improve >> this. > > Glib answer: use osm2pgsql and the postgis plugin. > > ... > > Or, in summary, making areas "work properly" would require so much > duplication of osm2pgsql, and keeping up with whatever the OSM > contributers decide is this months' way of doing thing, that mapnik's > implementation is likely to slowly bitrot. I'd leave the OSM plugin as > a quick hack, but when people outgrow it they should look into the > mainstream OSM/mapnik toolchain.
This came up at the most recent Camp Roberts, where Thomas Emge from ESRI was making progress on an Arc editor for OSM. He asked me about the right-hand vs. left-hand rule for polygon rings, Schuyler overheard, and it didn't take long before we all decided that "copy osm2pgsql" was the right answer for all these same reasons. It occurred to me that it might be sensible to pull those rules out of osm2pgsql's source somehow into a separate document, library, resource, guide, or *something* that could be referenced by osm2pgsql as well as other tools written in other languages. Similar to the way that default.style externalizes many of the tag/column mappings, there could be a textual description of the various rules and overrides that make a polygon a polygon. Since you seem to be a maintainer of osm2pgsql, Andy, can I ask whether it would be possible for you to remove or make overrideable the hardcoded dropping of natural=coastline? -mike. ---------------------------------------------------------------- michal migurski- [email protected] 415.558.1610 _______________________________________________ Mapnik-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/mapnik-users
