I have an issue on how some multipolygons are processed by imposm or osm2pqsql. The problem arises for rendering mixed leaf type forests mapped with a MP. Let's consider such a MP as: * relation: landuse=forest, leaf_type=broadleaved, leaf_cycle=deciduous, type=multipolygon * outer: no tags * inner1: landuse=forest, leaf_type=needleleaved, leaf_cycle=evergreen * inner2: landuse=meadow * inner3: natural=water, water=pond Examples of this kind of MP live in OSM [here][1] and [here][2]. I'm using imposm2 for importing OSM data to make some [paper maps][3] using a custom mapping aimed at rendering the leaf_type. However, with this kind of MP, I got blank holes in the forest for inner rings of type "inner1" that specify a different leaf_type than the relation. Inners like inner2 or inner3 are well rendered. This is not really a Mapnik problem since actually the inners of type "inner1" are not imported in my PostGIS DB using imposm2. Actually, I'm not the only one to face problem with these kind of MP, since the Transport, the [Humanitarian][4] and the OpenCycleMap renderings also show these holes in the MP. I though of a limitation of imposm2 but the Humanitarian rendering is supposed to use osm2pgsql. I didn't check for OpenCycleMap nor the Transport Map. The questions: - Is it a limitation of both imposm2 and (a old version) of osm2pgsql? Can it be circumvented by a pre-processing of the raw osm data*? - Is there a better mapping practice for these MP (that does not trigger JOSM warning)? Thanks for the support, EDIT: https://help.openstreetmap.org/questions/52242/needleleaved-inner-forest-polygon-not-rendered-rendering-or-modelling-problem is a related question juminet \* Actually if I manually delete the inners of type "inner1" from the relation, it works, but I'd like to find a automatic and better solution! [1]: https://www.openstreetmap.org/relation/1653686 [2]: https://www.openstreetmap.org/relation/1652966 [3]: https://github.com/nobohan/OpenArdenneMap [4]: https://www.openstreetmap.org/way/364040915#map=14/49.7378/5.5572&layers=H

I have an issue on how some multipolygons are processed by imposm or osm2pqsql. The problem arises for rendering mixed leaf type forests mapped with a MP. Let's consider such a MP as: * relation: landuse=forest, leaf_type=broadleaved, leaf_cycle=deciduous, type=multipolygon * outer: no tags * inner1: landuse=forest, leaf_type=needleleaved, leaf_cycle=evergreen * inner2: landuse=meadow * inner3: natural=water, water=pond Examples of this kind of MP live in OSM [here][1] and [here][2]. I'm using imposm2 for importing OSM data to make some [paper maps][3] using a custom mapping aimed at rendering the leaf_type. However, with this kind of MP, I got blank holes in the forest for inner rings of type "inner1" that specify a different leaf_type than the relation. Inners like inner2 or inner3 are well rendered. This is not really a Mapnik problem since actually the inners of type "inner1" are not imported in my PostGIS DB using imposm2. Actually, I'm not the only one to face problem with these kind of MP, since the Transport, the [Humanitarian][4] and the OpenCycleMap renderings also show these holes in the MP. I though of a limitation of imposm2 but the Humanitarian rendering is supposed to use osm2pgsql. I didn't check for OpenCycleMap nor the Transport Map. The questions: - Is it a limitation of both imposm2 and (a old version) of osm2pgsql? Can it be circumvented by a pre-processing of the raw osm data*? - Is there a better mapping practice for these MP (that does not trigger JOSM warning)? Thanks for the support, juminet \* Actually if I manually delete the inners of type "inner1" from the relation, it works, but I'd like to find a automatic and better solution! [1]: https://www.openstreetmap.org/relation/1653686 [2]: https://www.openstreetmap.org/relation/1652966 [3]: https://github.com/nobohan/OpenArdenneMap [4]: https://www.openstreetmap.org/way/364040915#map=14/49.7378/5.5572&layers=H