Strange outputs from majamask
System information
- majamask 1.0.0
Describe the current behavior
When a pixel is in a no data area of the raster but over water, the output pixel of rastermask is set as water pixel (value 5). It is quite strange but coherent with the code which compute the value from MG2 set to 0x0000001 and from CLM set to 0x00000000. The EDG mask is not used to spot the no data pixel. The issue is perhaps related to the fact that MG2 is set to 1 by MAJA even if the EDG value is equal to 1. It is the expected behavior?
When a pixel is in a no data area of the raster but over land, the output pixel of rastermask is set as Valid Reflectance (value 0). Use in this case Valid Reflectance seems quite abusive, I think.
Describe the expected behavior
Urgency/Criticity
- Urgency: Low
- Criticity: Low
Code to reproduce the issue
Use a coastal product with orbit border as SENTINEL2A_20231105-141051-796_L2A_T22NBM_C_V3-1