Skip to content
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

Closed
qgib opened this issue May 12, 2014 · 8 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Project

Comments

@qgib
Copy link
Contributor

qgib commented May 12, 2014

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


@qgib
Copy link
Contributor Author

qgib commented May 13, 2014

Author Name: Giovanni Manghi (@gioman)


Confirmed on master/linux.


  • fixed_version_id was changed from Version 2.2 to Version 2.4
  • operating_system was changed from Windows to
  • os_version was changed from Vista 32 home basic to
  • version was changed from 2.2.0 to master

@qgib
Copy link
Contributor Author

qgib commented May 14, 2014

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.

@qgib
Copy link
Contributor Author

qgib commented May 14, 2014

Author Name: Etienne Tourigny (@etiennesky)


fixed in changeset 061941e


  • status_id was changed from Open to Closed

@qgib
Copy link
Contributor Author

qgib commented Jun 21, 2014

Author Name: Tom Grundy (Tom Grundy)


please reopen - bug fix seems to be broken - see issue #19067


  • status_id was changed from Closed to Reopened

@qgib
Copy link
Contributor Author

qgib commented Jun 22, 2014

Author Name: Tom Grundy (Tom Grundy)


I can confirm that the 'new' bug still exists in QGIS 422148c (just installed)

@qgib
Copy link
Contributor Author

qgib commented Jun 23, 2014

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.

@qgib
Copy link
Contributor Author

qgib commented Jun 28, 2014

Author Name: Jürgen Fischer (@jef-n)


  • fixed_version_id was changed from Version 2.4 to Future Release - High Priority

@qgib
Copy link
Contributor Author

qgib commented Jan 18, 2016

Author Name: Alexander Bruy (@alexbruy)


Seems fixed in master. Please reopen if necessary


  • resolution was changed from to fixed/implemented
  • status_id was changed from Reopened to Closed

@qgib qgib added Bug Either a bug report, or a bug fix. Let's hope for the latter! Project labels May 25, 2019
@qgib qgib added this to the Future Release - High Priority milestone May 25, 2019
@qgib qgib closed this as completed May 25, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Project
Projects
None yet
Development

No branches or pull requests

1 participant