Open radi2015 opened 4 years ago
This is indeed a bug. It looks like one of the CGAlgorithms3D
distance algorithms is not symmetric. Not sure what the exact cause is yet.
Hi. I`m using NetTopologySuite. It has same problem.
In case s<0 && t<0
, CGAlgorithms3D seems to compute only distancePointSegment(A, C, D)
.
Does algorithm need to calculate distancePointSegment(C, A, B)
in the case?
s and t seem to be determined by the order of geometries. (g1,g2 / g2,g1)
out: 0.6460693969920951 5.322947522798961