Something went wrong while setting issue due date.
KDTree cannot handle cases near -180, 180 lon correctly
Closed
KDTree cannot handle cases near -180, 180 lon correctly
The KDTree may give the incorrect answer for query records who are close to the -180, 180 boundary line.
I may need to handle a special case for lon...
Related merge requests
1
added BUG label
created merge request !3 (merged) to address this issue
mentioned in merge request !3 (merged)
mentioned in commit 086e5b37
closed via merge request !3 (merged)
Please register or sign in to reply