Fix MODIS readers applying add_offset incorrectly #2142
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It was pointed out on the mailing list that when reading MODIS L2 (MOD06) cloud top temperature that the resulting values were nonsensical. This is due to us applying scale_factor/add_offset in the wrong way. We were doing:
but we should be doing:
because MODIS.
This PR fixes this issue and others. While adding checks to the tests to verify that what was happening was actually happening, I noticed that byte mask conversions were actually converting dask to numpy arrays. I've fixed this issue as well by wrapping these operations in a
da.map_blocks
call.Note: This PR does not include the test fixes in #2141 so the tests will fail until that is merged.