[mkgmap-dev] mkgmap crashes when creating new boundaries

Sun Nov 25 08:20:48 GMT 2012

Thorsten Kukuk wrote
> Hi,
> 
> since 2 days mkgmap crashes for me on both machines when generating
> new boundaries.
> The last successful run was for one week, only the OSM data was
> regular updated, mkgmap version should be the same (r2373):
> 
> java.util.concurrent.ExecutionException:
> java.lang.ArrayIndexOutOfBoundsException: 14
>         at java.util.concurrent.FutureTask$Sync.innerGet(Unknown Source)
>         at java.util.concurrent.FutureTask.get(Unknown Source)
>         at
> uk.me.parabola.mkgmap.main.Preparer.runPreparer(Preparer.java:92)
>         at uk.me.parabola.mkgmap.main.Main.endOptions(Main.java:349)
>         at
> uk.me.parabola.mkgmap.CommandArgsReader.readArgs(CommandArgsReader.java:126)
>         at uk.me.parabola.mkgmap.main.Main.main(Main.java:114)
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 14
>         at
> uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryQuadTree$NodeElem.calcLocTags(BoundaryQuadTree.java:1094)
>         at
> uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryQuadTree$NodeElem.
> <init>
> (BoundaryQuadTree.java:1034)
>         at
> uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryQuadTree$Node.add(BoundaryQuadTree.java:639)
>         at
> uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryQuadTree$Node.access$100(BoundaryQuadTree.java:392)
>         at uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryQuadTree.
> <init>
> (BoundaryQuadTree.java:144)
>         at
> uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryUtil.loadQuadTreeFromStream(BoundaryUtil.java:597)
>         at
> uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryUtil.loadQuadTrees(BoundaryUtil.java:153)
>         at
> uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryUtil.loadQuadTree(BoundaryUtil.java:127)
>         at
> uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryPreparer$QuadTreeWorker.call(BoundaryPreparer.java:245)
>         at
> uk.me.parabola.mkgmap.reader.osm.boundary.BoundaryPreparer$QuadTreeWorker.call(BoundaryPreparer.java:230)
>         at java.util.concurrent.FutureTask$Sync.innerRun(Unknown Source)
>         at java.util.concurrent.FutureTask.run(Unknown Source)
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown
> Source)
>         at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
> Source)
>         at java.lang.Thread.run(Unknown Source)
> 
> The arguments:
> osmconvert $PLANET --out-o5m > $TMPDIR/world-$DATE.o5m
> osmfilter $TMPDIR/world-$DATE.o5m --keep-nodes=
> --keep-ways-relations="boundary=administrative =postal_code postal_code="
> --drop="type=street type=associatedStreet type=place type=commune" | gzip
> -9 > $TMPDIR/boundaries-$DATE.osm.gz
> mkgmap --createboundsfile=$TMPDIR/boundaries-$DATE.osm.gz
> --bounds=$TMPDIR/$DATE
> 
> Any ideas?

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.

Gerd

--
View this message in context: http://gis.19327.n5.nabble.com/mkgmap-crashes-when-creating-new-boundaries-tp5737419p5737422.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.