Allow running processing tools on grass vector layers #58027
Merged
Conversation
This file contains 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
Remove an outdated constraint preventing processing tools from operating on GRASS provider vector layers. These native QGIS algorithms "just work" with GRASS provider vectors, so there's no reason to explicitly block them anymore...
export the layer to an OGR compatible source first Use the same logic we use eg for auto-exporting memory layers so that GDAL tools "just work" with GRASS provider vector layers
nyalldawson
added
the
Processing
alexbruy
approved these changes
Jul 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Remove an outdated constraint preventing processing tools from operating on GRASS provider vector layers. These native QGIS
algorithms "just work" with GRASS provider vectors, so there's no reason to explicitly block them anymore...