traitdataform
traitdataform copied to clipboard
A package to manage and compile functional trait data into predefined templates
Loving get_gbif_taxonomy so far. I just ran it on a list my colleagues maintain of about 20,000 "valid" names of hymenopteran species. About 16 came back with the warning "...
to produce - human readable txt or md file, containing a header, trait definitions (if available), license statement, and dedicated space for manual additions. - metadata.xml or .eml
The output created by the standardize functions is parsimonious, i.e. contains only the columns that have been explicitly provided. A template argument should provide the terms and order of terms...
Hi, Ive encountered an issue with the get_gbif_taxonomy breaking when trying to resolve a synonymous genus. See below example: `traitdataform::get_gbif_taxonomy("Epiptera septentrionalis",subspecies = FALSE, verbose=TRUE, higherrank=FALSE, fuzzy=TRUE ,resolve_synonyms = TRUE )`...
if GBIF matching does not return a match, apply other nameservers. Example: get_gbif_taxonomy("Carabus arvensis")
In some cases (see "Leptotyphlops conjunctus"), the first result from `get_gbifid_` is a "HIGHERRANK" match, even when there are also exact matches. Currently the function doesn't filter out this match,...
the function `standardize.traits()` is supposed to map factor levels provided into harmonized factor levels. For this, a more advanced mapping structure might be required in parameter `traitmap`.
feeding in a data table to link to measurementID or occurenceID or locationID (for georeferencing exploratories data).
Hello :-) The DOI foundation recommends [this new resolver](https://www.doi.org/doi_handbook/3_Resolution.html#3.8). It may be a bit ironic that they would change the URL of their service, but it's now [encrypted](https://www.ssllabs.com/ssltest/analyze.html?d=doi.org). Because the...