[postgis-devel] Issue 21 in postgis: locate_along_measure: wrong values, invalid data ?

[codesite-noreply at google.com]

Comment #17 on issue 21 by mark.cav... at siriusit.co.uk:  
locate_along_measure: wrong values, invalid data ?
http://code.google.com/p/postgis/issues/detail?id=21

I know that this is a old bug (and even marked as closed), but I've been
investigating Stephen Davies' regression failure and have found that on some
platforms, removing the logic in comment #3 re-introduces floating point  
errors :(

As a result of this, I've realised that the combination of memcpy/clipping  
logic was
wrong and so have spent quite a bit of time testing this on Stephen's  
machine. With
the latest SVN commits to 1.3 branch and trunk, I've re-introduced the  
memcpy() and
adjusted the logic so that his machine now passes regression.

However: the LRS logic is complicated. If you have some LRS test cases  
lying around,
please run them through a recent SVN update and make sure I haven't missed  
any corner
cases.

I don't see this as an emergency fix to push out a 1.3.5 yet, but I've  
backpatched it
as it is likely to catch someone out in the future.


ATB,

Mark.


-- 
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings