> For the complete documentation index, see [llms.txt](https://isbm.savimbo.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://isbm.savimbo.com/appendices/appendix-d-species-categorization-of-richness.md). # Appendix D: Species categorization of richness Sample categorization of species richness for pilot site in Villagarzón, Colombia Many of the most biodiverse regions in the planet have incomplete, or inaccurate data. Following is a sample table to show species richness, and biodiversity risk for a sample BCP in the Putumayan Amazon. It is incomplete. While the table is simple, the data itself, and data sources are characteristically underdeveloped. Some easy-to-use public data sources for gathering this data include (but are definitely not limited to): * [iNaturalist](https://www.inaturalist.org/observations?place_id=7196\&verifiable=any\&view=species) * [Global Biodiversity Information Facility (GBIF)](https://www.gbif.org/country/CO/about) * [eBird](https://ebird.org/region/CO?yr=all) Of note, traditional medicine doctors “taitas” in the region describe a medicinal plant formulary of nearly 3,000 vascular plants, nearly double the characterized vascular plants in Western science for the region. #### **Table 10. Species richness and biodiversity risk in Colombia**
Taxonomy# Species# Endemic# ThreatenedZone
All species75,9478,80312,594Colombia
Trees2197280106Putumayo
Vascular plants1223346121Putumayo
Amphibians183811Wetlands, Putumayo/Caquetá/Amazonas
Reptiles371914Amazon rainforest
Birds59823141Wetlands, Putumayo/Caquetá/Amazonas
Insects190126Wetlands, Putumayo/Caquetá/Amazonas
Mammals154*19Putumayo
Fish46**Wetlands, Putumayo/Caquetá/Amazonas
Fungi95**Wetlands, Putumayo/Caquetá/Amazonas
\* No data available, \*\* Estimations only --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://isbm.savimbo.com/appendices/appendix-d-species-categorization-of-richness.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.