-
New resources & options aren't in the API documentation. @spatialit is the documentation auto-generated, or does it need to be manually updated?
-
There are two issues related to the UI when processing big responses:
1. Showing download/server process. Since the Neotoma folks enabled compression, most of the time is actually spent on the ser…
-
Occurs when object of type `site` is passed to the function:
```r
> "Beef*" %>%
+ neotoma::get_site() %>%
+ neotoma::get_dataset(datasettype = "pollen")
The API call was successful, you hav…
-
Some of the response properties or values that might be returned using get_dataset seem to be missing. For example, `MP
-
-
Especially with Neotoma data, it is possible to return a large number of `occurrence` results from a few sites.
This would also be applicable for trying to estimate sampling effort, e.g., show me all…
-
Sites recently uploaded by PI: Oswald, W. Wyatt are not populating chronology tables despite each site having multiple radiocarbon dates. Datasets effected are 40791 ,40793, 40797 ,40799, 40803, 40844…
-
Should we try to cross-link to neotomadb.org to be able to pull in paleoecological data for cal/val of longer runs? Should we include NEOTOMA site names in the BETYdb site names, similar to the way we…
-
@fils
### Expected Behavior
Returns all metadata associated with URL/ID returned from search calls.
### Actual Behavior
Returns only a small amount of data
### Steps to reproduce this beh…
-
We collect a lot of metadata for collection units and datasets, which are often critical for understanding the datasets, but which are not exposed through Neotoma explorer. Currently, the only way to …