[mkgmap-dev] Tiles that crash MapSource with latest Mkgmap

Sun Apr 5 21:09:10 BST 2009

Sorry that I didn't respond earlier. I've been away for most of this 
weekend.

Do you recommend to use the -ea option in my mapbuilding process just to 
notice that a map has failed? I certainly would like to know if it did, 
so I can flag it as such. Or does it do other (possibly unwanted) things 
as well?

Thanks for looking into this. Do you still want me to try find out in 
which Mkgmap version this error occurs first?

  Steve Ratcliffe wrote:
> On Thu, Apr 02, 2009 at 09:47:26PM +0200, Lambertus wrote:
>> I've been busy generating new Garmin tiles, but unfortunately some of  
>> the tiles cause MapSource to crash...
> 
> I've tried to make some similar maps and I think the reason is that the NET
> section is overflowing.
> 
> If assertions are enabled (java -ea ... ) then I get this one triggered.
> 
>   assert offsetNet1 < 0x400000 : "NET 1 offset too large";
> 
> If is leave assertions not enabled then I get a map that appears to be
> broken in qlandkarte in a similar way to the maps you produced.
> 
> So I guess we need to make this a proper error.  And perhaps investigate
> why the NET section is sometimes so big.
> 
>> Some further testing showed that the tile was rendered (using the same  
>> commandline!) without causing the problems using Mkgmap-r830.
> 
> That will be because routing with .osm files was not in r830 :)
> 
> ..Steve
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev