Red Deer condo refresh control center.
A single public readout of the latest acquisition run: what is current, what joined to the 80-building atlas, what is stale or unknown, and what needs review before a new claim goes live.
Every refresh stage leaves a visible trail.
The report separates source freshness from join coverage. A local snapshot may remain useful while its portal metadata still needs a check.
| Stage | Status | Last run | Coverage and output |
|---|---|---|---|
| Matrix/Pillar 9 aggregate Aggregate public-safe building data is available. | Current | Jul 20, 2026 | rows: 2,962 · buildings: 80 |
| City open-data acquisition Catalog metadata and local source artifacts are tracked. | Review | Jul 20, 2026 | datasets: 17 · alerts: 2 |
| Permit enrichment 29 building clusters remain in the permit review queue. | Watch | Jul 20, 2026 | matched: 51 · total: 80 |
| Parcel and neighbourhood enrichment Official parcel geometry is the location join used by public profiles. | Current | Jul 20, 2026 | mapped: 80 · total: 80 |
| Spatial context enrichment Planning, assessment, sidewalks, transit, waste, roads, and business signals are kept as context. | Current | Jul 20, 2026 | matched: 80 · total: 80 |
| Historical Matrix snapshot Year-over-year and snapshot comparisons can be generated. | Current | Jul 20, 2026 | comparisonAvailable: yes |
| Public site build The public catalog and readiness report were generated with this build. | Current | Jul 24, 2026 | generated: yes |
How much of the building atlas has usable civic context?
Coverage is calculated against the current building-cluster denominator. Partial coverage stays visible instead of being rounded into a site-wide claim.
| Signal | Matched | Coverage | Status |
|---|---|---|---|
| Market rows with usable aggregate fields Imported Matrix/Pillar 9 rows are summarized at building level before publication. | 2,962 / 2,962 | 100% | Current |
| Building clusters with parcel and neighbourhood joins Official parcel geometry and neighbourhood labels are the location backbone. | 80 / 80 | 100% | Current |
| Building clusters matched to permit history Unmatched clusters stay in the review queue until an address convention is defensible. | 51 / 80 | 64% | Watch |
| Building clusters with property assessment context Assessment context is not current market value or a tax bill. | 79 / 80 | 99% | Review |
| Building clusters with statutory-plan context Plan overlap describes the planning frame around the parcel. | 80 / 80 | 100% | Current |
| Building clusters with sidewalk context Sidewalk attributes are infrastructure evidence, not a condition certification. | 80 / 80 | 100% | Current |
| Building clusters with nearest transit context Transit joins identify the nearest mapped stop or route context. | 80 / 80 | 100% | Current |
| Building clusters with full spatial context Spatial context combines the civic layers available in the current local snapshot. | 80 / 80 | 100% | Current |
Open gaps with a reason and a destination.
These counts are the practical next actions for the next data refresh. Zero means no item was detected in that category, not that a source is permanently complete.
| Queue | Items | Status | Next view |
|---|---|---|---|
| Source-health alerts Statutory Plans source metadata is 662 days old against a 2-day refresh expectation. Sidewalks source metadata is 662 days old against a 220-day refresh expectation. | 2 | Review | Open review |
| Unmatched permit building clusters Candidate civic addresses need alias or address-convention review before joining. | 29 | Review | Open review |
| Unmatched parcel or neighbourhood joins Address validation and official neighbourhood mapping should be rechecked on the next refresh. | 0 | Current | Open review |
| Assessment context gaps A missing assessment join is a context gap, not a market-data failure. | 1 | Review | Open review |
| GIS artifacts with audit errors Downloaded civic artifacts should be audited before their records support public claims. | 0 | Current | Open review |
| Historical comparison readiness A previous Matrix snapshot is available for change comparison. | 0 | Current | Open review |
Run the same sequence each time.
- Import the newest approved Matrix/Pillar 9 export and inspect the generated import report.
- Fetch City metadata and downloadable artifacts, then inspect source-health changes.
- Re-run parcel, permit, and spatial joins; investigate gaps before rebuilding the public pages.
- Capture a Matrix snapshot so the next refresh can explain movement instead of only reporting a level.
- Record the run so coverage regressions and source-health changes remain visible.
- Download the public-safe readiness report and catalog for downstream search, analytics, and QA.
Machine-readable outputs
The public catalog is designed for people and systems. The smaller readiness file is the fast operational handshake for QA, automations, and future ingestion.
Download refresh readiness JSONDownload refresh history JSONDownload public data catalogOpen full acquisition log