<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Hi Felix,<br><br>yes, confirmed. The output files are much bigger because splitter never writes the<br>version info (timestamp,uid,user,changeset, version).<br>In mkgmap we read the file only once, not multiple times as in splitter,<br>so the advantage is rather small.<br><br>Gerd<br><br><div>> Date: Wed, 7 May 2014 15:20:51 +0200<br>> From: extremecarver@gmail.com<br>> To: mkgmap-dev@lists.mkgmap.org.uk<br>> Subject: Re: [mkgmap-dev] splitter r325: improved split algo and new option<br>> <br>> Well, I just ran splitter on the .osm.pbf file for Asia and austria.<br>> True the split is a bit faster to o5m - but the difference is not so big.<br>> <br>> Compiling from osm.pbf or o5m however - was more or less the same speed...<br>> on the other hand the o5m splitted files use much more space than <br>> osm.pbf (for Austria 293MB vs 450MB - that's about 50% more).<br>> <br>> I will do some further test with input o5m and output osm.pbf vs output <br>> o5m. However if there is also no significant time difference (right now <br>> it's like maybe 10% faster output to o5m instead of osm.pbf) - then I <br>> think I'm gonna stay splitter output at osm.pbf - simply because on my <br>> server I'm a bit harddisk bound (got a large network drive for saving <br>> stuff, but with about 20MB/s vs 150MB/s for the local drive, it's really <br>> only useful to save stuff there - not for working with anything on the <br>> network drive). Splitter input according to the above time measures <br>> however - really seems to profit from o5m...<br>> On 07.05.2014 12:56, Felix Hartmann wrote:<br>> > okay, well the numbers are convincing. I will change to o5m and <br>> > osmupdate too - as soon as I find the time (I do think I need 5-10 <br>> > hours changing my scripts and making sure everything is neatly cut, <br>> > but right now I'm too timelimited to do so)..<br>> > On 07.05.2014 12:15, Bernd Weigelt wrote:<br>> >> Am Mittwoch, 7. Mai 2014, 11:37:58 schrieb Felix Hartmann:<br>> >>> Well I still use pbf and not o5m.<br>> >>> First pbf is smaller..<br>> >>> Second - Geofabrik only offers pbf - that's why I stayed with it.<br>> >>><br>> >>> I don't think I can cut a lot of time by first converting to 05m, then<br>> >>> hand it over to splitter...<br>> >>> Actually I also let splitter output pbf... Maybe I could change that in<br>> >>> future to 05m..<br>> >> I download a planet.pbf, convert it to o5m, time ~50 mins,and cut the <br>> >> needed<br>> >> polies from that planet.o5m. an update of my germany.o5m, 3,2 GB. <br>> >> takes now 3<br>> >> minutes. I update the planet once a month, my extracts everytime i <br>> >> need them.<br>> >><br>> >> thats much faster then download a new pbf everyday or update this pbf.<br>> >> and with the local planet it is easier to create special maps for <br>> >> friends like<br>> >> bonn+100 or dach+<br>> >><br>> >> Bernd<br>> >><br>> >><br>> ><br>> <br>> -- <br>> keep on biking and discovering new trails<br>> <br>> Felix<br>> openmtbmap.org & www.velomap.org<br>> <br>> _______________________________________________<br>> mkgmap-dev mailing list<br>> mkgmap-dev@lists.mkgmap.org.uk<br>> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev<br></div> </div></body>
</html>