USEPA / elevatr

An R package for accessing elevation data
Other
204 stars 26 forks source link

get_elev_point: Error: API did not return json #32

Closed tmt2131 closed 3 years ago

tmt2131 commented 4 years ago

Hi!

Great package that's been really helpful. Quick question, I've used this package in the past with no problems. I tried running something new today and received this error message: "Error: API did not return json".

I tried running the sample code on this page (https://rdrr.io/cran/elevatr/man/get_elev_point.html) to see if it was my code and I'm getting the same error message. Are there any changes that I should be aware of? Thanks!

jhollist commented 4 years ago

Glad to hear you are finding elevatr helpful.

I just tested my example code for both get_elev_raster and get_elev_point and it is working for me.

The API you were using may have been down for a bit? Try again and if it is still not working, let me know along with the code you ran and the result of sessionInfo().

tmt2131 commented 4 years ago

Hi Jeff,

Thanks for the quick response. Thanks for offering to help. I've tried it several times since I've gotten your email without any success. My understanding is that API is external to my computer and would be on the (in this case) USGS or web side.

I used the example code here

library(elevatr)

mt_wash <- data.frame(x = -71.3036, y = 44.2700) mt_mans <- data.frame(x = -72.8145, y = 44.5438) mts <- rbind(mt_wash,mt_mans) ll_prj <- "+proj=longlat +ellps=WGS84 +datum=WGS84 +no_defs" mts_sp <- sp::SpatialPoints(sp::coordinates(mts),

Here's the print out of my sessionInfo()

R version 3.6.3 (2020-02-29) Platform: x86_64-apple-darwin15.6.0 (64-bit) Running under: macOS Catalina 10.15.5

Matrix products: default BLAS: /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib LAPACK: /Library/Frameworks/R.framework/Versions/3.6/Resources/lib/libRlapack.dylib

Random number generation:

locale: [1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8

attached base packages: [1] stats graphics grDevices utils datasets methods base

other attached packages:

loaded via a namespace (and not attached):

I also tried running all of this on my lab's server since I wasn't quite sure if I understood API correctly and received the same error message.

Thanks for your help!

Tammy

On Wed, Jul 1, 2020 at 1:36 PM Jeffrey W Hollister notifications@github.com wrote:

Glad to hear you are finding elevatr helpful.

I just tested my example code for both get_elev_raster and get_elev_point and it is working for me.

The API you were using may have been down for a bit? Try again and if it is still not working, let me know along with the code you ran and the result of sessionInfo().

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/jhollist/elevatr/issues/32#issuecomment-652554992, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEGCYMB7UIAJD4XIYGSMDZLRZNX2TANCNFSM4ONTGZHQ .

jhollist commented 4 years ago

@tmt2131 So, it appears to be a server side issue. The USGS server returns a 503 error. While I was testing it, it worked, then it didn't... On the epqs site there is a message about maintenance, so that is likely the issue. It should resolve itself at some point.

Alternatively, you can use the "aws" source with a resonably high z value.

Something like:

get_elev_point(locations = mt_wash, prj = ll_prj, src = "aws", z = 12)

should work. Depending on number of points and how close those points are, this can take some time. I think at this point, I am fairly sure this is not an elevatr issue. I'm going to close the issue, but if you continue to have problems in a few days, feel free to re-open the issue.

Thanks!

jhollist commented 4 years ago

Never mind, I am going to reopen this.

It is a server side issue because the have changed to service URL! I need to look into this some more.

If the aws source works for you, use that for now. I am not entirely sure when I will have time to get at this fix.

tmt2131 commented 4 years ago

Hi Jeffrey,

Thanks for looking into this and keeping the issue open. I tried inputting the values directly into USGS’s point inquiry website earlier today, before emailing you, and it had worked directly on the website. Thanks for communicating the issue and the problem. Unfortunately, aws source won’t work but I’ll find another solution in the meantime. Thanks again for your help!

Best, Tammy

On Wed, Jul 1, 2020 at 8:45 PM Jeffrey W Hollister notifications@github.com wrote:

Never mind, I am going to reopen this.

It is a server side issue because the have changed to service URL! I need to look into this some more.

If the aws source works for you, use that for now. I am not entirely sure when I will have time to get at this fix.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jhollist/elevatr/issues/32#issuecomment-652715254, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEGCYMHQZZO3YQX2M73GHI3RZPKD7ANCNFSM4ONTGZHQ .