[Backport release-3_38] Allow postgresraster layers as gdal processing tools input #57973
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
We could probably backport everything from that PR except "Fix running GDAL algorithms on cloud storage layers" The rest are legitimate bug fixes (eg fixes running GDAL algorithms on layers loaded with open options, which otherwise will just raise errors) |
…n options or credential options qgis#57884
uclaros
force-pushed
the
fix-gdal-postgresraster-3-38
branch
from
54b9883 to
7147a23
Compare
wonder-sk
approved these changes
Jul 18, 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.
Description
Manual backport #57958 to 3.38
@nyalldawson do you think this is OK, or should I also backport part of #57884 (first 3 commits?) first so that the branches diverge less?