> For the complete documentation index, see [llms.txt](https://docs.airqo.net/airqo-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.airqo.net/airqo-docs/calibration-guide.md). # Calibration Guide ## Overview Low-cost air quality monitors are relied on to increase the geographical coverage of air quality monitoring networks, especially in low-resource settings where access to reference grade monitors is limited. However, low-cost sensors require field calibration to improve their performance. In this document, we provide users with a guide on how to calibrate low-cost sensors based on the AirQo experience and help the reader appreciate the various factors involved in field calibration. We also introduce AirQalibrate, a tool that enables users without access to reference grade monitors or technical expertise to develop a calibration model to calibrate data (PM2.5 and PM10) from their low-cost monitors. ## The need for calibration Low-cost air quality sensors are sensitive to ambient conditions such as humidity and temperature which can affect the quality of data from these sensors. Field calibration provides a means to correct this data thereby improving data quality and reliability. ## Support services If you need additional support, send us an email at --- # 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://docs.airqo.net/airqo-docs/calibration-guide.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.