
Hi all, right after the merge to trunk I noticed that the split algo is not fully predictable (and it never was). It is possible that a file is split very well with a max-nodes=x and much worser with max-nodes=x-1000 or max-nodes=x+1000 This also means that the new --num-tiles option may not work with e.g. --num-tiles=1000 for Europe. I may also disable the support for polygons in combination with --num-tiles. I think nobody needs this and the calculation time can be extreme. I try to find a better algo, in the meantime you may try to increase or decrease max-nodes a little bit if splitter doesn't find a good split. Gerd -- View this message in context: http://gis.19327.n5.nabble.com/splitter-r387-tp5806869.html Sent from the Mkgmap Development mailing list archive at Nabble.com.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Am 20.05.2014 20:14, schrieb GerdP:
It is possible that a file is split very well with a max-nodes=x and much worser with max-nodes=x-1000 or max-nodes=x+1000
Hi Gerd, your x is rounded to 100.000? Henning -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQEcBAEBAgAGBQJTe5+qAAoJEKXggIeC16WPWY4H/AlEvWxCMv2XdrbpDvTmdOkg 9yKBz6CcJ+2OtmIfqz9EMaik4TSGBaVxIB7m6HZTV2ECBWBZ7eQXoWfafXCGM5o6 gNONgcFKCFLuvzyxyjPNy2b6MuOeMpMUMQzI9BDAYO779PA8TIPiltt73bT1pc5A NQ9f5TU+FOdnJ494d5SZYcVLqp9Dn6e4qoGFsQNOp5ty3jsVV5IO1GB8P2Y7e5Z2 pAIIBGUrLAhFAiFW3xPqRC+SRt11EKwCOzMRjKyQQTF2MCddqCcBiIfyIR9aPp1i +pK6T7BE41LseDnSMJ40ePXnrFHyJygl+j9GXMT2ppBVXpJltIVDBhcj5zP55Xg= =dZJZ -----END PGP SIGNATURE-----

Hi Henning, I don't think that it depends on that, but yes, I typically test with default 1600000 and values like 1000000, 1100000 and 1200000 because I saw those in scripts from users. Anyhow, I have ideas how to improve the algo, so I hope the problem can be solved. Gerd osm-8 wrote
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 20.05.2014 20:14, schrieb GerdP:
It is possible that a file is split very well with a max-nodes=x and much worser with max-nodes=x-1000 or max-nodes=x+1000
Hi Gerd, your x is rounded to 100.000?
Henning -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32) Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/
iQEcBAEBAgAGBQJTe5+qAAoJEKXggIeC16WPWY4H/AlEvWxCMv2XdrbpDvTmdOkg 9yKBz6CcJ+2OtmIfqz9EMaik4TSGBaVxIB7m6HZTV2ECBWBZ7eQXoWfafXCGM5o6 gNONgcFKCFLuvzyxyjPNy2b6MuOeMpMUMQzI9BDAYO779PA8TIPiltt73bT1pc5A NQ9f5TU+FOdnJ494d5SZYcVLqp9Dn6e4qoGFsQNOp5ty3jsVV5IO1GB8P2Y7e5Z2 pAIIBGUrLAhFAiFW3xPqRC+SRt11EKwCOzMRjKyQQTF2MCddqCcBiIfyIR9aPp1i +pK6T7BE41LseDnSMJ40ePXnrFHyJygl+j9GXMT2ppBVXpJltIVDBhcj5zP55Xg= =dZJZ -----END PGP SIGNATURE-----
_______________________________________________ mkgmap-dev mailing list
mkgmap-dev@.org
-- View this message in context: http://gis.19327.n5.nabble.com/splitter-r387-tp5806869p5806874.html Sent from the Mkgmap Development mailing list archive at Nabble.com.
participants (2)
-
GerdP
-
Henning Scholland