-
-
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
layer transparency 'no data value' checkbox setting is not preserved during save/load project #18675
Comments
Author Name: Giovanni Manghi (@gioman) Confirmed on master/linux.
|
Author Name: Etienne Tourigny (@etiennesky) Actually I am not sure if the no data value settings (and additional nodata value) should be saved in the project, but rather in the .qml file. |
Author Name: Etienne Tourigny (@etiennesky) fixed in changeset 061941e
|
Author Name: Tom Grundy (Tom Grundy) please reopen - bug fix seems to be broken - see issue #19067
|
Author Name: Tom Grundy (Tom Grundy) I can confirm that the 'new' bug still exists in QGIS 422148c (just installed) |
Author Name: Tom Grundy (Tom Grundy) Here's a good workaround: just change the nodata value of the geotiff itself to some safe value. In this case, white is meant to be transparent, so: gdal_edit.py -a_nodata 255 documented "here":http://www.gdal.org/gdal_edit.html So - the bug remains but the workaround is acceptable, unless you have a raster that really has no nodata value, since you can't disable the handling of a nodata value in qgis. |
Author Name: Jürgen Fischer (@jef-n)
|
Author Name: Alexander Bruy (@alexbruy) Seems fixed in master. Please reopen if necessary
|
Author Name: Tom Grundy (Tom Grundy)
Original Redmine Issue: 10236
Affected QGIS version: master
Redmine category:project_loading/saving
for a geoiff (and probably other raster types) the Layer Properties -> Transparency -> No Data Value checkbox setting is not preserved: uncheck the box, save the project, exit qgis, restart qgis, then load the project, and notice the checkbox is checked. This is important when you want black to be opaque but have other custom pixel values that you want to be transparent. The layers in question do not have an alpha channel.
Related issue(s): #19067 (duplicates)
Redmine related issue(s): 10668
The text was updated successfully, but these errors were encountered: