> For the complete documentation index, see [llms.txt](https://docs.getdor.com/dtm-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.getdor.com/dtm-docs/dtm-api/data-validity/completeness.md).

# Completeness

The `completeness` key indicates whether additional data is expected for the given interval or if all data has been received. Data is marked `incomplete` if the interval hasn't closed yet or if any sensors have yet to send their data after the close of the interval.

For example, if hourly data is queried at 12:10 pm for the 12:00 - 1:00 pm hour the data will be `incomplete` because the interval includes the current time and therefore hasn't closed yet. Similarly, if the same 12:00 - 1:00 pm hour is queried at 1:05 pm, it will still be `incomplete` until all sensors have sent data after the close of the interval at 1:00 pm. Once all sensors have purged their data, the interval will be updated to `complete`.

#### Completeness Definitions <a href="#completeness-definitions" id="completeness-definitions"></a>

| Value          | Description                                                                                                                                                                                          |
| -------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **complete**   | The interval has closed and all sensors associated to the location have purged their data for the interval.                                                                                          |
| **incomplete** | One or more sensors associated with the location have not fully purged their data to the server for the interval. Metrics for this interval will likely be updated by NextQuick Start in the future. |