-
Notifications
You must be signed in to change notification settings - Fork 75
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.
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
Suport netCDFServer name #215
Comments
There are a couple of ways to go about this. Probably the best way, from an end users point of view, would would involve making sure that this just works©™®: ncss = dataset.subset() To do so, we could add a check in the Lines 592 to 596 in 935d195
and check to see if
If both are true, then we use use |
Adds support for NetcdfServer, when available, to be used for NCSS.
See #216 for what seemed to be least horrible to me. |
Adds support for NetcdfServer, when available, to be used for NCSS.
Adds support for NetcdfServer, when available, to be used for NCSS.
Adds support for NetcdfServer, when available, to be used for NCSS.
Adds support for NetcdfServer, when available, to be used for NCSS.
When using NCEI data, they use the older name for NCSS. This makes workshop materials more complicated and requires too much knowledge of the data source for users. We thought this was in 0.7 😭
The text was updated successfully, but these errors were encountered: