dataRetrieval issueshttps://code.usgs.gov/water/dataRetrieval/-/issues2024-03-22T18:48:39Zhttps://code.usgs.gov/water/dataRetrieval/-/issues/435update status page for Codes service2024-03-22T18:48:39ZStanish, Leeupdate status page for Codes serviceThe WQX3.0 format will affect the mapping of USGS pcodes to Characteristics and other metadata used by the dataRetrieval function, pcode_to_name, which uses the WQP Codes service (https://www.waterqualitydata.us/Codes/public_srsnames). E...The WQX3.0 format will affect the mapping of USGS pcodes to Characteristics and other metadata used by the dataRetrieval function, pcode_to_name, which uses the WQP Codes service (https://www.waterqualitydata.us/Codes/public_srsnames). Expect to see these differences in the WQP services in April when new profiles are released. The codes service, however probably won't be updated until May. We will want to update the Status page to notify users of this discrepancy.https://code.usgs.gov/water/dataRetrieval/-/issues/434codes service is changing2024-03-22T18:44:56ZStanish, Leecodes service is changingat least one dataRetrieval function, pcode_to_name, is going to be affected by upcoming changes to the WQP Codes service (https://www.waterqualitydata.us/Codes/public_srsnames). The dev team probably won't update the service until May, a...at least one dataRetrieval function, pcode_to_name, is going to be affected by upcoming changes to the WQP Codes service (https://www.waterqualitydata.us/Codes/public_srsnames). The dev team probably won't update the service until May, after which point we'll need to evaluate impacts to this function. I'm guessing the URL will change at a minimum.
Right now this is a static list that appears to be saved locally, would it be better for this to be an actual service? We can make that request.https://code.usgs.gov/water/dataRetrieval/-/issues/427switch default WQP services profile2024-03-14T20:31:48ZStanish, Leeswitch default WQP services profileTo be done ~2 months after WQX 3.0 release. Update the WQP services functions to default to the fullPhysChem profile. To ease uses into the change, we might want to add a notification when a user calls the function stating something lik...To be done ~2 months after WQX 3.0 release. Update the WQP services functions to default to the fullPhysChem profile. To ease uses into the change, we might want to add a notification when a user calls the function stating something like: 'retrieving with the default profile (fullPhysChem)'.
We will want to provide some communication around this change as well.add WQX 3.0 profileshttps://code.usgs.gov/water/dataRetrieval/-/issues/433add sorting by date to WQP services functions2024-02-09T21:44:22ZStanish, Leeadd sorting by date to WQP services functionsthis is a highly requested option by users and something that the services isn't optimized to do (even though it is an option, it would cause queries to go REALLY SLOWLY).this is a highly requested option by users and something that the services isn't optimized to do (even though it is an option, it would cause queries to go REALLY SLOWLY).add WQX 3.0 profileshttps://code.usgs.gov/water/dataRetrieval/-/issues/432determine what field names will look like2023-11-14T20:07:55ZStanish, Leedetermine what field names will look likeOptions:
1. Taken directly from the WQP services without being modified
2. Make them look like 2.0 names
3. Change separator?
4. Something else?
5. Do users want/need a helper function to modify the names?Options:
1. Taken directly from the WQP services without being modified
2. Make them look like 2.0 names
3. Change separator?
4. Something else?
5. Do users want/need a helper function to modify the names?add WQX 3.0 profileshttps://code.usgs.gov/water/dataRetrieval/-/issues/426Communicate change of default WQP services profile2023-11-14T19:39:10ZStanish, LeeCommunicate change of default WQP services profileOver time we want to move away from the legacy default profile that has existed > 10 years, but don’t want to break workflows on day 1.
New default to be basic phys chem, but legacy profile will continue to be served for a while. Eventua...Over time we want to move away from the legacy default profile that has existed > 10 years, but don’t want to break workflows on day 1.
New default to be basic phys chem, but legacy profile will continue to be served for a while. Eventually the legacy profile will stop being used.
We want to give users time to prepare for the change. The first task therefore is to start communicating about the update in the functions themselves, in GitHub documentation, possibly elsewhere?add WQX 3.0 profileshttps://code.usgs.gov/water/dataRetrieval/-/issues/431plan for eventual NWIS qw decommission2023-11-13T19:37:30ZStanish, Leeplan for eventual NWIS qw decommissionAt some point the pcode searchability will stop being useful for NWIS qw. How far out will this be, and is it worth planning for now?At some point the pcode searchability will stop being useful for NWIS qw. How far out will this be, and is it worth planning for now?add WQX 3.0 profileshttps://code.usgs.gov/water/dataRetrieval/-/issues/429update documentation for new WQX profiles2023-11-13T15:12:46ZStanish, Leeupdate documentation for new WQX profilesSome key points to mention:
* CharacteristicNameUserSupplied is going to be an important mapping field for USGS data for at least some time
* reference the WQP Profiles blog post and the 'What is WQX?' blog post
* Mention the new defaul...Some key points to mention:
* CharacteristicNameUserSupplied is going to be an important mapping field for USGS data for at least some time
* reference the WQP Profiles blog post and the 'What is WQX?' blog post
* Mention the new default profile for WQP service callsadd WQX 3.0 profileshttps://code.usgs.gov/water/dataRetrieval/-/issues/428Enable joining of all profiles into a single table2023-11-13T15:05:47ZStanish, LeeEnable joining of all profiles into a single tableWe want DR to enable joining of all profiles into a single table. Need to determine what fields are required to joinWe want DR to enable joining of all profiles into a single table. Need to determine what fields are required to joinadd WQX 3.0 profiles