> 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/project-description/implementation-plan/indicator-species-observations.md).
# Indicator species observations
Data generated from a indicator species project used in crediting
Indicator species observations require raw data (audio recording, video, or photo) date-time stamp, and geocode in decimal degrees format.
For rare, threatened, trafficked, or endangered indicator species projects are encouraged to mask geocodes for public PMPs through free sites like [iNaturalist ](https://www.inaturalist.org/signup?return_to=https://www.inaturalist.org/aboput)or [Earthranger](https://www.earthranger.com/), and arrange private review by crediting bodies.
#### **Figure 6. Indicator species observations with geocode and date-time stamp**
Figure 6b. Indicator species observations with geocode and date-time stamp. Note: geocodes have been hidden.
It should be noted that automated data such as satellite telemetry for game cameras is prohibitively expensive for most IP and LC projects. Therefore, the vast majority of projects will require trusted human coders to add geocode and date-time stamp metadata to observations. However, this does not fundamentally differ from the requirements for carbon studies in quantifying carbon load and is controlled for by independent IEP analysis of project data and IEP site visits.
---
# 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/project-description/implementation-plan/indicator-species-observations.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.
