blog / how-often-should-block-level-surface-temperature-data-refres

How often should block-level heat data refresh between seasons

Aerial view of a town's edge, with a housing estate, warehouses, and a construction site under a cloudy sky.

A parks director asked us this at a budget hearing last spring: if we buy heat data once, do we have to keep buying it every month to keep it useful? Monthly buys you little beyond weather noise, and a single purchase from three summers ago buys you even less by the time you need it. The right rhythm tracks the cooling season itself.

Why block-level heat data goes stale

Surface temperature at the block level isn't static the way a zoning map is. A parking lot gets repaved in June and runs five degrees hotter by July. A nonprofit plants forty street trees along a corridor in April, and by the third summer that canopy is shading sidewalks that used to bake. A warehouse gets demolished and the asphalt pad sits exposed for two years before anything replaces it. None of that shows up if you're working off imagery from three summers ago, and none of it shows up gradually enough that you'd notice without a fresh read.

The demographic side of the overlay changes too, just on census cadence rather than seasonal cadence. A block that was mostly rental units with high elderly occupancy can shift after a redevelopment cycle, sometimes within a couple of years. The heat layer and the vulnerability layer age at different rates, and a refresh schedule needs to account for both separately.

How often is enough

For most cities, two passes a year covers it: one before the cooling season starts, and one near peak heat. The pre-season pass gives you a baseline to plan against, siting cooling centers, deciding which blocks get first call on shade-tree budget, briefing public health on where to expect the worst heat-related 911 calls. The peak-season pass checks that baseline against what's happening on the hottest days, which is when surface temperature differences between blocks are most pronounced and most worth acting on.

A once-a-year read, taken right before the season, is the minimum that's actually useful for targeting investment. Anything less than that and you're planning off data that might be two or three construction cycles out of date. Anything more frequent than seasonal, weekly or monthly, mostly captures weather noise rather than the built-environment changes you're trying to track, and it costs more than the decision in front of you requires.

The exception is after a major capital project. If your department just finished a shade-tree planting on fifteen blocks or a cool-roof retrofit on a public housing complex, it's worth pulling a fresh pass the following summer specifically to see if the intervention moved the number. Run that pass as a one-off check tied to the specific investment, separate from your regular two-pass schedule.

When to update the citywide picture versus a single block

There's a difference between updating your whole heat map and checking in on a handful of blocks. If you're mid-cycle on a cooling-center siting decision and a council member wants to know whether a specific block still qualifies as a priority, you don't need a new citywide pass, you need that block's current read. Save the full-city refresh for the season boundary: once before summer to set priorities, once during peak to confirm them.

This is also where the "whole city at once" instinct costs planners time they don't have. Most departments don't need every block resurveyed on the same clock. The blocks that were borderline last year are the ones worth checking first; the blocks that were clearly hottest or clearly coolest two seasons running probably haven't flipped.

If you're setting this up for the first time, Heat Exposure Mapping builds the overlay around that seasonal rhythm instead of a one-time snapshot, so the surface temperature, building type, and demographic layers stay lined up with the cadence your budget cycle runs on.

Figuring out your own refresh schedule starts with knowing which blocks you're tracking and why. Get in touch and we'll help you map out a cadence that fits your cooling season.

Start a pilot