logo separator

[mkgmap-dev] splitter r241 and mkgmap r2378

From GerdP gpetermann_muenchen at hotmail.com on Wed Nov 21 15:23:51 GMT 2012

Hi all,

I've committed spltter r241:
- added parameter --problem-report. If keep-complete is true this parm can
be used to specify the output file for the generated problem list.
The planet-xxx.kml files are no longer written.

With r240 I started to implement a version info, but this doesn't work yet.
@Steve: please can you review the build script? In the jar file I see two
mkgmap-version.properties contains the correct svn.version
splitter-version.properties has the correct name, but svn.version is

mkgmap r2378 is in the o5m_support branch. It allows to read o5m files.

If you want to try o5m format with splitter and mkgmap, the tool chain
should look similar to this:
(download xxx.osm.pbf) 
osmconvert --drop-version xxx.osm.pbf -o=xxx.o5m 
java [JVM_opts] -jar splitter-problem-list-r241.jar [options] --output=o5m
java [JVM_opts] -jar mkgmap-o5m_support-r2378.jar -c templates.args
java [JVM_opts] -jar mkgmap-o5m_support-r2378.jar *.o5m

A few numbers:
I have a niedersachsen.osm.pbf with ca. 138Mb
osmconvert requires ~ 10 seconds to write niedersachsen.o5m with ca. 173Mb
a) input pbf, output pbf, keep-complete=false, overlap=2000 : 50 seconds, ~
121 MB output
b)input pbf, output pbf, keep-complete=true, overlap=0 : 117 seconds, ~ 118
MB output
c) input o5m, output o5m, keep-complete=false, overlap=2000 : 22 seconds, ~
181 MB output
d) input o5m, output o5m, keep-complete=true, overlap=0 : 49 seconds, ~ 175
MB output

mkgmap runs more or less with the same speed, no matter if o5m or pbf is


View this message in context: http://gis.19327.n5.nabble.com/splitter-r241-and-mkgmap-r2378-tp5736852.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.

More information about the mkgmap-dev mailing list