Aggregation timing

A region's score can only move as fast as its slowest input. Which is why your region's score is from last year.

Why each ring of the nested Index refreshes at a different speed. Neighbourhood sensors update hourly. City portals update every few months. EUROSTAT regional material-flow accounting (a count of what a region pulls in and throws out) arrives 18 months late. This page stacks those schedules — how often each source publishes — so you can see which level each one holds back.The slowest input decides how often the outermost ring can refresh, and that is the EUROSTAT lag at the region level.

11 kinds of indicator · 5 update rhythms Slowest input · 540-day lag (EUROSTAT MFA) Fastest input · ≤ 1-hour (PM2.5 sensors)
Neighbourhood indicators (hours → months) City indicators (hours → annual) Region indicators (annual cadence · up to 18-month lag)
The slowest link

The Region ring cannot complete a refresh faster than its slowest input. That input is currently: 540 days

EUROSTAT regional Material Flow Accounting publishes once a year, 18 months behind. Until that lag shrinks, or a faster regional stand-in is added, the region's score is an 18-month-old picture. The region ring's mock pill — the sample-data label on its score — should always say so.This is not a flaw in the method; it is how the regional governance level works, and the dashboard's job is to show it plainly.

Why the update rhythm matters for ρ

ρ measures how long it takes to turn a reading into action. A PM2.5 spike at the neighbourhood council can be acted on within a week: a high ρ at the neighbourhood. A Generalitat (Catalonia's regional government) reading that lands 540 days late cannot be acted on inside its own cycle. At the region, the update rhythm sets a hard ceiling on ρ.

One discipline note: ρ is only a real measurement where there is an agreed way to measure how fast action follows a reading.Region-level ρ is currently mock, ρ protocol pending in every pilot (no partner runs a regional policy-adoption tracker). Where ρ cannot be measured, the dashboard shows n/a — protocol pending; ρ is never quietly set to 1, because an unmeasured response is not a perfect one.

What the nesting does to the lag

The nesting rule — each level's record begins with the smaller level's — means the region's first 256 numbers are the city's.When the city refreshes every few months, those numbers update inside the region even before the annual EUROSTAT release. The full region record is only complete once the slowest input lands, but its opening stretch is current. That is the answer to "why is the region score updating monthly when the material-flow data only lands once a year?"

↪ Return to the aggregation atlas · or read the scale-by-scale walk from the ground up.