Hi Stephen,
please explain I don't see how the suggested change in splitter is related to this. Gerd ________________________________ Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von Steve Sgalowski <steve.sgalow...@gmail.com> Gesendet: Sonntag, 4. Dezember 2016 10:36:02 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Size checks in splitter when splitting Australia in the osm file of 7 gb in size , that would be usefull, as i set the max nodes to 90,000 to make smaller tiles as i get frequently , that there is not enough room in a single gmapsupp.img file to hold all the data . Stephen On Sun, Dec 4, 2016 at 7:28 PM, Gerd Petermann <gpetermann_muenc...@hotmail.com<mailto:gpetermann_muenc...@hotmail.com>> wrote: Hi all, years ago we added a check in splitter r251 to make sure that it doesn't write extremely large tiles. See http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2012q1/013611.html and http://www.mkgmap.org.uk/pipermail/mkgmap-dev/2012q4/015707.html In short: The problem is that the precomp-sea option will add a huge amout of sea polygons to such a tile, another problem is that the bounds option loads a huge amount of data. I've now noticed that this check might not be useful if you use splitter to split a large file into a few smaller tiles, esp. the whole planet with num-tiles=2. I'd like to skip this check when a) --num-tiles is used b) --max-nodes value is large, e.g. higher than 10.000.000 Another option would be to add a new option like --skip-size-check. What do you think? Gerd _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk<mailto:mkgmap-dev@lists.mkgmap.org.uk> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
