Conditional rendering on vector layer intersection#59
Open
alpha-beta-soup wants to merge 3 commits intonextgis:masterfrom
Open
Conditional rendering on vector layer intersection#59alpha-beta-soup wants to merge 3 commits intonextgis:masterfrom
alpha-beta-soup wants to merge 3 commits intonextgis:masterfrom
Conversation
Author
|
cf #56 |
Author
|
Is there anything that you would like to me to do to get this up to a point where it can be merged? |
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
3 participants
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 adds support for the specification of a vector layer in the "Extents" section of the dialogue. If this option is selected, only tiles that intersect this layer's features (not just the feature extents) are rendered. All other possible tiles are ignored. I use a
QgsSpatialIndexto check the intersection betweentile.toRectangle()geometry and features in the specified layer, so it is very fast (tested against a 400MB global coastline Esri Shapefile, and again as a PostGIS layer).An example of the benefit: I used a layer containing only the Australian mainland as my vector intersection source layer. From zooms 0 to 4, only 9 tiles are produced to cover the region of interest, compared to 301 tiles without this additional option.
Let me know if something is not up to scratch.