Skip to content
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

get_dataset() now fails with url timeout error #252

Open
AMBarbosa opened this issue Nov 25, 2022 · 2 comments
Open

get_dataset() now fails with url timeout error #252

AMBarbosa opened this issue Nov 25, 2022 · 2 comments

Comments

@AMBarbosa
Copy link

Hi, get_dataset() was working alright until the last time I used it (March this year), but now it's consistently failing (for the same taxa, and even for the Examples in the help file) with Error in url::curl_fetch_memory(url, handle = handle) : Timeout was reached: [wnapi.neotomadb.org] Connection timed out after 10008 milliseconds, even if I greatly increase getOption('timeout') in my R installation. Cheers

@SimonGoring
Copy link
Member

Hi @AMBarbosa thank you for reaching out. The package neotoma has now been deprecated. Unfortunately our wnapi.neotomadb.org server reached end of life and was no longer operable.

The package has been replaced by neotoma2. As much as possible we have kept many of the same patterns, but there are new data structures.

The wnapi server was only passing along data submitted before June 2020. The new package accesses all data up until the present. Please contact us directly either by email ([email protected]) or on our slack workspace (there is an it_r channel) and we can help assist you in migrating to neotoma2.

My sincere apologies.

@AMBarbosa
Copy link
Author

Thanks for the reply! I'll try 'neotoma2' the next time I need it (I was going to use it during a course, which has ended in the meantime). But I suggest adding a message about this when 'neotoma' is installed and/or loaded (like what happens e.g. when running library(maptools)). Right now, people are installing and loading the package with no idea that it has been replaced.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants