Coverage QA (was "Data Quality Dashboard")
API configuration status, per-source coverage %, and place-CHAS apportionment audit. The 5-layer QA status and place-coverage panels below are also summarized in the Data Trust Center's QA Coverage tab; use this page for the full source inventory and maintainer tools (API keys, pipeline log).
Data Quality Layers — see CONTRIBUTING.md
What data is missing or estimated? Each automated check below (schema, sentinel, bounds, freshness, plausibility) runs daily and reports pass/fail — a failing layer means a dataset needs a maintainer's attention, not that the whole site is broken.
Status: loading…
Place-Level Data Coverage — TIGER 2024 spatial join
The dashboard mixes two CHAS methodologies depending on the place: tract-aggregated (TIGER 2024 spatial join — accurate for cross-county jurisdictions like Erie, Aurora, Longmont) and primary-county fallback (used when the place isn’t in TIGER coverage). This panel shows the buckets explicitly so the methodological provenance is auditable.
API Configuration — maintainer setup, not needed to use the site
API Key Setup — maintainer setup, not needed to use the site
Keys entered here are saved to your browser's localStorage and loaded automatically on each visit. They are never sent to any server. For CI/CD, add them as GitHub Secrets.
Data Source Health
Where our data comes from, and how fresh it is right now — every row below is a dataset that feeds into the site's tools.
| Source | Local File | Last Refreshed | Notes |
|---|