gnames / gnverifier

GNverifier verifies scientific names against more than 100 biodiversity databases
https://verifier.globalnames.org
MIT License
19 stars 1 forks source link

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

Open abubelinha opened 3 months ago

abubelinha commented 3 months ago

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?