mkgmap splitter error: java.lang.ArrayIndexOutOfBoundsException -- DensityMap.subset
Anybody seen this before?? - happens with splitter 202 from trunk: java -Xmx6600m -jar splitter.jar --max-nodes=800000 --output=pbf --overlap=5000 --max-areas=255 --geonames-file=cities15000 --description=us-pacific --mapid=65290000 us-pacific.osm.pbf cache= description=us-pacific geonames-file=cities15000 legacy-mode=false mapid=65290000 max-areas=255 max-nodes=800000 max-threads=8 (auto) mixed=false no-trim=false output=pbf output-dir= overlap=5000 resolution=13 split-file= status-freq=120 write-kml= Elapsed time: 0s Memory: Current 122MB (1MB used, 121MB free) Max 5866MB Time started: Tue Nov 06 17:53:17 CET 2012 Map is being split for resolution 13: - area boundaries are aligned to 0x800 map units - areas are multiples of 0x1000 map units wide and high Processing c:\openmtbmap\osmpbf_geofabrik\us-pacific.osm.pbf Bounding box -179.9965 15.92097 -129.7998 72.98845 in 1 file Time: Tue Nov 06 17:53:19 CET 2012 Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 2097151 at uk.me.parabola.splitter.DensityMap.subset(DensityMap.java:118) at uk.me.parabola.splitter.DensityMapCollector.getRoundedArea(DensityMapCollector.java:79) at uk.me.parabola.splitter.Main.calculateAreas(Main.java:303) at uk.me.parabola.splitter.Main.split(Main.java:164) at uk.me.parabola.splitter.Main.start(Main.java:119) at uk.me.parabola.splitter.Main.main(Main.java:108) -- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
Hi Felix, I can't reproduce it with r202, but with r221. Seems that you use the boundingBox.patch and this seems to cause the problem. Correct? Ciao, Gerd Felix Hartmann-2 wrote
Anybody seen this before?? - happens with splitter 202 from trunk: java -Xmx6600m -jar splitter.jar --max-nodes=800000 --output=pbf --overlap=5000 --max-areas=255 --geonames-file=cities15000 --description=us-pacific --mapid=65290000 us-pacific.osm.pbf cache= description=us-pacific geonames-file=cities15000 legacy-mode=false mapid=65290000 max-areas=255 max-nodes=800000 max-threads=8 (auto) mixed=false no-trim=false output=pbf output-dir= overlap=5000 resolution=13 split-file= status-freq=120 write-kml= Elapsed time: 0s Memory: Current 122MB (1MB used, 121MB free) Max 5866MB Time started: Tue Nov 06 17:53:17 CET 2012 Map is being split for resolution 13: - area boundaries are aligned to 0x800 map units - areas are multiples of 0x1000 map units wide and high Processing c:\openmtbmap\osmpbf_geofabrik\us-pacific.osm.pbf Bounding box -179.9965 15.92097 -129.7998 72.98845 in 1 file Time: Tue Nov 06 17:53:19 CET 2012 Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 2097151 at uk.me.parabola.splitter.DensityMap.subset(DensityMap.java:118) at uk.me.parabola.splitter.DensityMapCollector.getRoundedArea(DensityMapCollector.java:79) at uk.me.parabola.splitter.Main.calculateAreas(Main.java:303) at uk.me.parabola.splitter.Main.split(Main.java:164) at uk.me.parabola.splitter.Main.start(Main.java:119) at uk.me.parabola.splitter.Main.main(Main.java:108)
-- keep on biking and discovering new trails
Felix openmtbmap.org & www.velomap.org
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/mkgmap-splitter-error-java-lang-ArrayIndexOut... Sent from the Mkgmap Development mailing list archive at Nabble.com.
yes, I use 202 with boundingBox.patch - forgot to mention it (oh and hope it gets integrated into trunk soon..., I currently don't want to use the splitter branch...). On 06.11.2012 18:42, GerdP wrote:
Hi Felix,
I can't reproduce it with r202, but with r221. Seems that you use the boundingBox.patch and this seems to cause the problem. Correct?
Ciao, Gerd
Felix Hartmann-2 wrote
Anybody seen this before?? - happens with splitter 202 from trunk: java -Xmx6600m -jar splitter.jar --max-nodes=800000 --output=pbf --overlap=5000 --max-areas=255 --geonames-file=cities15000 --description=us-pacific --mapid=65290000 us-pacific.osm.pbf cache= description=us-pacific geonames-file=cities15000 legacy-mode=false mapid=65290000 max-areas=255 max-nodes=800000 max-threads=8 (auto) mixed=false no-trim=false output=pbf output-dir= overlap=5000 resolution=13 split-file= status-freq=120 write-kml= Elapsed time: 0s Memory: Current 122MB (1MB used, 121MB free) Max 5866MB Time started: Tue Nov 06 17:53:17 CET 2012 Map is being split for resolution 13: - area boundaries are aligned to 0x800 map units - areas are multiples of 0x1000 map units wide and high Processing c:\openmtbmap\osmpbf_geofabrik\us-pacific.osm.pbf Bounding box -179.9965 15.92097 -129.7998 72.98845 in 1 file Time: Tue Nov 06 17:53:19 CET 2012 Exception in thread "main" java.lang.ArrayIndexOutOfBoundsException: 2097151 at uk.me.parabola.splitter.DensityMap.subset(DensityMap.java:118) at uk.me.parabola.splitter.DensityMapCollector.getRoundedArea(DensityMapCollector.java:79) at uk.me.parabola.splitter.Main.calculateAreas(Main.java:303) at uk.me.parabola.splitter.Main.split(Main.java:164) at uk.me.parabola.splitter.Main.start(Main.java:119) at uk.me.parabola.splitter.Main.main(Main.java:108)
-- keep on biking and discovering new trails
Felix openmtbmap.org & www.velomap.org
_______________________________________________ mkgmap-dev mailing list mkgmap-dev@.org http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- View this message in context: http://gis.19327.n5.nabble.com/mkgmap-splitter-error-java-lang-ArrayIndexOut... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
Hi Felix, Felix Hartmann-2 wrote
yes, I use 202 with boundingBox.patch - forgot to mention it (oh and hope it gets integrated into trunk soon..., I currently don't want to use the splitter branch...).
somehow the patch caused a bbox to be shifted to a value smaller than -180.0 attached is a new version of the patch that makes sure that this doesn't happen. boundingBox_v2.patch <http://gis.19327.n5.nabble.com/file/n5734525/boundingBox_v2.patch> Gerd -- View this message in context: http://gis.19327.n5.nabble.com/mkgmap-splitter-error-java-lang-ArrayIndexOut... Sent from the Mkgmap Development mailing list archive at Nabble.com.
thanks, that patch fixed it... On 06.11.2012 19:53, GerdP wrote:
Hi Felix,
Felix Hartmann-2 wrote
yes, I use 202 with boundingBox.patch - forgot to mention it (oh and hope it gets integrated into trunk soon..., I currently don't want to use the splitter branch...). somehow the patch caused a bbox to be shifted to a value smaller than -180.0 attached is a new version of the patch that makes sure that this doesn't happen.
boundingBox_v2.patch <http://gis.19327.n5.nabble.com/file/n5734525/boundingBox_v2.patch>
Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/mkgmap-splitter-error-java-lang-ArrayIndexOut... Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list mkgmap-dev@lists.mkgmap.org.uk http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
-- keep on biking and discovering new trails Felix openmtbmap.org & www.velomap.org
participants (2)
-
Felix Hartmann -
GerdP