Closed kcmaguire closed 8 years ago
This problem seems to have been a problem with the print
method (in part) rather than the get_geochron
. That's why the fix (commenting out the class
call) worked to resolve the problem (in part), because it over-rode the print command.
The API for geochron
does not actually provide the dataset information which is requested when we use the print.geochronologic
method.
To fix this I've made some changes to get_geochron
in commit https://github.com/ropensci/neotoma/commit/db4e983b176df354a8251e8e477557c0f54e09e7. This should resolve the problems.
I get the following error when using the get_geochron function:
Here is a second example:
To overcome this, I modified the function as so: