Re: [mkgmap-dev] Size checks in splitter

2016-12-04 Thread Gerd Petermann
See splitter r487 in the refactoring2 branch. Von: mkgmap-dev im Auftrag von Steve Sgalowski Gesendet: Sonntag, 4. Dezember 2016 10:51:47 An: Development list for mkgmap Betreff: Re: [mkgmap-dev] Size checks in splitter it does to me , when i use a 3rd party

Re: [mkgmap-dev] Size checks in splitter

2016-12-04 Thread Steve Sgalowski
; > > please explain I don't see how the suggested change in splitter is related > to this. > > > Gerd > -- > *Von:* mkgmap-dev im Auftrag von > Steve Sgalowski > *Gesendet:* Sonntag, 4. Dezember 2016 10:36:02 > *An:* Development list fo

Re: [mkgmap-dev] Size checks in splitter

2016-12-04 Thread Gerd Petermann
Hi Stephen, please explain I don't see how the suggested change in splitter is related to this. Gerd Von: mkgmap-dev im Auftrag von Steve Sgalowski Gesendet: Sonntag, 4. Dezember 2016 10:36:02 An: Development list for mkgmap Betreff: Re: [mkgmap-dev]

Re: [mkgmap-dev] Size checks in splitter

2016-12-04 Thread Steve Sgalowski
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 Peterman

[mkgmap-dev] Size checks in splitter

2016-12-04 Thread Gerd Petermann
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-