Treatment of no_data pixels
When using products processed by MAJA 4.5, WASP does not seem to ignore no_data pixels and instead treats them as black. This results in a very dark output products with clearly visible interfaces where partial (i.e. cut) products were used. I would like to know if this is intentional and I should filter out such partial products when selecting inputs for WASP mosaic, is it an unintended behavior or am I doing something wrong?
Context:
I am using L2A products as available via CODE-DE (e.g. direct download via https://finder.code-de.org/). As an example let us consider the following case. I tried to create composite centred around 2022/02/15 from 46 days period. I used the following inputs:
[
'SENTINEL2B_20220310-103636-069_L2A_T32ULC_C_V1-0',
'SENTINEL2A_20220308-104639-812_L2A_T32ULC_C_V1-0',
'SENTINEL2B_20220306-105629-166_L2A_T32ULC_C_V1-0',
'SENTINEL2A_20220305-103641-949_L2A_T32ULC_C_V1-0',
'SENTINEL2B_20220303-104632-812_L2A_T32ULC_C_V1-0',
'SENTINEL2A_20220301-105635-027_L2A_T32ULC_C_V1-0',
'SENTINEL2B_20220228-103634-561_L2A_T32ULC_C_V1-0',
'SENTINEL2A_20220226-104638-709_L2A_T32ULC_C_V1-0',
'SENTINEL2A_20220223-103640-504_L2A_T32ULC_C_V1-0',
'SENTINEL2A_20220219-105633-179_L2A_T32ULC_C_V1-0',
]
and I called the following command
/wasp/bin/WASP --input " ".join(input_metadata_files) --out OUTPUT_PATH --date 20220215 --logging LOG_PATH
I am currently using WASP 1.2 and GDAL 3.1.3
The resulting product (S2_L3_WASP_202202_33UVA on CODE-DE) is dark and has visible darker stripes in places where partial products were used.