> For the complete documentation index, see [llms.txt](https://knowledge.aterio.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.aterio.io/data-products/new-industrial-developments/our-modeling-approach/data-quality.md).

# Data Quality

Aterio applies a structured validation process to ensure that all project information such as facility type, construction status, developer details, and location is accurate and consistent with verified public records. Each data point is cross-checked using multiple sources, including corporate filings, press releases, permitting databases, infrastructure filings, and satellite imagery.

When no figures are provided, only observable or verifiable information is included in the dataset. Our analysts reconcile project counts and footprints using a combination of regulatory data, developer updates, and visible construction evidence. Each facility is validated individually to ensure that the dataset reflects real, verifiable industrial activity rather than speculative or duplicate announcements.

<br>


---

# 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://knowledge.aterio.io/data-products/new-industrial-developments/our-modeling-approach/data-quality.md?ask=<question>&goal=<endgoal>
```

`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.