<div dir="ltr"><div>Acth...</div><div><br></div><div>* osmium sort <i>"...will take roughly 10 times as much memory as the files take on disk in osm.pbf format"</i> - thus I can't pursue this option when dealing with several countries :(</div><div>* osmconvert seems to need o5m, not pbf... I have all pbfs.</div><div><br></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jun 10, 2020 at 10:56 PM Gerd Petermann <<a href="mailto:gpetermann_muenchen@hotmail.com" target="_blank">gpetermann_muenchen@hotmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Enrico,<br>
<br>
I use osmconvert. I am not familar with osmosis and I cannot use osmium on Windows.<br>
sort instead of merge sounds good, but I would expect an error message from splitter when data is not sorted correctly.<br>
You should also check the output from splitter reg. the bounds.<br>
<br>
Gerd<br>
<br>
________________________________________<br>
Von: mkgmap-dev <<a href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk" target="_blank">mkgmap-dev-bounces@lists.mkgmap.org.uk</a>> im Auftrag von Enrico Liboni <<a href="mailto:eliboni@gmail.com" target="_blank">eliboni@gmail.com</a>><br>
Gesendet: Mittwoch, 10. Juni 2020 22:49<br>
An: Development list for mkgmap<br>
Betreff: Re: [mkgmap-dev] Osmium or Splitter/mkgmap issue?<br>
<br>
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...<br>
<br>
What do you usually use to merge pbfs?<br>
<br>
Thanks!<br>
Enrico<br>
<br>
On Wed, Jun 10, 2020 at 10:27 PM Gerd Petermann <<a href="mailto:gpetermann_muenchen@hotmail.com" target="_blank">gpetermann_muenchen@hotmail.com</a><mailto:<a href="mailto:gpetermann_muenchen@hotmail.com" target="_blank">gpetermann_muenchen@hotmail.com</a>>> wrote:<br>
Hi Enrico,<br>
<br>
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.<br>
In one command you list the input files, in the other you use *.pbf.<br>
<br>
Gerd<br>
<br>
________________________________________<br>
Von: mkgmap-dev <<a href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk" target="_blank">mkgmap-dev-bounces@lists.mkgmap.org.uk</a><mailto:<a href="mailto:mkgmap-dev-bounces@lists.mkgmap.org.uk" target="_blank">mkgmap-dev-bounces@lists.mkgmap.org.uk</a>>> im Auftrag von Enrico Liboni <<a href="mailto:eliboni@gmail.com" target="_blank">eliboni@gmail.com</a><mailto:<a href="mailto:eliboni@gmail.com" target="_blank">eliboni@gmail.com</a>>><br>
Gesendet: Mittwoch, 10. Juni 2020 22:19<br>
An: Development list for mkgmap<br>
Betreff: [mkgmap-dev] Osmium or Splitter/mkgmap issue?<br>
<br>
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.<br>
<br>
Am I doing something wrong? Thanks to anyone that could shed some light on this!<br>
<br>
# input pbfs<br>
-r--r----- 1 enrico enrico 4673440 Jun 10 21:50 malta-latest.osm.pbf<br>
-r--r----- 1 enrico enrico 15376 Jun 10 21:50 Malta_lon14.03_14.74lat35.65_36.00_view3.osm.pbf<br>
-r--r----- 1 enrico enrico 8300 Jun 10 21:50 Malta_lon14.03_14.74lat36.00_36.18_view3.osm.pbf<br>
# using osmium<br>
$ osmium merge *.pbf -o all.pbf<br>
$ java -jar ../splitter/splitter.jar --mapid=70000001 all.pbf<br>
$ java -jar ../mkgmap/mkgmap.jar --family-id=10030 --product-id=1 --route --remove-short-arcs --bounds=../bounds.zip \<br>
--precomp-sea=../sea.zip --location-autofill=is_in,nearest --draw-priority=20 --gmapsupp --index --housenumbers 7000*pbf<br>
<br>
-rw-rw-r-- 1 enrico enrico 4695873 Jun 10 21:54 all.pbf<br>
-rw-rw-r-- 1 enrico enrico 4288669 Jun 10 21:54 70000001.osm.pbf<br>
-rw-rw-r-- 1 enrico enrico 7925760 Jun 10 21:55 70000001.img<br>
-rw-rw-r-- 1 enrico enrico 8171520 Jun 10 21:55 gmapsupp.img<br>
<br>
# using osmosis<br>
$ ../osmosis/bin/osmosis --rbf ./malta-latest.osm.pbf \<br>
--rbf ./Malta_lon14.03_14.74lat35.65_36.00_view3.osm.pbf \<br>
--rbf ./Malta_lon14.03_14.74lat36.00_36.18_view3.osm.pbf \<br>
--merge --merge --wb all.pbf<br>
$ java -jar ../splitter/splitter.jar --mapid=70000001 all.pbf<br>
$ java -jar ../mkgmap/mkgmap.jar --family-id=10030 --product-id=1 --route --remove-short-arcs --bounds=../bounds.zip \<br>
--precomp-sea=../sea.zip --location-autofill=is_in,nearest --draw-priority=20 --gmapsupp --index --housenumbers 7000*pbf<br>
<br>
-rw-rw-r-- 1 enrico enrico 4680030 Jun 10 22:03 all.pbf<br>
-rw-rw-r-- 1 enrico enrico 4288668 Jun 10 22:04 70000001.osm.pbf<br>
-rw-rw-r-- 1 enrico enrico 3547136 Jun 10 22:04 70000001.img<br>
-rw-rw-r-- 1 enrico enrico 3788800 Jun 10 22:04 gmapsupp.img<br>
<br>
Using very latest splitter, mkgmap, and osmium (tried with 1.10 and 1.12 compiled from source...).<br>
Note both gmapsupp.img seems to work just fine on the garmin device.<br>
_______________________________________________<br>
mkgmap-dev mailing list<br>
<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a><mailto:<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a>><br>
<a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" rel="noreferrer" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
_______________________________________________<br>
mkgmap-dev mailing list<br>
<a href="mailto:mkgmap-dev@lists.mkgmap.org.uk" target="_blank">mkgmap-dev@lists.mkgmap.org.uk</a><br>
<a href="http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev" rel="noreferrer" target="_blank">http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev</a><br>
</blockquote></div>