[mkgmap-dev] Commit: r911: Fix ordering of NOD 3 entries near 0.
From Mark Burton markb at ordern.com on Thu Feb 19 22:30:10 GMT 2009
On Thu, 19 Feb 2009 09:01:08 +0000 (GMT) svn commit <svn at 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
- Previous message: [mkgmap-dev] Commit: r911: Fix ordering of NOD 3 entries near 0.
- Next message: [mkgmap-dev] Commit: r911: Fix ordering of NOD 3 entries near 0.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the mkgmap-dev mailing list