-
assigned issue to
spectral metadata handling
Recently we decided to store band-wise wavelength, FWHM, and bad band metadata at band-level. E.g.
Only, if that is not available, we fall back to ENVI classic metadata:
The GDAL Metadata widget, does not correctly deal with that. E.g. center wavelength is taken from band-level in nanometer units and FWHM is taken from dataset-level in micrometer units:
I would suggest to:
- add a column for “Bad band” status (True/False or Yes/No)
- Remove the Wavelength Units combo box. Changing the current unit seam to do nothing anyway.
- Each band can have its own wavelength (nanometers, micrometers), so I would suggest to always show nanometers.
Find attached a single-band subset of the enmap_berlin test raster for reproducing the issue.
Comments (14)
-
reporter -
reporter - edited description
-
reporter - edited description
-
reporter @Benjamin Jakimow you may use the
enmapboxprocessing.rasterreader.RasterReader
to query the relevant band information:
RasterReader.wavelength(bandNo) # in nm RasterReader.fwhm(bandNo) # in nm RasterReader.badBandMultiplier(bandNo) # 1 indicates a valid band (ENVI Classic style)
-
reporter - changed version to 3.9
-
- changed status to open
I think we first need to clearly document the way how and where wavelength information (wavelength unit, wavelengths, FWHM) are
- searched and 2. taken in accouunt in case of competing information
-
reporter I would place this in the Glossary. Here is my first attempt, that needs to be completed:
https://enmap-box.readthedocs.io/en/latest/general/glossary.html#term-wavelengthIf I remember correctly, we wanted to search in the following locations:
- ENVI band domain
- Any other band domain
- ENVI dataset domain
- Any other dataset domain
I will update the Glossary and expand the RasterReader methodes.
I guess you will implement the same logic in your external QPS packages.
-
reporter Sidenote: I really suggest to search in the band domains first, because the dataset domains might be outdated because of prior spectral subsetting.
-
reporter - changed version to 3.10
Let’s don’t rush this.
-
reporter -
assigned issue to
-
assigned issue to
-
reporter Also overhaul other related terms like spectral library, spectral raster layer, etc.
-
reporter I updated the metadata section the glossary, where I detailed the GDAL PAM model, how to manage metadata in the GUI, in an external editor and programmatically.
I also explained how exectly we derive band-wise information like wavelength, fwhm, bad bands, …Have a read here: https://enmap-box.readthedocs.io/en/latest/general/glossary.html#raster-metadata
-
reporter - removed version
Removing version: 3.10 (automated comment)
-
reporter - changed milestone to 3.10 (Feature)
-
assigned issue to
It is now explained in the glossary, how bandwise metadata for WL, FWHM and BadBandMultiplier is derived.
- Log in to comment