[mkgmap-dev] Splitter output files are nearly empty

Tue May 3 19:01:14 BST 2011

On Tue, May 03, 2011 at 05:48:55PM +0200, Lambertus wrote:
>Recently I've upgraded upgraded all my Garmin map making tools to the
>latest versions:
>Osmosis 0.39
>Splitter r171
>Mkgmap r1926
>
>Since then I'm having a problem while splitting the planet file: all 
>output files are empty (~160 bytes).

It looks like a splitter problem.

>In de commandline output I notice two things for which I seek input:
>- What does "***** Full GC *****" mean?

I assume that GC means garbage collection. Which JVM are you using? An 
educated guess is that the memory runs out and a "full garbage 
collection" cycle is started as a last resort.

>- Is input from stdin still functional/supported for splitter?

I am not sure. I am using pbf output.

>Below is the commandline and output.
>
>Commandline:
>bunzip2 -d -c -k /home/lambertus/planet.openstreetmap.org/world.osm.bz2
>| ~/garmin/utils/osmosis/bin/osmosis --rx - --tf reject-ways building=*
>--tf reject-nodes type=communication --tf reject-ways admin_level=8 --tf
>reject-ways admin_level=9 --tf reject-ways admin_level=10 --wx file='-'

Why not use

osmosis --rb world.osm.pbf ... --wb filtered-world.osm.pbf

and

... splitter.jar filtered-world.osm.pbf

>| java -Xmx7500m -ea -jar ~/garmin/utils/splitter/splitter.jar 
>--no-trim --cache=cache --mapid=63240001 --max-nodes=1400000 
>--write-kml=world.kml 
>--geonames-file=/home/lambertus/garmin/utils/cities15000.zip /dev/stdin

I am not sure if the --cache option still works. It was sort of 
superceded or made unnecessary by the Protobuf input format support.

Best regards,

	Marko