Edits to status Rmd page #735
Conversation
|
|
||
| When the NWIS services are decommissioned (possible September 2024): there will no longer be any "qw" information provided in the output of `whatNWISdata`. Discrete water-quality availability will be available via WQP services. More information will be provided as we learn more. | ||
| When the NWIS services are decommissioned (likely in 2025): there will no longer be any "qw" information provided in the output of `whatNWISdata`. Discrete water-quality availability will be available via WQP services. More information will be provided as we learn more. |
There was a problem hiding this comment.
Actually, I think this is incorrect. I'm wondering if whatNWISdata still returns older qw data, or if the service HAS been decommissioned.
There was a problem hiding this comment.
I was just looking at this. It's still showing qw data, but I'll try to get clarification on what will happen when the NWIS qw service actually gets decommissioned
There was a problem hiding this comment.
qwdata isn't slated for decommission until end of Q1, so it should still be working. Another tact for this warning is to just say that the 'qw' information has not been updated since March 2024 and will soon become deprecated: we recommend users obtain water quality data availability from the WQP services instead. Or something
There was a problem hiding this comment.
Right, but will there be any qw info from the site inventory after Q1, or will there always be the stale info?
There was a problem hiding this comment.
if that info is being pulled from an rdb then yes, that info will no longer be available. IoW will not support a public endpoint for data in the qwdata DB indefinitely, at some point it will be decommissioned.
There was a problem hiding this comment.
That info is coming from the site service (which is waterservices, not waterdata) - but it is RDB. So something like:
I'm guessing (and hoping!) that the qw data just goes away because it would be much more confusing to be wrong/outdated. But I'm still not clear if we know that anwer.
There was a problem hiding this comment.
Yes, the data should stop flowing when qwdata is decommissioned.
ehinman
had a problem deploying
to
github-pages
GitHub Actions
Failure
vignettes/Status.Rmd
Outdated
| @@ -73,7 +73,7 @@ knitr::kable(df) | |||
|
|
|||
| This function is generally advertised as a user-friendly function since it only works with a known list of sites, parameter codes or characterisitic names, and start/end dates. | |||
There was a problem hiding this comment.
I don't see where 'this function' is defined, assuming it is readWQPqw()?
There was a problem hiding this comment.
It's under the header ## readWQPqw (on line 72). We can change it though to:
The readWQPqw function is generally advertised...
vignettes/Status.Rmd
Outdated
| @@ -97,11 +97,11 @@ attr(rawPcode_legacy, "url") | |||
|
|
|||
| ## readWQPdata | |||
|
|
|||
| The "readWQPdata" function is the most flexible function to get WQP data. Currently there are 4 options that use the new WQX 3.0 profiles, and 11 legacy options. | |||
| The `readWQPdata()` function is the most flexible function to get WQP data. Currently there are 11 legacy options and 4 options that use the new WQX 3.0 profiles. Note that `readWQPdata()` does not leverage a `legacy` argument to specify which profile version the user would like returned, but instead relies on the user's specification of `service` and `dataProfile` arguments. | |||
There was a problem hiding this comment.
Correction: there are 5 WQX3 profiles
This PR updates the status page to include information about the retirement of
readNWISqw()and the WQP functions default to WQX version 2.