Hierarchically indexed XSorted geometries - #7
Open
patrickbr wants to merge 1 commit into
Open
Conversation
…m/to parameter for both sides, will be used for hiearchical geoms
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR will add simple hierachical indexing to the
XSortedgeometries. The plan is to make the existing methods for DE9IM computation and withinDistance computation onXSortedTuplelists accept ranges on both sides and sort the tuples only within hierarchically indexed quad-tree cells. Before any segment/segment check takes place, an auxiliary quadtree-traversal will first find quadtree cell pairs we have to check.The meta-goal is to make our
withinDistancecomputation faster than thelibgeosimplementation (which uses hierarchical indexing). At the moment,libgeosis around 30% faster on average.