Thorsten Kukuk wrote >> Yes, seems to be caused by wrong OSM data (adminlevel=14) . >> It seems that mkgmap doesn't verify this value. I'll see where this is >> missing. > > Thanks! > > Thorsten
Turned out the wrong value must be admin_level=15 . r2380 contains the needed check. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/mkgmap-crashes-when-creating-new-boundaries-tp5737419p5737425.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
