Wouter van Kleunen

40 bits NodeID + 24 flags seem reasonable.

wow. Why are they this big when loaded ?

3.5 million references to one OutputObject, right ?

13GB for the full planet is not unreasonable i would say. You don't really have to clamp, you can set the bounding box when converting the planet now right ?...

BTW, the shapesfile already have an rtree right ? So maybe instead of generating references to the outputobjects in the tileindex, you can retrieve them using the rtree already ?

Yes, it would be good to experiment with this. I was expecting the memory usage would go down. But I did not expect this would make such a huge difference....

--include is nice, but it is basicly copying the pre-processed mbtiles to the target mbtiles file, and start processing the osm.pbf. So this could be done using a script: ````...

I have developed a polygon correct approach (remove self-intersection, correct order, correct inners), based on boost geometry: https://github.com/kleunen/boost_geometry_correct The approach for calculating and removing self-intersection is vastly simpler and more...

What is approach that is used now for removing self-intersection from polygons ? I looked through the code, but could not find an approch that is used.

Ah yes. It is common and does work well in many practical cases. But in cases with holes. It will not generate the second polygon. The approach i took does...