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

label raster bands of a layer stack #25027

Open
qgib opened this issue Sep 12, 2017 · 1 comment
Open

label raster bands of a layer stack #25027

qgib opened this issue Sep 12, 2017 · 1 comment
Labels
Feature Request Processing Relating to QGIS Processing framework or individual Processing algorithms

Comments

@qgib
Copy link
Contributor

qgib commented Sep 12, 2017

Author Name: andre mano (andre mano)
Original Redmine Issue: 17128

Redmine category:rasters


When performing a layer stack, sometimes it is convenient to be able to name the bands to be stacked. This label could be coming from the file name or manually provided by the user. This information could be stored in the aux.xml file as described here:

https://lists.osgeo.org/pipermail/gdal-dev/2013-October/037321.html

and here:

https://gis.stackexchange.com/questions/62005/how-to-rename-the-band-names-of-a-layer-stack

As an add-on to this, this feature would be more meaningful if QGIS would be able to read this metadata information (maybe it can already, not sure...)

@qgib qgib added Feature Request Rasters Related to general raster layer handling (not specific data formats) labels May 25, 2019
@alexbruy alexbruy added Processing Relating to QGIS Processing framework or individual Processing algorithms and removed Rasters Related to general raster layer handling (not specific data formats) labels Apr 22, 2020
@Skerre
Copy link

Skerre commented Dec 5, 2023

Has this ever been addressed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Feature Request Processing Relating to QGIS Processing framework or individual Processing algorithms
Projects
None yet
Development

No branches or pull requests

3 participants