Inconsistent naming of S2A bands (v20180419.0)
Posted: Tue May 15, 2018 6:25 am
Hi all
The naming of the 'rho' datasets is derived from the band central wavelength information in the metadata file (e.g. MTD_MSIL1C.xml). Due to the change of the Sentinel-2A relative spectral response (RSR) function at the end of 2017, the acquisitions after 2018-01-15 have slightly wavelengths and thus names for the bands. For example band 1 was 444 nm and is now 443 nm, band 4 was 664 nm and is now 665.
I will adopt a new naming scheme based on the RSR weighted wavelength (as is done for Landsat) in the next version of ACOLITE.
Quinten
The naming of the 'rho' datasets is derived from the band central wavelength information in the metadata file (e.g. MTD_MSIL1C.xml). Due to the change of the Sentinel-2A relative spectral response (RSR) function at the end of 2017, the acquisitions after 2018-01-15 have slightly wavelengths and thus names for the bands. For example band 1 was 444 nm and is now 443 nm, band 4 was 664 nm and is now 665.
I will adopt a new naming scheme based on the RSR weighted wavelength (as is done for Landsat) in the next version of ACOLITE.
Quinten