New error downloading WCGBTS

[rBatt]

I was able to use download_catch_rates to get the WCGBTS data earlier this week, but today I get an error.

d <- download_catch_rates(survey="WCGBTS", add_zeros=FALSE, species_set=10)

Using that, I get:

Obtaining data for WCGBTS survey...
Downloading all WCGBTS catch-rate data for 2003 from NWFSC database: https://www.nwfsc.noaa.gov/data/
Error in open.connection(con, "rb") : HTTP error 400.

Does this mean that the server changed its API? Any ideas?

[James-Thorson]

I'm on paternity leave for 3 more weeks but feel free to email Todd hay and
cc me

On Oct 14, 2016 10:59 AM, "Ryan Batt" [email protected] wrote:

I was able to use download_catch_rates to get the WCGBTS data earlier
this week, but today I get an error.

d <- download_catch_rates(survey="WCGBTS", add_zeros=FALSE,
species_set=10)

Using that, I get:

Obtaining data for WCGBTS survey...
Downloading all WCGBTS catch-rate data for 2003 from NWFSC database:
https://www.nwfsc.noaa.gov/data/
Error in open.connection(con, "rb") : HTTP error 400.

Does this mean that the server changed its API? Any ideas?

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#2, or mute the thread
https://github.com/notifications/unsubscribe-auth/AHnqTfSd_rsa_TzzX9o3YZTle3Pq1Vlkks5qz8MNgaJpZM4KXR6S
.

[rBatt]

No problem at all! I'm working through the problem myself right now, but I figured I should post here; hope you don't mind.

It looks like they are changing the variable names in the database/ API (I'm new to these things, sorry).

In particular, it looks like the variable operation_dim$project_name that was being used in the filter= part of the query no longer exists. However, I see that they now have a project variable that seems to contain the same information and that I've used in a successful test of that filter.

@mpinsky Tagging you here so you know what's going on.

[DanOvando]

Hmmm, download_catch_rateswas working for both WCGBTS and WCGHL, stopped this week, will dig into the issue next week

Evaluation error: HTTP error 500..

so something on the server end

[DanOvando]

Hmmm seems to be working again today, mysteries