Use xarray for OPeNDAP requests #752
Draft
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.
Description
This is a small change that will make the codebase more consistent. RAiDER uses several packages for interfacing with datasets in different places, and one is pydap for GMAO and MERRA2 data. This change changes pydap out for xarray, which is already used in many other places.
For GMAO, pydap is no longer used at all. For MERRA2, since it requires authentication, pydap is still used under the hood through xarray's pydap engine.
Motivation and Context
How Has This Been Tested?
All tests still pass. I realized the path for fetching GMAO data before
T0was not tested intest_downloaders, so I added a test for it.Screenshots (if appropriate):
Type of change
Checklist: