Fix AMSR-2 L1B reader loading bytes incorrectly #351
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
I think this is due to a recent change in numpy where bytes arrays are no longer considered
np.string_types. This was causing AMSR-2 L1B attributes read from the file to stay as bytes objects when they should have been strings.Additionally, AMSR-2 L1B composites were running in to the same issue that VIIRS SDR had run in a while ago where xarray doesn't like that the 'coordinates' attribute is a list and when you concatenate DataArrays that have different 'coordinates' attributes, it fails. See pydata/xarray#2060 for more details.
git diff origin/master **/*py | flake8 --diff