My sense is that there have been previous issues with accessing tnrs, but I am not sure if there is any way to address Bad Gateway problems or if this is one of the reasons tnrs may become defunct in the future. I have been receiving somewhat unpredictable errors when using the tnrs function. Sometimes I run a query on multiple species names at once and I get a Bad Gateway error, but when I re-run on a single species it works. Other times I cannot even perform a successful query on a single species name. See code below. Thanks in advance!
R version 3.3.3 (2017-03-06)
Platform: x86_64-apple-darwin13.4.0 (64-bit)
Running under: macOS Sierra 10.12.4
iplant_resolve(query="Mimulus cardinalis var. verbenaceus")
Error: lexical error: invalid char in json text.
<!DOCTYPE HTML PUBLIC "-//IETF/
(right here) ------^
In addition: Warning message:
In iplant_resolve(query = "Mimulus cardinalis var. verbenaceus") :
Bad Gateway (HTTP 502).
plant_list_species=tnrs(query = "Mimulus cardinalis var. verbenaceus", source = "iPlant_TNRS")
Error: HTTP status 502 - Bad Gateway
The text was updated successfully, but these errors were encountered:
Thanks so much @sckott . Yes I also noticed that tnrs is working now. Too bad that they are down so often--it is a really great tool for resolving taxon names but it would be nice if it were more consistently reliable. Thanks again!
I tried other functions like gnr_resolve and am convinced that tnrs does a better job for many of my taxon names, so I would prefer irregular access to tnrs than no access at all. Of course it would be even better if the function were more reliable, as sometimes I want to re-run code and it won't work for some indefinite period of time.