> For the complete documentation index, see [llms.txt](https://aquapurge-project.gitbook.io/aqpp-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aquapurge-project.gitbook.io/aqpp-whitepaper/data-collection.md). # Data Collection Aquapurge is more than a cleanup initiative; it's a data-driven movement. Through the active participation of our community, we gather valuable insights about ocean pollution. This includes data on the types of pollutants, their distribution across various locations, and patterns of accumulation. By harnessing this data, we gain a comprehensive understanding of the scope and severity of the issue. **Use Cases:** The data collected by Aquapurge serves as a powerful tool for informed decision-making. It enables us, directly, to: * Identify pollution hotspots * Prioritize cleanup efforts * Tailor our initiatives to have the greatest impact Moreover, this data becomes a valuable resource for external stakeholders, as it can be used to: * Research and Awareness * Policies and Decision Making * Amplified Efforts by NGOs **Targeted Beneficiaries** * NGOs * Governments * Educational & Research Facilities * Blue Economy Stakeholders --- # 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://aquapurge-project.gitbook.io/aqpp-whitepaper/data-collection.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.