What it is
An urban air-quality network measures pollutants across locations and time. Lower-cost devices can improve spatial coverage but require co-location, calibration, uncertainty reporting, maintenance, and careful comparison with regulatory monitors.
How the system fits together
Physical and digital layer
Document the equipment, software, interfaces, and geographic scope as separate maintained components.
Data and identity
Record data owners, timestamps, identifiers, quality limits, access rules, and retention before combining feeds.
Operating workflow
Name the team that reviews outputs, can override automation, and remains responsible during faults or outages.
Evaluation
Compare service, equity, safety, reliability, and cost against a published baseline rather than counting installed devices.
- 01
Physical and digital layer
- 02
Data and identity
- 03
Operating workflow
- 04
Evaluation
Where cities use it
- Exposure and hotspot research
- Public information
- Evaluating traffic or building interventions
Data generated
- Pollutant concentrations
- Weather and device health
- Calibration and siting metadata
Analytics and AI applications
- Spatial interpolation
- Anomaly detection
- Time-series analysis
Example in practice
A city co-locates lower-cost sensors with reference stations across seasons before using them to describe neighborhood patterns.
Design considerations
Choose sensor placement and refresh rates from an operational need. Keep device identity, calibration, network health, and location visible to the team using the data.
Limits and risks
- Integration can concentrate security and vendor dependencies.
- Uneven coverage or stale records can make a precise interface misleading.
- A technical capability does not establish necessity, public value, or a measured outcome.