Actions22
- Collection Actions
- Dataset Actions
- Dataset Search Actions
- Installation Actions
- Institution Actions
- Occurrence Actions
- Occurrence Count Actions
- Occurrence Search Actions
- Occurrence Search Catalog Number Actions
- Occurrence Search Collection Code Actions
- Occurrence Search Occurrence ID Actions
- Occurrence Search Recorded By Actions
- Occurrence Search Record Number Actions
- Occurrence Search Institution Code Actions
- Organization Actions
- Name Parser Actions
- Network Actions
- Node Actions
- Species Actions
- Species Match Actions
- Species Search Actions
- Species Suggest Actions
Name Parser → Get
AI-generatedOverview
This node integrates with the Global Biodiversity Information Facility (GBIF) API to provide access to biodiversity data. Specifically, the Name Parser - Get operation allows users to parse a scientific name string into its taxonomic components using GBIF's name parser service.
This is useful in scenarios where you have raw scientific names and want to extract structured taxonomic information such as genus, species, authorship, and other parsed details. For example, researchers or biodiversity data managers can use this node to clean and standardize species names before further analysis or integration.
Properties
| Name | Meaning |
|---|---|
| Scientific Name | The scientific name string to be parsed by the GBIF name parser service. |
Output
The output is a JSON object containing the parsed components of the provided scientific name. This typically includes fields such as:
- Parsed genus, species, subspecies, authorship, and other taxonomic ranks.
- Normalized or canonical forms of the name.
- Flags or notes about parsing confidence or issues.
The exact structure follows the response format of the GBIF /parser/name endpoint, which returns detailed taxonomic parsing results.
No binary data is produced by this node.
Dependencies
- Requires internet access to call the public GBIF API at
https://api.gbif.org/v1/parser/name. - No authentication or API key is required for this specific operation.
- Uses HTTP GET requests with JSON responses.
Troubleshooting
- Empty or invalid scientific name input: The node expects a valid scientific name string. Providing an empty string or malformed name may result in an error or empty parsing results.
- Network connectivity issues: Since the node calls an external API, network problems will cause request failures.
- API changes or downtime: If GBIF changes their API or it becomes temporarily unavailable, the node will fail to retrieve data.
- Unexpected response format: If the API response format changes, the node might not parse the output correctly.
To resolve errors:
- Ensure the "Scientific Name" property is correctly set.
- Verify network connectivity.
- Check GBIF API status if persistent errors occur.
Links and References
- GBIF Name Parser API documentation: https://www.gbif.org/developer/summary#name-parser
- GBIF main website: https://www.gbif.org/
- GBIF API reference: https://www.gbif.org/developer/occurrence-api
This summary focuses on the Name Parser - Get operation of the GBIF node as requested.