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 comparison, Germany split needs 23 minutes, mkgmap 1 hour. The map has ~3,7 GB. (without the message)
Gerd Petermann < gpetermann_muenc...@hotmail.com> hat am 9. November 2019 um 11:04 geschrieben:
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:58An: Development list for mkgmapBetreff: [mkgmap-dev] max-nodes value ...is far above highest node count...
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 regardsArndt_______________________________________________mkgmap-dev mailing list
_______________________________________________ mkgmap-dev mailing list email@example.com http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev