u use
> > o5m format
> > for input and output and give enough heap.
> >
> > Reg. mkgmap performance improvements: yes, that's what I expected.
> > In short, the branch improved the evaluation of tags and the
> > creation of the NOD file.
> >
> > Gerd
> >
> >
> > --------------
Date: Wed, 7 May 2014 11:37:58 +0200
From: extremecar...@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] splitter r325: improved split algo and new option
Well I still use pbf and not o5m.
First pbf is smaller..
Second - Geofabrik only offers pbf - that's
Gerd
Date: Wed, 7 May 2014 16:06:27 +0200
From: extremecar...@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] splitter r325: improved split algo and new option
Well, yes - I mainly tried on Austria now, so results may differ a
bit by country - but
geset, version).
In mkgmap we read the file only once, not multiple times as in splitter,
so the advantage is rather small.
Gerd
> Date: Wed, 7 May 2014 15:20:51 +0200
> From: extremecar...@gmail.com
> To: mkgmap-dev@lists.mkgmap.org.uk
> Subject: Re: [mkgmap-dev] splitter r325: improved s
:51 +0200
> From: extremecar...@gmail.com
> To: mkgmap-dev@lists.mkgmap.org.uk
> Subject: Re: [mkgmap-dev] splitter r325: improved split algo and new option
>
> Well, I just ran splitter on the .osm.pbf file for Asia and austria.
> True the split is a bit faster to o5m - but the dif
Well, I just ran splitter on the .osm.pbf file for Asia and austria.
True the split is a bit faster to o5m - but the difference is not so big.
Compiling from osm.pbf or o5m however - was more or less the same speed...
on the other hand the o5m splitted files use much more space than
osm.pbf (for
okay, well the numbers are convincing. I will change to o5m and
osmupdate too - as soon as I find the time (I do think I need 5-10 hours
changing my scripts and making sure everything is neatly cut, but right
now I'm too timelimited to do so)..
On 07.05.2014 12:15, Bernd Weigelt wrote:
Am Mit
Am Dienstag, 6. Mai 2014, 13:56:42 schrieb Gerd Petermann:
> It is now less likely that splitter creates tiles with a low number of
> nodes, it is more likely that all tiles have nearly the same number of
> nodes, and typically you will see fewer tiles.
> Maybe this also means that you can increa
+0200
From: extremecar...@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] splitter r325: improved split algo and new
option
Well I still use pbf and not o5m.
First pbf is smaller..
Second - Geofabrik only offers pbf - that's why I stayed with it.
I don't think
Am Mittwoch, 7. Mai 2014, 11:37:58 schrieb Felix Hartmann:
> Well I still use pbf and not o5m.
> First pbf is smaller..
> Second - Geofabrik only offers pbf - that's why I stayed with it.
>
> I don't think I can cut a lot of time by first converting to 05m, then
> hand it over to splitter...
> Ac
From: extremecar...@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] splitter r325: improved split algo and new option
Well I still use pbf and not o5m.
First pbf is smaller..
Second - Geofabrik only offers pbf - that's why I stayed wi
0
From: extremecar...@gmail.com <mailto:extremecar...@gmail.com>
To: mkgmap-dev@lists.mkgmap.org.uk
<mailto:mkgmap-dev@lists.mkgmap.org.uk>
Subject: Re: [mkgmap-dev] splitter r325: improved split algo and
new option
Seems to be much better now. I don't think I can increa
Gerd
Date: Wed, 7 May 2014 11:29:10 +0200
From: extremecar...@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] splitter r325: improved split algo and new option
Well - I'll update all my maps on Thursday again, to recheck. Maybe
it has to do with
mkgmap-dev] splitter r325: improved split algo and new
option
Seems to be much better now. I don't think I can increase the
max-nodes value though, but for most maps the new algo creates less
tiles for the same max-nodes value (e.g. Austria from 43 down to 35
for me, with the smallest tile
f splitter + mkgmap to process e.g. Asia?
Gerd
Date: Tue, 6 May 2014 18:22:00 +0200
From: extremecar...@gmail.com
To: mkgmap-dev@lists.mkgmap.org.uk
Subject: Re: [mkgmap-dev] splitter r325: improved split algo and new option
Seems to be much better now. I don't think I c
Hi Felix,
fine :-)
And yes, I meant max-nodes may have to be decreased, not increased. Sorry
for the typo.
Reg. speed: That's unexpected. It should not take much time to find the
better split,
(a few seconds) and typically safe some time to have fewer tiles.
I'll check that tomorrow.
Gerd
Feli
Seems to be much better now. I don't think I can increase the max-nodes
value though, but for most maps the new algo creates less tiles for the
same max-nodes value (e.g. Austria from 43 down to 35 for me, with the
smallest tile now around 5MB instead of 2.8, and the biggest 12MB
instead of 11M
Hi all,
I've applied num-tiles-v1.patch and improved the split algo, see
http://gis.19327.n5.nabble.com/mkgmap-ToDo-list-tp5803388p5805165.html
It is now less likely that splitter creates tiles with a low number of
nodes, it is more likely that all tiles have nearly the same number of nodes,
18 matches
Mail list logo
