-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use GDAL settings in "Settings > options" for the Processing tools #40235
Comments
That set of options is not part of the Processing ones (at the bottom of "settings > options"), but it is still a good idea. Setting this as feature request. |
By the way, it could be nice to have those options in every algs involving raster creation. |
@gioman, maybe do I misunderstand you but it's the so-called default profile that does not populate the widgets. Other profiles do. Looks more like a bug to me. |
I'm pretty sure it was already reported, just can't find the ticket. |
the definition of one of the stored GDAL profiles Fixes qgis#41378 Fixes qgis#40235
the definition of one of the stored GDAL profiles Fixes qgis#41378 Fixes qgis#40235 (cherry picked from commit 7454a0e)
@nyalldawson I'm a bit lost... Do you agree this should be fixed on 3.18 bdef9fb ? EDIT : Oh ok, by default it's set to no profile... |
Describe the bug
GDAL algs dialog don't load default Create Options defined in GDAL settings
GDAL Settings:
![image](https://user-images.githubusercontent.com/39594821/99945493-00a26b80-2d75-11eb-82c1-e17d8783d953.png)
"Save raster layer as" dialog
![image](https://user-images.githubusercontent.com/39594821/99945598-30517380-2d75-11eb-92d4-5a78ce04a970.png)
Everything's fine.
"Clip raster by mask layer" dialog
![image](https://user-images.githubusercontent.com/39594821/99945767-82929480-2d75-11eb-87de-b68cebbbe8de.png)
Erg empty create options ! Not fine !
I took this algs as example but similar issue on every gdal algs dialog.
QGIS and OS versions
Tested on a fresh new profile
Win 10 OSGeo4W Qgis 3.16.1
The text was updated successfully, but these errors were encountered: