[mkgmap-dev] How to solve/debug weird problem
From Johannes Formann johannes at formann.de on Sat Jan 22 18:08:50 GMT 2011
Hello Marko, Marko Mäkelä <marko.makela at iki.fi> wrote: > Unrelated to this mkgmap bug (or insufficient diagnostics), is there a > reason why you are still using the osm.bz2 input? The osm.pbf is more > compact and can be split quicker. Just tried it again, but got an exception: '-Xms256m' '-Xmx2560m' '-jar' 'splitter.jar' '--resolution=14' '--geonames-file=/home/osm/radkarte/cities1000.zip' '/home/osm/build/germany.osm.pbf' '/home/osm/radkarte/contourdata.osm.gz' The ' characters around the executable and arguments are not part of the command. [apply] cache= [apply] description= [apply] geonames-file=/home/osm/radkarte/cities1000.zip [apply] legacy-mode=false [apply] mapid=63240001 [apply] max-areas=255 [apply] max-nodes=1600000 [apply] max-threads=4 (auto) [apply] mixed=false [apply] no-trim=false [apply] output-dir= [apply] overlap=2000 [apply] resolution=14 [apply] split-file= [apply] status-freq=120 [apply] write-kml= [apply] Elapsed time: 0s Memory: Current 245MB (1MB used, 244MB free) Max 2275MB [apply] Time started: Sat Jan 22 18:47:53 CET 2011 [apply] Map is being split for resolution 14: [apply] - area boundaries are aligned to 0x400 map units [apply] - areas are multiples of 0x800 map units wide and high [apply] The input osm file(s) will be re-parsed during the split (slower) because no --cache parameter was specified [apply] Processing /home/osm/build/germany.osm.pbf... [apply] Error parsing xml from file org.xmlpull.v1.XmlPullParserException: only whitespace content allowed before start tag and not \u0 (position: START_DOCUMENT seen \u0... @1:1) [apply] org.xmlpull.v1.XmlPullParserException: only whitespace content allowed before start tag and not \u0 (position: START_DOCUMENT seen \u0... @1:1) [apply] at org.xmlpull.mxp1.MXParser.parseProlog(MXParser.java:1519) [apply] at org.xmlpull.mxp1.MXParser.nextImpl(MXParser.java:1395) [apply] at org.xmlpull.mxp1.MXParser.next(MXParser.java:1093) [apply] at uk.me.parabola.splitter.AbstractXppParser.parse(AbstractXppParser.java:6 2) [apply] at uk.me.parabola.splitter.Main.parse(Main.java:459) [apply] at uk.me.parabola.splitter.Main.processOsmFiles(Main.java:450) [apply] at uk.me.parabola.splitter.Main.processMap(Main.java:436) [apply] Time finished: Sat Jan 22 18:47:53 CET 2011 [apply] at uk.me.parabola.splitter.Main.calculateAreas(Main.java:326) [apply] Total time taken: 0s [apply] at uk.me.parabola.splitter.Main.split(Main.java:207) [apply] at uk.me.parabola.splitter.Main.start(Main.java:121) [apply] at uk.me.parabola.splitter.Main.main(Main.java:110) [apply] Applied java to 2 files and 0 directories. Some Hints how to use the pbf format? greetings Johannes
- Previous message: [mkgmap-dev] How to solve/debug weird problem
- Next message: [mkgmap-dev] Splitting osm.pbf (Re: How to solve/debug weird problem)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list