-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
suggest to support matching names against IUCN #94
Comments
IUCN backbone integration came up again in today's GBatNet meeting - fyi @arw36 @JelleZijlstra @n8upham @ajacsherman @kephelps @myrmoteras |
I'll what I did to get the 2024-1 IUCN taxonomy into Hesperomys. It's not great, and it's up to you whether something like this would be a fit for what you want to do.
This gave me two CSVs, I think one is supposed to represent the taxonomy and the other the assessments of individual species. I used that CSV to import the classification into my database at https://hesperomys.com/ce/84965; I also used this to create some spreadsheets I shared with Aja. Regarding versioning, there is a version number (currently 2024-1, 2024-2 scheduled for late October). Somebody at the meeting today (I think Anna) said that the versioning applies to the spatial data. I sort of trust it also applies to the taxonomy, but that's difficult to verify; I hope they don't continuously make changes without telling us. |
@JelleZijlstra thanks for sharing your notes. I was able to repeat the steps you described to download a copy of the taxonomic backbone. I am baffled by why IUCN is making it so hard to re-use their taxonomic backbone. I understand that range maps may be sensitive, but taxonomic names without any associated data like range maps and/or IUCN status . . . I wonder what their reasoning is. |
as proposed by @ajacsherman
please provide example
The text was updated successfully, but these errors were encountered: