Hello all,
I have been downloading some Sentinel 2 L2A TCI scenes from the AWS registry. I noticed some scenes are missing a significant number of pixels.
This is occurring in both the TIF and JP2 files and it seems something similar to this post could be happening where a nodata value of 0 is being set somewhere.
An example of what it looks like for one of the scenes I downloaded:
Here are links to one such scene where I am seeing the issue:
s3://sentinel-s2-l2a/tiles/15/S/VU/2024/11/26/0/R10m/TCI.jp2
It appears from the above linked post that this is a known bug with sen2cor. Does anyone know if there is a planned fix to this? Thanks!
That does sound like Problems with COG images downloaded from the Planetary Computer API, though in that case I thought it was only related to COGs and not the JP2000 files, but I might be wrong about that.
I reported that upstream in What is the valid range for the TCI product? - Optical Toolbox - STEP Forum, and ESA (who is at least involved in sen2cor’s development) confirmed the bug. I don’t see a confirmation of a fix in that post but I thought they’d announced a fix.
Assuming it’s fixed in sen2cor, you’d need to check with whoever is hosting the L2A imagery (is that Synergise?) and see how they’re getting it. I thought that Synergise was getting L2A directly, not not running sen2cor, but again I could be misremembering.
I see, thanks for your help! I will try checking with Sinergise
