-
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
Latest dataset issue #118
Latest dataset issue #118
Conversation
This will be a good fix to get in the next release, as the GOES-16 datasets will likely be on thredds-jumbo, which siphon cannot talk to without this fix. |
@dopplershift - no pytest? I'm guessing you ran into this at some point with MetPy? |
The build I just checked looks like a more serious protobuf problem....I can dig in more later. |
This will need to be rebased on master after #119 is merged, which should fix our test problems. |
Alright, you should be good for a rebase now. |
In TDS 4.6, the latest service had a `name` of `Latest` and a `serviceType` of `Resolver`, at least on Unidata servers. In 5.0, the name has changed to simply `Resolver`, as part of the new Standard Service feature. The name was always configurable by the server admin, so there is no need to explicitly check the `service` elements `name` attribute.
Invalid values for THREDDS Catalog Metadata are not all that importiant for the end users to see. This commit sets the log level to ERROR instead of WARNING.
🤘 |
In TDS 4.6, the latest service had a
name
ofLatest
and aserviceType
ofResolver
, at least on Unidata servers. In 5.0, the name has changed to simplyResolver
, as part of the new Standard Service feature. The name was always configurable by the server admin, so there is no need to explicitly check theservice
elementsname
attribute.Also in this PR is change to make invalid values for THREDDS Catalog Metadata less noisy, as they are not all that importiant for the end users to see. This second commit sets the log level to ERROR instead of WARNING.