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

Baseline 4.0 Offset Issue #9

Open
julianblue opened this issue Jul 25, 2023 · 3 comments
Open

Baseline 4.0 Offset Issue #9

julianblue opened this issue Jul 25, 2023 · 3 comments
Labels
check-after-reprocessing Issues that we should re-check after the s2 reprocessing

Comments

@julianblue
Copy link

@matthewhanson ,

is there an update on this https://github.com/cirrus-geo/cirrus-earth-search/issues/26 ?

I am facing issues when processing sentinel data as there are cases when the scale supposedly was not applied (according to metadata) but actually seems to have been applied. --> causing negative values in some instances

@matthewhanson
Copy link
Member

@julianblue are you looking at the earthsearch:boa_offset_applied property? Or at the raster:bands.offset property? It looks like the offset property may be incorrectly set to -0.1 even when it has been applied but I think the boa_offset_applied is the truth.

This has been fixed in our new pipeline which we will be switching to soon for new scenes and will be processing the new ESA produced scenes as they are made available.

@gcaria
Copy link

gcaria commented Oct 4, 2023

When reading the TIFs directly from the S3 bucket, is there a way to know whether the offset has been applied?

e.g. reading the data with rioxarray, would it be possible to rely on the add_offset attribute (see example below)?

Screen Shot 2023-10-04 at 4 05 13 pm

@jkeifer
Copy link
Member

jkeifer commented Nov 22, 2023

@gcaria Unfortunately, the current COG files do not have the scale/offset written to them, so this is an unreliable indicator. This has also been fixed in the new pipeline.

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

5 participants