The official monitor and the sensors near you disagree
The regulatory monitor and the median of nearby outdoor sensors can read differently in the same city at the same hour. The monitor is one instrument, sited for regulatory coverage; the sensor network is dozens to hundreds of devices sited where people live. Neither is wrong. They measure different things, and the difference is what a resident actually notices.
The gap right now
| Metro | Official | Sensors | Gap | Devices |
|---|
We don't have sensor readings right now, for any metro. The sensor leg of our pipeline is not returning data, so there is no gap to show — the table is empty because that side of the comparison is missing, not because the cities lack sensors. We would rather show an empty table than an official number with nothing beside it dressed up as a comparison. The official monitor readings are still live on every city page.
Why they disagree
Four mechanisms account for most of it, and they are not errors. Averaging window: the official figure is smoothed across recent hours, so a sharp afternoon plume shows up late, held back by a clean morning. Siting: one monitor covers a whole metro, and it sits where regulation requires, not where you stand. Height: smoke can travel aloft, above the sensor layer. Instrument: low-cost sensors read high in humidity, which is why the correction above exists.
How to use this
When the two numbers are close, either one is fine to act on. When they diverge by more than about 20 points, treat the higher one as the better guide for the next hour and the lower one as the better guide for the day — the monitor is slower and smoother, the sensors are faster and noisier.
Method and reuse
Both series are refreshed hourly and stored from day one. Sources: EPA AirNow (regulatory monitors) and PurpleAir (outdoor devices only, `location_type=0`). Metros with fewer than three reporting devices are left blank rather than averaged into a number we cannot stand behind.
Updated