Hi, if you have no good reason to use resolution=16, remove this parm. That will reduce the required memory in this phase. Gerd RheinSkipper wrote
I updated JRE from 1.6 to 1.7, updated osmosis to latest version and gave it 16 GB of memory.
With a small bbox "left=8 right=9 bottom=49.5 top=50.5" osmosis still produces 6 GB of bbox data.
And running splitter on this bbox always results in:
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space at uk.me.parabola.splitter.DensityMap.addNode(DensityMap.java:132) at uk.me.parabola.splitter.DensityMapCollector.processNode(DensityMapCollector. java:58) at uk.me.parabola.splitter.BinaryMapParser.parseDense(BinaryMapParser.java:113) at crosby.binary.BinaryParser.parse(BinaryParser.java:124) at crosby.binary.BinaryParser.handleBlock(BinaryParser.java:68) at crosby.binary.file.FileBlock.process(FileBlock.java:135) at crosby.binary.file.BlockInputStream.process(BlockInputStream.java:34) at uk.me.parabola.splitter.PrecompSeaReader.processMap(PrecompSeaReader.java:85 ) at uk.me.parabola.splitter.Main.calculateAreas(Main.java:479) at uk.me.parabola.splitter.Main.split(Main.java:205) at uk.me.parabola.splitter.Main.start(Main.java:157) at uk.me.parabola.splitter.Main.main(Main.java:146)
Good luck! I fear this might be a hardware problem. Or maybe some kind of multitasking problem in the JRE. If you cannot reproduce it for sure it is unlikely that I will be able to do it.
Gerd
-- View this message in context: http://gis.19327.n5.nabble.com/Splitter-Error- tp5752745p5752812.html Sent from the Mkgmap Development mailing list archive at Nabble.com. _______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/Splitter-Error-tp5752745p5752962.html Sent from the Mkgmap Development mailing list archive at Nabble.com.