-
Notifications
You must be signed in to change notification settings - Fork 154
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor spatial join tests #1019
Refactor spatial join tests #1019
Conversation
I think the reason these were split out was so But if we're not expecting to need to change the implementations of these routines much anymore, I'm OK merging these tests. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approving CMake changes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see that tests are incremental checkpoints for developers to validate the correctness of the function. It would be nice to leave some comments in the test block for bounding_boxes
API and mention it's a checkpoint for this API.
/merge |
Description
Closes #1006
Closes #1007
I realized that the
join_quadtree_and_bounding_boxes()
tests are redundant to thequadtree_point_in_polygon
tests andquadtree_point_to_nearest_linestring
tests since the "small" test is duplicated in those. So I eliminated that test and added expectations forjoin_quadtree_and_bounding_boxes
in those tests.Checklist