Data operations

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.

Publication stateReview before publishingGenerated Jul 24, 2026 · Matrix data through 2026-07-08 · 5 recorded refresh runs
17Tracked sources: City layers in the registry
15Marked current: Health evidence supports the latest check
2Source checks to review: Watch, stale, or unknown status
2Open source alerts: Shown in the acquisition queue
Pipeline status

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.

StageStatusLast runCoverage and output
Matrix/Pillar 9 aggregate
Aggregate public-safe building data is available.
CurrentJul 20, 2026rows: 2,962 · buildings: 80
City open-data acquisition
Catalog metadata and local source artifacts are tracked.
ReviewJul 20, 2026datasets: 17 · alerts: 2
Permit enrichment
29 building clusters remain in the permit review queue.
WatchJul 20, 2026matched: 51 · total: 80
Parcel and neighbourhood enrichment
Official parcel geometry is the location join used by public profiles.
CurrentJul 20, 2026mapped: 80 · total: 80
Spatial context enrichment
Planning, assessment, sidewalks, transit, waste, roads, and business signals are kept as context.
CurrentJul 20, 2026matched: 80 · total: 80
Historical Matrix snapshot
Year-over-year and snapshot comparisons can be generated.
CurrentJul 20, 2026comparisonAvailable: yes
Public site build
The public catalog and readiness report were generated with this build.
CurrentJul 24, 2026generated: yes
Join coverage

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.

SignalMatchedCoverageStatus
Market rows with usable aggregate fields
Imported Matrix/Pillar 9 rows are summarized at building level before publication.
2,962 / 2,962100%Current
Building clusters with parcel and neighbourhood joins
Official parcel geometry and neighbourhood labels are the location backbone.
80 / 80100%Current
Building clusters matched to permit history
Unmatched clusters stay in the review queue until an address convention is defensible.
51 / 8064%Watch
Building clusters with property assessment context
Assessment context is not current market value or a tax bill.
79 / 8099%Review
Building clusters with statutory-plan context
Plan overlap describes the planning frame around the parcel.
80 / 80100%Current
Building clusters with sidewalk context
Sidewalk attributes are infrastructure evidence, not a condition certification.
80 / 80100%Current
Building clusters with nearest transit context
Transit joins identify the nearest mapped stop or route context.
80 / 80100%Current
Building clusters with full spatial context
Spatial context combines the civic layers available in the current local snapshot.
80 / 80100%Current
Review queue

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.

QueueItemsStatusNext 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.
2ReviewOpen review
Unmatched permit building clusters
Candidate civic addresses need alias or address-convention review before joining.
29ReviewOpen review
Unmatched parcel or neighbourhood joins
Address validation and official neighbourhood mapping should be rechecked on the next refresh.
0CurrentOpen review
Assessment context gaps
A missing assessment join is a context gap, not a market-data failure.
1ReviewOpen review
GIS artifacts with audit errors
Downloaded civic artifacts should be audited before their records support public claims.
0CurrentOpen review
Historical comparison readiness
A previous Matrix snapshot is available for change comparison.
0CurrentOpen review
Refresh loop

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