Felix Hartmann-2 wrote
Why does mkgmap (not mkgmap splitter!) need much more (~20% e.g. on France osm.pbf geofabrik extract) RAM when working with tiles splitted with 250 vs trunk splitter version (using keep-complete and overlap=0)? I didn't try out intermediate versions though. With 8GB Ram on the compiling machine, I needed to back down max-jobs=4 to max-jobs=2 in order to compile France without running out of memory (java xmx 6800M). _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
Probably because it uses it different algorithm to create the tiles. I assume that you also run into a special case, e.g. with coastlines described here: http://gis.19327.n5.nabble.com/splitter-r246-tp5737445p5737749.html Anyhow, the algorithm in r250 is creating too many tiles, so I am working on a different one. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/splitter-r250-and-open-questions-reg-bounding... Sent from the Mkgmap Development mailing list archive at Nabble.com.