Re: [OSM-talk] fixing multipolygons

2008-03-09 Thread Jon Burgess
On Sun, 2008-03-09 at 18:42 +0100, Martijn van Oosterhout wrote: > On Sun, Mar 9, 2008 at 5:58 PM, Jon Burgess <[EMAIL PROTECTED]> wrote: > > It just so happens that the existing multipolygon handling code in > > osm2pgsql will convert these ways into a closed area for the Mapnik > > rendering.

Re: [OSM-talk] fixing multipolygons

2008-03-09 Thread Martijn van Oosterhout
On Sun, Mar 9, 2008 at 5:58 PM, Jon Burgess <[EMAIL PROTECTED]> wrote: > It just so happens that the existing multipolygon handling code in > osm2pgsql will convert these ways into a closed area for the Mapnik > rendering. I can not remember whether this was by accident or design but > it would

Re: [OSM-talk] fixing multipolygons

2008-03-09 Thread Jon Burgess
On Sat, 2008-03-08 at 21:16 +0100, Robert Vollmert wrote: > 393 relations > 235 with non-closed ways > 53 with less than two members > 32 containing ways with less than two nodes > 56 modified relations > Examples of non-closed ways are relation 435 and 436. Both these have 2 ways which toge

[OSM-talk] fixing multipolygons

2008-03-08 Thread Robert Vollmert
Hello, I've attached an ugly python script that does some manipulations to relations in an OSM file it reads from stdin. In particular, for relations that aren't degenerate, it puts role=outer on the largest polygon and role=inner on all others. It also removes tags from inner ways that a