VIEW THIS AS

Auto mode follows the Route Engine until you choose a viewpoint.

YOU ARE HERE

ROUTE CHECK

CONNECTED TO

WHAT NEXT

Use the canonical route for this room, or HELP if you are unsure.

The Gold Standard Of Urban Sensor Data Service Continuity

Three students work together at a classroom table, reviewing open textbooks and notes.

A sensor can work while its data service fails

An environmental monitoring network continues collecting readings, but its public dashboard and data API become unavailable. The gold standard separates the ability to observe conditions from the ability to deliver trustworthy information to users.

Map the whole data journey

Identify sensing, local storage, communication, ingestion, validation, processing, database storage and publication. Each stage may fail independently or share an upstream dependency.

Define what users actually need

A researcher downloading a monthly dataset has different continuity needs from an operational team using near-real-time environmental information. Set priorities according to consequences and service purpose.

Protect observation time

If readings arrive late after a communications failure, retain their original measurement timestamps. Do not relabel historical observations as live conditions.

Design for partial failure

Appropriate buffering, backup storage, alternate communication or reduced-service modes may preserve some value. The correct arrangements depend on criticality, budget and technical constraints.

Explain stale and missing information

A dashboard should not quietly display yesterday’s value as current. Clearly distinguish fresh measurements, delayed data, quality-flagged readings and unavailable coverage.

Reconcile after restoration

Delayed batches can contain gaps, duplicates and out-of-order records. Verify completeness, units and quality before merging them into authoritative datasets.

Test dependencies, not only devices

A simulated gateway failure or database outage can reveal whether monitoring and recovery processes work. Test in controlled conditions that do not compromise operational safety.

Break-test: the API recovers but the dataset is incomplete

Can users see which periods remain missing, and does the responsible team continue recovery rather than declaring full success at the first successful request?

What proves continuity

Measure usable-data availability, data freshness, integrity after recovery, completeness and time to verified service restoration. Sensor uptime is only one contributing measure.

Connected knowledge

See Sensor Network Resilience, Service Level Verification and NEA.