Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sentinel-2 "eo:cloud_cover" doesn't match between v0 and v1 #5

Open
waltersdan opened this issue Jun 9, 2023 · 2 comments
Open

Sentinel-2 "eo:cloud_cover" doesn't match between v0 and v1 #5

waltersdan opened this issue Jun 9, 2023 · 2 comments
Labels
check-after-reprocessing Issues that we should re-check after the s2 reprocessing

Comments

@waltersdan
Copy link

When querying Sentinel-2 l2a imagery from these two collections:
https://earth-search.aws.element84.com/v0/collections/sentinel-s2-l2a-cogs
https://earth-search.aws.element84.com/v1/collections/sentinel-2-l2a
I can get the exact same images, except the property "eo:cloud_cover" is different for matching images.

For example, these are the eo:cloud_cover values for a set of images from v0:
56.36
87.25
100.
97.13
And the same images from v1:
78.148019
92.783248
99.999213
86.64819
I have verified they are the exact same images and have the exact same pixel values for several bands including SCL. The only difference seems to be the metadata

@tnigon
Copy link

tnigon commented Jun 12, 2023

I've noticed this as well. Although I do not know for sure, I'm presuming it has to do with Earthsearch V1 using the most recent version of Sen2Cor, which was released on December 6, 2022.

I'd be interested in confirmation of this, as well as any other nuances on the topic.

@matthewhanson
Copy link
Member

Yes, this may be an issue with the fact that the processing baseline between the L2 scene in Earth Search and the linked to L1 scene may have different processing baselines. With the new reprocessing happening by ESA we hopefully can get this fixed. Stay tuned to an update on the mailing list (and will post an issue in this repo).

@gadomski gadomski added the check-after-reprocessing Issues that we should re-check after the s2 reprocessing label Dec 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
check-after-reprocessing Issues that we should re-check after the s2 reprocessing
Projects
None yet
Development

No branches or pull requests

4 participants