Opened 11 years ago

Closed 11 years ago

#1650 closed defect (fixed)

Multipolygon: Inner holes don't render in some case

Reported by: Claas Augner Owned by: jburgess777@…
Priority: major Milestone:
Component: mapnik Version:
Keywords: multipolygon Cc:


This problem occurs, for example, with one of the Black Forest's relations:

See map section: (Mapnik doesn't render, while Osmarender does)

The holes were, however, rendered properly (then only in Mapnik) until December 2008.


I have just noticed another multipolygon nearby that is handled quite oddly by Mapnik:

See map section: (Mapnik renders a hole with small forest areas within – according to JOSM validator incorrect –, but none of the holes around; this time Osmarender doesn't render any hole).

Change History (4)

comment:1 Changed 11 years ago by Claas Augner

Meanwhile Osmarender renders the second example properly as well, whereas Mapnik still doesn't.

comment:2 Changed 11 years ago by jburgess777@…

Owner: changed from steve8@… to jburgess777@…

This should be fixed by an update I made to osm2pgsql this weekend which makes it ignore the orientation of the polygon rings. We will need to wait until the weekly import on Wednesday to be sure it works for these examples.

comment:3 Changed 11 years ago by jburgess777@…

It looks like the holes are rendering OK until a diff makes an update to the relation. I have applied a fix to osm2pgsql in r15118 which should fix this case too.

comment:4 Changed 11 years ago by jburgess777@…

Resolution: fixed
Status: newclosed

The 5838 relation now seems to be rendering correctly, but you need to use the export tab to see it at the moment.

The final fix was an error in the tagging, the name=Schwarzwald tag was on the relation instead of the outer way. This prevented osm2pgsql from migrating the landuse=forest tag from the outer way on to the multipolygon.

Note: See TracTickets for help on using tickets.