Closed matthewross07 closed 5 years ago
I've recently had trouble when there are sites in the call that have a weird character in the monitoring ID, which trips up the call and gives be a 404 error. Maybe look at the site names in Montana, and see if they have weird characters? -- see some documentation here and here. One potential reason it worked in the past but not now is that a new site was added.
Yeah, it's failing because the siteInfo attribute is getting too big...which comes from a call to whatWQPsites
. I've been meaning to do 2 things:
In the nearterm @matthewross07 ...if you can use the site types to limit your search, that's one option. I can get you another option after a couple of meetings this morning....
OK, I think I've fixed it...you can install like this:
remotes::install_github("USGS-R/dataRetrieval")
packageVersion("dataRetrieval")
[1] ‘2.7.5.9000’
I'm going to close this issue and open another one because I really want to add an argument that allows the user to turn off those attribute calls (and the POST issue is already an issue)
Y'all are great and much appreciated!
Random states failing to download WQP data
Hi! First I love this package and am grateful for your maintenance. I have been working with WQP for a few years now with the only occasional 404 error on a
readWQPdata
. However, now some code that used to always work is failing in ways that I don't understand. A reprex (hopefully!) is below:The main issue
The oddest part of this is that it is consistently giving this kind of error for Colorado and Montana across a variety of characteristic names (like Copper, Cadmium, etc...). It works fine for other states (like West Virginia, Indiana, Ohio, etc...)
Things I have checked:
siteType
does seem to fix the issue since both code chunks run below just fine:My question(s)
readWQPdata
site info? I've done this before, but then WQP started to think I was spamming them because of sending up such long strings.I appreciate any advice.