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 if you split e.g. a well 
mapped area like Germany you simply waste time and energy when you chose a bad 
combination of max-nodes and resolution.


Von: mkgmap-dev <mkgmap-dev-boun...@lists.mkgmap.org.uk> im Auftrag von Arndt 
Röhrig <ar...@speichenkarte.de>
Gesendet: Samstag, 9. November 2019 10:58
An: Development list for mkgmap
Betreff: [mkgmap-dev] max-nodes value ...is far above highest node count...

Good morning,

sometimes mkgmap say something like this:
max-nodes value 1600000 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 regards
mkgmap-dev mailing list

Reply via email to