The Sentinel-2 L2A product seems to have inconsistencies in the setting of the nodata value in the GeoTiff metadata.
While in general the value is expected to be set to 0, there seem to be a number of cases in which the nodata value is not set at all.
This can easily lead to downstream processing issues if not handled carefully, for example when harmonizing the pre- and post baseline 4.0 data.
An example with no nodata value set is:
https://sentinel2l2a01.blob.core.windows.net/sentinel2-l2/30/U/YV/2023/05/20/S2B_MSIL2A_20230520T104629_N0509_R051_T30UYV_20230520T152439.SAFE/GRANULE/L2A_T30UYV_A032395_20230520T104624/IMG_DATA/R10m/T30UYV_20230520T104629_B03_10m.tif
The Sentinel-2 L2A product seems to have inconsistencies in the setting of the
nodatavalue in the GeoTiff metadata.While in general the value is expected to be set to 0, there seem to be a number of cases in which the nodata value is not set at all.
This can easily lead to downstream processing issues if not handled carefully, for example when harmonizing the pre- and post baseline 4.0 data.
An example with no
nodatavalue set is:https://sentinel2l2a01.blob.core.windows.net/sentinel2-l2/30/U/YV/2023/05/20/S2B_MSIL2A_20230520T104629_N0509_R051_T30UYV_20230520T152439.SAFE/GRANULE/L2A_T30UYV_A032395_20230520T104624/IMG_DATA/R10m/T30UYV_20230520T104629_B03_10m.tif