Add GeometryCollection dimension cache #1103
Merged
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.
Heterogeneous (mixed)
GeometryCollection
s have to use an O(n) algorithm to determine the dimensions of the elements. This causes performance issues in algorithms which use the dimension of the collection (see #1100).This PR solves this problem by caching the computed dimensions of a GeometryCollection. It adds a single reference to each collection object, but the actual cache is lazily created when dimension information is accessed.
For example, for a
CoverageUnion
of a grid of 1M rectangles this improves the performance from 17 s to 370 ms (45x).Fixes #1100