Commit: r911: Fix ordering of NOD 3 entries near 0.
Version 911 was commited by robert on 2009-02-19 09:01:07 +0000 (Thu, 19 Feb 2009) Fix ordering of NOD 3 entries near 0. Was comparing coordinates in map units as unsigned values, now comparing degrees. This should fix inter-tile routing near longitude or latitude zero. Not sure what happens near longitude 180. Also move the comparison out of RouteNode into Coord.
On Thu, 19 Feb 2009 09:01:08 +0000 (GMT) svn commit <svn@mkgmap.org.uk> wrote:
Version 911 was commited by robert on 2009-02-19 09:01:07 +0000 (Thu, 19 Feb 2009)
Fix ordering of NOD 3 entries near 0.
Was comparing coordinates in map units as unsigned values, now comparing degrees. This should fix inter-tile routing near longitude or latitude zero. Not sure what happens near longitude 180.
I just can't see how converting the int values to doubles makes any difference here (apart from slowing the program down!). The values being compared were not unsigned - Java doesn't do unsigned! Cheers, Mark
On Feb 19, 2009, at 23:30, Mark Burton wrote:
I just can't see how converting the int values to doubles makes any difference here (apart from slowing the program down!).
The values being compared were not unsigned - Java doesn't do unsigned!
You're right, of course. My assumption was that map units were unsigned 0..2**24-1, but that's not true. And just now, I've spent an hour experimenting with an old mkgmap.jar from weeks ago, and was very confused why the boundary nodes weren't being sorted at all... Cheers Robert
participants (3)
-
Mark Burton -
Robert Vollmert -
svn commit