Wouter van Kleunen

Yes the issue with the ijsselmeer we had before. The default style only renders water from osm up to zoom level 8. But large lakes are visible after zoom level...

The cleanup at the end is not even needed. The data structures inside the mmap file get deallocated and then when all this is done. The complete file gets deleted...

"Filled the tileset with good things" is the last line in tilemaker.cpp, but after this all the destructors are run. I also ran a planet conversion, it did nog hang...

I am not sure if I now used my adapted style for this.

maybe something with 'Use OsmID to lookup generated geometry'. that would be the most likely candidate to cause this issue.

I think i actually see the issue with this commit Try #317, i have not tested it yet

Yes, it does seem to be a collision between the OSMIDs. That is why i added the extra two bits and the | OSMID_RELATION. To make the osm id unique....

Indeed what toshelp is saying, i changed the behaviour of the is_valid check to not process self_intersecting polygons. On my map i had an issue that a tile was rendered...

Try also run with --verbose, to see if the polygon is mentioned

Also on openstreetmap.org itself, you see rendering issues with this relation: