logo separator

[mkgmap-dev] Osmium or Splitter/mkgmap issue?

From Gerd Petermann gpetermann_muenchen at hotmail.com on Wed Jun 10 21:56:21 BST 2020

Hi Enrico,

I use osmconvert. I am not familar with osmosis and I cannot use osmium on Windows.
sort instead of merge sounds good, but I would expect an error message from splitter when data is not sorted correctly.
You should also check the output from splitter reg. the bounds.


Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk> im Auftrag von Enrico Liboni <eliboni at gmail.com>
Gesendet: Mittwoch, 10. Juni 2020 22:49
An: Development list for mkgmap
Betreff: Re: [mkgmap-dev] Osmium or Splitter/mkgmap issue?

Gerd -  however I see no reason why bounds should be different, I use the very same ones. By the way, as per my other email, it seems that usong osmium sort instead of osmium merge does the trick. Perhaps objects are not sorted as osmium merge expects...

What do you usually use to merge pbfs?


On Wed, Jun 10, 2020 at 10:27 PM Gerd Petermann <gpetermann_muenchen at hotmail.com<mailto:gpetermann_muenchen at hotmail.com>> wrote:
Hi Enrico,

maybe the two files 70000001.osm.pbf have different bounds? If one is much larger the difference could be the additional data for sea and background polygons.
In one command you list the input files, in the other you use *.pbf.


Von: mkgmap-dev <mkgmap-dev-bounces at lists.mkgmap.org.uk<mailto:mkgmap-dev-bounces at lists.mkgmap.org.uk>> im Auftrag von Enrico Liboni <eliboni at gmail.com<mailto:eliboni at gmail.com>>
Gesendet: Mittwoch, 10. Juni 2020 22:19
An: Development list for mkgmap
Betreff: [mkgmap-dev] Osmium or Splitter/mkgmap issue?

I'm getting a weird behaviour: I merge <5MB pbfs,  when using osmium I get a 8MB img file while with osmosis it is less than 4MB! The latter seems fine since the initial pbfs are less than 5MB. I'd like to use osmium in my scripts since it performs better.

Am I doing something wrong? Thanks to anyone that could shed some light on this!

# input pbfs
-r--r-----  1 enrico enrico 4673440 Jun 10 21:50 malta-latest.osm.pbf
-r--r-----  1 enrico enrico   15376 Jun 10 21:50 Malta_lon14.03_14.74lat35.65_36.00_view3.osm.pbf
-r--r-----  1 enrico enrico    8300 Jun 10 21:50 Malta_lon14.03_14.74lat36.00_36.18_view3.osm.pbf
# using osmium
$ osmium merge *.pbf -o all.pbf
$ java -jar ../splitter/splitter.jar --mapid=70000001 all.pbf
$ java -jar ../mkgmap/mkgmap.jar  --family-id=10030 --product-id=1  --route --remove-short-arcs  --bounds=../bounds.zip \
 --precomp-sea=../sea.zip  --location-autofill=is_in,nearest --draw-priority=20 --gmapsupp  --index --housenumbers 7000*pbf

-rw-rw-r-- 1 enrico enrico 4695873 Jun 10 21:54 all.pbf
-rw-rw-r-- 1 enrico enrico 4288669 Jun 10 21:54 70000001.osm.pbf
-rw-rw-r-- 1 enrico enrico 7925760 Jun 10 21:55 70000001.img
-rw-rw-r-- 1 enrico enrico 8171520 Jun 10 21:55 gmapsupp.img

# using osmosis
$ ../osmosis/bin/osmosis --rbf ./malta-latest.osm.pbf \
 --rbf ./Malta_lon14.03_14.74lat35.65_36.00_view3.osm.pbf \
 --rbf ./Malta_lon14.03_14.74lat36.00_36.18_view3.osm.pbf \
 --merge --merge --wb all.pbf
$ java -jar ../splitter/splitter.jar --mapid=70000001 all.pbf
$ java -jar ../mkgmap/mkgmap.jar  --family-id=10030 --product-id=1  --route --remove-short-arcs  --bounds=../bounds.zip \
 --precomp-sea=../sea.zip  --location-autofill=is_in,nearest --draw-priority=20 --gmapsupp  --index --housenumbers 7000*pbf

-rw-rw-r--  1 enrico enrico 4680030 Jun 10 22:03 all.pbf
-rw-rw-r--  1 enrico enrico 4288668 Jun 10 22:04 70000001.osm.pbf
-rw-rw-r--  1 enrico enrico 3547136 Jun 10 22:04 70000001.img
-rw-rw-r--  1 enrico enrico 3788800 Jun 10 22:04 gmapsupp.img

Using very latest splitter, mkgmap, and osmium (tried with 1.10 and 1.12 compiled from source...).
Note both gmapsupp.img seems to work just fine on the garmin device.
mkgmap-dev mailing list
mkgmap-dev at lists.mkgmap.org.uk<mailto:mkgmap-dev at lists.mkgmap.org.uk>

More information about the mkgmap-dev mailing list