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.

Sign up for GitHub

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

Jump to bottom

atmcorr sets 0 to 'no data' when it shouldn't #24

Open
milyra opened this issue Jan 5, 2018 · 0 comments
Open

atmcorr sets 0 to 'no data' when it shouldn't #24

milyra opened this issue Jan 5, 2018 · 0 comments
Labels
bug

Comments

@milyra
Copy link
Contributor

milyra commented Jan 5, 2018

In images where the initial 'no data' value is 0, if dark waters reach 0 as a result of the atmospheric correction, the value gets set to 'no data', which then causes problems when the results from the atmcorr is sent further through the chain.
Can we possibly keep 0 and 'no data' separate? Meaning, if there were a value before, it shouldn't by accident end up as 'no data' when just using atmcorr.
@milyra milyra added the bug label Jan 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@milyra