[mkgmap-dev] mkgmap ToDo list

Fri Apr 25 21:33:47 BST 2014

Hi Henning,

okay, got it. 
You mentioned the density file written by splitter. I have no idea how,
but you may find a way to manipulate the values in that file.

DensityMap.readMap() contains the code to read that file
which simply represents the content of the density map 
(x and y index and number of nodes in each line)
If splitter finds a file density.txt in its working directory, it will read
that file
instead of the input file(s) to calculate the areas.list.

What you need now is a routine that calculates a weight factor for each
field
in the density map based on the number of bytes in the corresponding img
file,
which you can use to lower the number of nodes.

The problem is: You have only one factor for many elements in the grid
of the density map, and I see no way to calculate something more detailed
in mkgmap.

Does that help you somehow?

Gerd

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 .org

> http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev

--
View this message in context: http://gis.19327.n5.nabble.com/mkgmap-ToDo-list-tp5803388p5804194.html
Sent from the Mkgmap Development mailing list archive at Nabble.com.