> For the complete documentation index, see [llms.txt](https://monitoring.toolkit.citiobs.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://monitoring.toolkit.citiobs.eu/readme/why-this-toolkit.md). # Why this Toolkit? *Citizen Observatories* (COs) involve citizens using modern mobile and web technologies and/or sensors to collect and share data, which enhance Earth Observation systems and official data sources by filling in gaps and adding detail. Often using dedicated IT infrastructure, COs support the flow of data and information between citizens, scientists, and decision-makers, and typically have a distinct focus on influencing decision-making, policy change, and/or environmental governance outcomes. We have seen that data collected in Citizen Science and COs initiatives are often not regarded as trustful data when it is communicated to decision makers. We have also seen that COs for environmental monitoring tend to engage with participants that feel attracted to technology, leaving behind participants that feel not at ease when it comes to the use of novel technologies. The Toolkit aims to provide guidance to avoid or reduce the technological barriers hindering the widespread adoption of sensing devices and other monitoring systems. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://monitoring.toolkit.citiobs.eu/readme/why-this-toolkit.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.