Lambertus wrote
Tried to split the whole planet using splitter-problem-list-r242.jar and got the following error:
Elapsed time: 16m 0s Memory: Current 1076MB (991MB used, 85MB free) Max 3555MB in 1 file Time: Fri Nov 23 23:03:14 CET 2012 Exact map coverage is (-90.0,-180.0) to (90.0,180.0) Trimmed and rounded map coverage is (-84.990234375,-180.0) to (85.078125,180.0) Splitting nodes into areas containing a maximum of 1,500,000 nodes each... Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 3869 at uk.me.parabola.splitter.DensityMap.getNodeCount(DensityMap.java:85) at uk.me.parabola.splitter.SplittableDensityArea.getSplitHoriz(SplittableDensityArea.java:132) at uk.me.parabola.splitter.SplittableDensityArea.split(SplittableDensityArea.java:75) at uk.me.parabola.splitter.Main.calculateAreas(Main.java:344) at uk.me.parabola.splitter.Main.split(Main.java:190) at uk.me.parabola.splitter.Main.start(Main.java:145) at uk.me.parabola.splitter.Main.main(Main.java:134)
The commandline was:
java -Xmx4000m -ea -jar splitter.jar --output=xml --keep-complete --overlap=0 --no-trim --mapid=1 --max-nodes=1500000 --write-kml=initial.kml --geonames-file=cities15000.zip planet-latest.osm.pbf
Is this a known problem? Searching the list and websearch did not result in a hit...
Yes, today I found that this problem is likely to occur with r242, or to be precise, with splitter and my bounding box patch. It is related to my question regarding alignment. I hope I can fix it soon. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/splitter-problem-list-r242-index-out-of-bound... Sent from the Mkgmap Development mailing list archive at Nabble.com.