-
Notifications
You must be signed in to change notification settings - Fork 33
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
The get_nldi_basin() function (from nhdplusTools) not working #372
Comments
This issue has been reported over here. internetofwater/nldi-services#389 Keep an eye on that for resolution. |
Hey @dblodgett-usgs -- FWIW I get the same error when using |
@rburghol and @motasem-suleiman -- we should be back in business. We had a bit of a comedy of version incompatibilities between AWS, Postgres and PostGIS that were quite confounding. Great work by @ewojtylko to chaise it down. |
@dblodgett-usgs I'm still seeing 403 request failed error with basic example from Get Started page - this code:
Returns this error for me:
|
Yeah -- The firewall issue that kicked off all this was fixed in one way but the example you reference is still not quite working. We are working on opening up the firewall to larger POST payloads and then it should be fully back. |
Ahh, I noticed this was a throttling issue yesterday, 50 segments seemed to be acceptable to the service, so I made this workaround using
|
Nice hack! That would totally work around what we are seeing. I'll update when we get this figured with the security folks. |
An exception was put in place last night. Seems that we are back in business. Tests for me work. Will leave this open till I get confirmation you all are back in action. Thanks for your patience. |
All working when I check- thanks @dblodgett-usgs ! |
I keep getting an error when I use the get_nldi_basin() function from the nhdplusTools library.
Request failed [500]. Retrying in 1.2 seconds...
Request failed [500]. Retrying in 3.8 seconds...
Warning message:
Cannot open "{"description":"Something bad happened. Contact us with Reference Number: 1255184806","type":"error"}"; Check connection parameters.
The text was updated successfully, but these errors were encountered: