As an example, we can consider the classification paths returned for 'Phleum alpinum'. When the results are filtered to include only the 7 required ranks, we get the following with matching GNR confidence scores of 0.988:
...
"classification_path": [
"Viridiplantae|Streptophyta|Magnoliopsida|Poales|Poaceae|Phleum|Phleum alpinum",
"Archaeplastida|Chloroplastida|Streptophyta|Tracheophyta|Magnoliopsida|Liliopsida|Poales|Poaceae|Phleum|Phleum alpinum",
"Plantae|Tracheophyta|Liliopsida|Poales|Poaceae|Phleum|Phleum alpinum",
"Plantae|Tracheophyta|Liliopsida|Poales|Poaceae|Phleum|Phleum alpinum",
"Plantae|Tracheophyta|Liliopsida|Poales|Poaceae|Phleum|Phleum alpinum",
"Plantae|Tracheophyta|Liliopsida|Poales|Poaceae|Phleum|Phleum alpinum",
"Plantae|Magnoliophyta|Liliopsida|Poales|Poaceae|Phleum|Phleum alpinum",
"Plantae|Tracheophyta|Liliopsida|Poales|Poaceae|Phleum|Phleum alpinum",
"Plantae|Tracheophyta|Magnoliopsida|Poales|Poaceae|Phleum|Phleum alpinum"
],
"name_string": [
"Phleum alpinum",
"Phleum alpinum",
"Phleum alpinum",
"Phleum alpinum L.",
"Phleum alpinum prol. commutatum (Gaudin) Rouy",
"Phleum alpinum prol. parviceps (Briq.) Rouy",
"Phleum alpinum Linnaeus",
"Phleum alpinum L.",
"Phleum alpinum L."
],
"classification_path_ranks": [
"kingdom|phylum|class|order|family|genus|species",
"kingdom|kingdom|phylum|phylum|class|class|order|family|genus|species",
"kingdom|phylum|class|order|family|genus|species",
"kingdom|phylum|class|order|family|genus|species",
"kingdom|phylum|class|order|family|genus|species",
"kingdom|phylum|class|order|family|genus|species",
"kingdom|phylum|class|order|family|genus|species",
"kingdom|phylum|class|order|family|genus|species",
"kingdom|phylum|class|order|family|genus|species"
],
"sources": [
"National Center for Biotechnology Information",
"Open Tree of Life Reference Taxonomy",
"iNaturalist Taxonomy",
"Catalogue of Life Checklist",
"Catalogue of Life Checklist",
"Catalogue of Life Checklist",
"The Interim Register of Marine and Nonmarine Genera",
"GBIF Backbone Taxonomy",
"EUNIS"
],
...
The problems illustrated in this case include:
- A source returns multiple terms for a given rank, e.g. OTOL's Kingdom, Phylum, and Class ranks. It's not clear how the 'correct' term should be chosen.
- A simple vote for the most frequently occurring
classification_path result is problematic because:
- A single source can appear more than once, e.g. here the Catalogue of Life Checklist appears 3 times, reporting several synonyms as shown in the
name_string field. Whether a term here is a synonym or not isn't available in the output of a GNR query.
- The sources are interdependent.
- Results at a given rank (even when not considering OTOL) are discrepant, e.g.
"kingdom": ["Plantae", "Viridiplantae"], "phylum": ["Tracheophyta", "Magnoliophyta", "Streptophyta"], "class": ["Magnoliopsida", "Liliopsida", "Magnoliopsida"].
The full response for this example can be explored by visiting: http://resolver.globalnames.org/name_resolvers.json?names=Phleum+alpinum&with_vernaculars=true&wigh_context=false&with_canonical_ranks=true
As an example, we can consider the classification paths returned for 'Phleum alpinum'. When the results are filtered to include only the 7 required ranks, we get the following with matching GNR confidence scores of 0.988:
The problems illustrated in this case include:
classification_pathresult is problematic because:name_stringfield. Whether a term here is a synonym or not isn't available in the output of a GNR query."kingdom": ["Plantae", "Viridiplantae"],"phylum": ["Tracheophyta", "Magnoliophyta", "Streptophyta"],"class": ["Magnoliopsida", "Liliopsida", "Magnoliopsida"].The full response for this example can be explored by visiting: http://resolver.globalnames.org/name_resolvers.json?names=Phleum+alpinum&with_vernaculars=true&wigh_context=false&with_canonical_ranks=true