Skip to content
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

species authorship causes GBIF accepted infraspecific taxon not being matched? #116

Open
abubelinha opened this issue Jun 19, 2024 · 0 comments

Comments

@abubelinha
Copy link

abubelinha commented Jun 19, 2024

This is the GBIF backbone accepted taxon: https://www.gbif.org/species/7423643
I am passing 11 as data source:

Thanks
@abubelinha


EDIT:
I constructed the above queries from the verifier.globalnames.org interface form textarea, and selected output=JSON
That gave the results I linked above (containing a names= parameter).
Now that I went to the api interface I am a bit confused since I don't see which form should I use how to construct the exact same output.

Instead, I see a verifications/names menu entry which seems to work better and match the name I was looking for.

https://verifier.globalnames.org/api/v1/verifications/Linaria%20polygalifolia%20Hoffmanns.%20%26%20Link%20subsp.%20aguillonensis%20%28Garc%C3%ADa%20Mart.%29%20Castrov.%20%26%20Lago?data_sources=11&all_matches=true&capitalize=false&species_group=false&fuzzy_uninomial=false&stats=false&main_taxon_threshold=0.5

Could you explain those differences?


EDIT:
gbif-api species/match issue with the same taxon name
Same problem. Just out of curiosity, do GBIF and gnames match names in a similar way?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant