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

radiometric offsets L1C #7

Closed
safalabolo opened this issue May 13, 2024 · 7 comments
Closed

radiometric offsets L1C #7

safalabolo opened this issue May 13, 2024 · 7 comments

Comments

@safalabolo
Copy link

A simple question: are the Sentinel-2 L1C bands, before applying super resolution, corrected with "radiometric offsets" (https://scihub.copernicus.eu/news/News00931)?

@jmichel-otb
Copy link
Collaborator

No the radiometric offsets are not applied beforehand. Feel free to apply them on super-resolved products.

@jmichel-otb
Copy link
Collaborator

A FAQ section has been added in README with this information.

@jmichel-otb
Copy link
Collaborator

I realize that I may have mis-interpreted the issue. Upon reading of the L1C product, we apply a -1000 radiometric offset to reflectances if required.

@safalabolo
Copy link
Author

@jmichel-otb
I also imagine when talking about the L2A (theia) level, is that correct?

@jmichel-otb
Copy link
Collaborator

I think in this case the offset is handled in MAJA (the L1C -> L2A processor).

I updated the FAQ.

@eomasters-repos
Copy link

I've also stumbled upon this offset. Compring the read data did not provide the same values as reading the data with other tools.
I think the radiometric offset of -1000 should actually not be applied. This offset is applied by the sensorsio library, I've raised an issue there.
Also, the no-data value is not correctly considered by sensorsio.

@jmichel-otb
Copy link
Collaborator

Fixed in https://framagit.org/jmichel-otb/sensorsio/-/merge_requests/14

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants