Hi Gerd
Here is modified patch that handles 4 byte cityPtr in mdr11 and renames
the variable for this to avoid having 2 variable of the same name in
scope. I've named it to be like the equivalent function in mkgmap
I've also got rid of the system.out.printf and fixed some bad
tabbing/indentation
Hi Arndt,
if you search for a line containing
"Creating the initial areas took"
and the reported value is much higher than a few seconds you may try to
decrement the resolution by 1.
BTW: Do you use the default 13 or a higher value? If higher, why?
Gerd
Hi Gerd,
thank you for helping me again!
Sorry, i meant of course "splitter".
So far the message comes only by splitting "Iberia" (Spain, Andorra, Portugal).
splitter needs 16 minutes, mkgmap 2 hours. The map has ~2,4 GB.
For compar
Hi Arndt,
you get this message from splitter, not mkgmap. This is only about performance
of the phase in which splitter calculates the tiles. This depends on the chosen
resolution. The higher the resolution the longer it takes. If you split very
small input files simply ignore this message, but
Good morning,
sometimes mkgmap say something like this:
max-nodes value 160 is far above highest node count 249343 in single grid element, consider using a lower resolution.
What does that mean? The map seems to be OK.
Best reg
Hi Ticker,
reg. Mdr12: I am pretty sure this is no longer used. I don't remember the
details but I think it cannot work with unicode maps.
I guess with "makes no sense" you mean the strange loop with increment of 10240?
And sorry, it is not related to --location-autofill option. This is only need
Version mkgmap-r4356 was committed by gerd on Sat, 09 Nov 2019
Improve testmap to work with --index option, patch
f:\dwnload\temp\indPointSubtype.patch by Ticker Berkin
http://www.mkgmap.org.uk/websvn/revision.php?repname=mkgmap&rev=4356
___
mkgmap-dev
