You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For each database we normalized species names against the GBIF Taxonomic Backbone, using the GBIF Species Lookup Tool (GBIF 2018c) and the GBIF Species API v1 (GBIF 2018b). A 96.0% match was found between GBIF Taxonomic Backbone and WEP, and a 93.3% match was found between the Backbone and the GENESYS and the Global Crop Wild Relative Occurrence Database.
We should explore ways to fix taxonomy so that matches are as close to 100% as possible. TNRS?
The text was updated successfully, but these errors were encountered:
Sure, but please take in count we'll never reach the 100% since not everything in the taxonomy field can be verifiable as a valid taxonomy or even a word that looks like a taxonomy.
Here there are some highlight of the unmatched taxonomy:
Also, in the unmatched count I'm putting the matches that wasn't on species level (or lower), so the records document only to genus (or higher) level are counted there.
personal note: Maybe I should clarify that for the paper.
personal note: Also, I should try to query the API twice when we are queering a hybrids, since they may be starting the specific epithet sometimes with 'x' or with the '×' sign
For each database we normalized species names against the GBIF Taxonomic Backbone, using the GBIF Species Lookup Tool (GBIF 2018c) and the GBIF Species API v1 (GBIF 2018b). A 96.0% match was found between GBIF Taxonomic Backbone and WEP, and a 93.3% match was found between the Backbone and the GENESYS and the Global Crop Wild Relative Occurrence Database.
We should explore ways to fix taxonomy so that matches are as close to 100% as possible. TNRS?
The text was updated successfully, but these errors were encountered: