We have many questions around the availability of S2 L2A and S1 RTC products in different buckets. We appreciate any pointers.
We have been getting S2 L2A images from this S3 bucket: sentinel-s2-l2a (Sentinel-2 - Registry of Open Data on AWS by Sinergise).
It appears not all images we expect to be in that bucket are present.
We see that some of the images missing from the sentinel-s2-l2a bucket are in this bucket: eodata
aws s3 ls s3://eodata/Sentinel-2/MSI/L2A_N0500/
What is the difference between the buckets and should we use N0500 the latest available processing version in the eodata bucket?
Will N0500 have all images from L2 first light to present?
Which processing version would be the most complete?
Also, there appear to be newer processing versions than N0500: S2 Processing
Copernicus Dashboard - Processors Releases | ESA
Which one should be use please?
Does eodata/Sentinel-2/MSI/L2A_N0500 have cloud cover % in the metadata? sentinel-s2-l2a does not so we need to calculate if from SLC 20m also b/c SLC 60m is not always available in sentinel-s2-l2a.
For some S2 tiles we know that there are multiple images on a given date but this does not appear to be the case for those same tiles and dates on eodata/Sentinel-2/MSI/L2A_N0500 for those dates. In eodata there is only one image.
As for S1 RTC data (s3 ls s3://eodata/Sentinel-1-RTC/SAR/), is this 20m data? Does the bucket have a full collection?
It is gridded to S2 tiles? Or else how is it gridded?
How is it different from RTC from Alaska SAR?
Alaska SAR produces RTC on demand with up to x images per month and account.