On 12/27/2011 01:49 PM, GerdP wrote: >> I don't know why this happens now, and it really shouldn't (apart from >> > the timestamps which are easy to ignore), I will try to find out why. >> > > thanks, tt would be great if this could be changed.
I discovered that it is only boundary lines that are affected. I didn't quite track down the exact cause, but I guess that the relation members are held in a hash map somewhere and are read out in an indeterminate order. Whatever the exact reason, adding a hashCode() method to the Way class prevents the random ordering, so I shall commit that change. ..Steve _______________________________________________ mkgmap-dev mailing list [email protected] http://www.mkgmap.org.uk/mailman/listinfo/mkgmap-dev
