Node IDs greather than 2.147.483.647 - problems expected ?
It is expected that the node ID count reaches this weak 2.000.000.000. Are there any problems expected when the int max limit (2.147.483.647) will be reached ? Regards Klaus -- View this message in context: http://gis.19327.n5.nabble.com/Node-IDs-greather-than-2-147-483-647-problems... Sent from the Mkgmap Development mailing list archive at Nabble.com.
toc-rox wrote
It is expected that the node ID count reaches this weak 2.000.000.000. Are there any problems expected when the int max limit (2.147.483.647) will be reached ?
No, splitter can handle almost all possible long values (since r192), only Long.MIN_VALUE is reerved. Mkgmap reserves values > 2^62 for fake ids. Ciao, Gerd -- View this message in context: http://gis.19327.n5.nabble.com/Node-IDs-greather-than-2-147-483-647-problems... Sent from the Mkgmap Development mailing list archive at Nabble.com.
participants (2)
-
GerdP -
toc-rox