[mkgmap-dev] mkgmap ToDo list

Tue Apr 29 14:39:36 BST 2014

Hi Lambertus,

and I guess that even after this optimization you will
see a factor 3 or higher between the largest tile and the smallest.
Can you confirm that?

Gerd

> Date: Tue, 29 Apr 2014 15:32:38 +0200
> From: osm at na1400.info
> To: mkgmap-dev at lists.mkgmap.org.uk
> Subject: Re: [mkgmap-dev] mkgmap ToDo list
> 
> Num-tiles=x would indeed be better for this specific need.
> 
> It is my experience that it regularly takes multiple calls to Splitter 
> to get 2+ sub-tiles when you reduce the max-nodes by 100k for each 
> sub-split attempt. This is what I currently do to get an optimum in 
> tile-size vs total number of tiles.
> 
> 
> 
> On 29/04/2014 15:09, Gerd Petermann wrote:
> > Hi Lambertus,
> >
> > that sounds like a possible change in splitter:
> > Instead of specifying max-nodes you may specify --num-tiles=x
> > and splitter will try to find a split that produces excactly x tiles
> > which are not too narrow and have a node number which is not
> > too far from the average (but still aligned to a multiple of map units
> > as now).
> > So, for your script that means you don't have to find the max-nodes
> > value.
> >
> > I'll think about this again...
> >
> > Gerd
> >
> >  > Date: Tue, 29 Apr 2014 14:59:36 +0200
> >  > From: osm at na1400.info
> >  > To: mkgmap-dev at lists.mkgmap.org.uk
> >  > Subject: Re: [mkgmap-dev] mkgmap ToDo list
> >  >
> >  > While this possibly can be solved in Splitter or Mkgmap, it could also
> >  > be solved by your build-script when you add a maximum tile size check
> >  > and re-split (with a lower number of max-nodes) until you get two or
> >  > more sub-tiles. Granted, this adds complexity to the script but it works
> >  > well for me.
> >  >
> >  > On 25/04/2014 21:54, Henning Scholland wrote:
> >  > > Hi Gerd,
> >  > >
> >  > > I would like to have img-tiles which have globally nearly the same
> >  > > filesize, so that they use the space of devices like eTrex 10.
> >  > >
> >  > > With my actual map I use globally the same value for max-nodes. But the
> >  > > size of the img-tiles differ more then factor 2. Eg. a tile in Germany
> >  > > is between 2 and 5 mb where a tile in China is about 10 mb. If I remove
> >  > > details, this difference will increase, because in Germany more objects
> >  > > will be removed from the img-tile then in China.
> >  > >
> >  > > Henning
> >  > >
> >  > > _______________________________________________
> >  > > mkgmap-dev mailing list
> >  > > mkgmap-dev at lists.mkgmap.org.uk
> >  > > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> >  >
> >  > _______________________________________________
> >  > mkgmap-dev mailing list
> >  > mkgmap-dev at lists.mkgmap.org.uk
> >  > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> >
> >
> > _______________________________________________
> > mkgmap-dev mailing list
> > mkgmap-dev at lists.mkgmap.org.uk
> > http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
> >
> 
> _______________________________________________
> mkgmap-dev mailing list
> mkgmap-dev at lists.mkgmap.org.uk
> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mkgmap.org.uk/pipermail/mkgmap-dev/attachments/20140429/334987ce/attachment-0001.html>