Update NWM Client New interfaces and bring up to feature parity with old client

[jarq6c]

This turned out to be a bit bigger than I had intended, but it is the result of months of experimentation as well as feedback from frequent users of National Water Model output. I'll summarize changes for each component.

FileDownloader.py

Added an overwrite boolean parameter that will warn and skip similarly named files.

NWMFileProcessor.py

Updated get_dataset to accept the xarray.open_mfdataset paths argument. Essential coordinates (reference_time, time, and feature_id) are always returned.

NWMClient.py

Updated abstract interface to accept an nwm_feature_ids parameter to facilitate retrieval of smaller amounts of data. Unfortunately, retrieving data is still relatively slow, but this new interface accommodates the most common use-case (retrieval of time series data from a few sites).

NWMFileClient.py

Added unit_system parameter to match older nwm_client unit handling. Replaced get_dataset method with get_files that just downloads files and returns their local paths. get method works with several configurations and reference_times by default. Implements nwm_feature_ids parameter.

ParquetStore.py

Formerly ParquetCache.py, I decided to rename this module and reimplement as a MutableMapping similar to pandas.HDFStore. It can still be used as a context manager, but now it also includes key-access and inherits useful methods like get and pop from MutableMapping. As a consequence, the old get method was removed. This could live somewhere else, eventually.

NWMClientDefaults.py

Added defaults for handling units, variables, and the new ParquetStore.

UnitHandler.py

Taken verbatim from the older nwm_client. This could potentially live somewhere else (eventually).

_version.py

bumped to 7.0.0 due to breaking interface changes

Checklist

• PR has an informative and human-readable title
• PR is well outlined and documented. See #12 for an example
• [?] Changes are limited to a single goal (no scope creep)
• Code can be automatically merged (no conflicts)
• Code follows project standards (see CONTRIBUTING.md)
• Passes all existing automated tests
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output) using numpy docstring formatting
• Placeholder code is flagged / future todos are captured in comments
• Reviewers requested with the Reviewers tool ➡️

[jarq6c]

Ping @aaraney

[aaraney]

@jarq6c, thanks for pinging me. Im excited to start reviewing this tomorrow!

[aaraney]

Thanks for contributing this, @jarq6c! I got about halfway through the review and I need to step away to do some other tasks. Ill be back to finish this up either this weekend or sometime next week. Have a nice weekend!

[aaraney]

@jarq6c, it looks like newer commits got rebased on top of this PR yesterday. I think you can do an interactive rebase (git rebase -i HEAD~4) on your nwm-new-units branch, drop the three new commits, and then force push to get us back to where we were before. Then, I think you need to rebase your nwn-new-units branch on top of main, resolve any conflicts, and force push again. The first force push is optional, but I think its worth it just to make sure the history lines up on GitHub.

[jarq6c]

@jarq6c, it looks like newer commits got rebased on top of this PR yesterday. I think you can do an interactive rebase (git rebase -i HEAD~4) on your nwm-new-units branch, drop the three new commits, and then force push to get us back to where we were before. Then, I think you need to rebase your nwn-new-units branch on top of main, resolve any conflicts, and force push again. The first force push is optional, but I think its worth it just to make sure the history lines up on GitHub.

Started a new PR from a new branch over on #227