SpatialIQ Operator Dashboard
Checking…Sign in
travel_exploreNationalnational
SpatialIQ intelligence lane. Imagery → estimation → calibration → validation. Modelled figures are planning estimates with a stated range and confidence — never enumerated counts. Field-enumerated values are authoritative and shown separately. All figures are simulated demo data, not official NPC census figures.

Self-Census self-report lane The bridge from the citizen app

This is where the two products meet. Citizens self-register in the Self-Census app; an enumerator validates each household through the audited boundary (a minimised, PII-free work list — no names, no NIN); the validated record then joins SpatialIQ as an area-level lane — never per-person, and never overwriting field data.

1Citizen self-registersSelf-Census app · NIN-anchored · private QR receipt
2Enumerator validatesaudited boundary · consent-gated GPS · field decision
3Joins SpatialIQvalidated area-level lane · kept separate below
Self-Census submissions unavailable.

What needs attention today Priorities

All clear — no critical alerts, no pending decisions.

Population insights Estimation

Field-validated EA coverage
verified 0 enumerated0 modelled model_training
No estimation in scope.

Building intelligence Classification

Building intelligence unavailable.

Field anomaly flags Discrepancy

Field-capture quality flags (missing structures, possible duplicates, out-of-boundary) — FR-VAL-020. Distinct from the calibration discrepancies (model-vs-truth, FR-VAL-010). Self-Census self-report discrepancies live in the Field Enumerator App lane, not here.

No anomaly flags available.

Built-form profile Classification

The mix of building forms — an area-level socio-economic signal. Each bar is a share of classified structures, not people. Classify buildings, count areas.

No classified structures in scope yet.

Model calibration — validation against ground truth Validation

Calibration unavailable in scope.

Field-inaccessible areas (0) capture-gap EAs · estimate-only

0 EAs are genuinely field-inaccessible (security / riverine / hard-to-reach). The rest are capture-gap (buildings detected, roster not yet captured). Both carry a modelled range with confidence and method — no field count, no implied validation.

No estimable capture-gap EAs in scope.