Sites requiring attention
Current sites within 10 miles of credible fire activity, closest first.
Checking live fire intelligence…
Recent / previous fire history
Reference only — these incidents do not affect current risk counters and are not shown on the live map by default.
Historical entries come from the dashboard’s stored reported-fire snapshot. They are clearly separated from live verified-fire and satellite activity to avoid confusion.
Screening rule. A site can be triggered either by a freshness-verified authoritative reported fire or by a qualifying satellite cluster. A satellite concern still requires at least two nominal/high-confidence VIIRS detections within 1 mile of each other, no more than 12 hours old, including at least one high-confidence detection. Authoritative news must be published within the last 24 hours and clearly describe a real fire/blaze/wildfire incident. Direct official incident pages must also expose a recent published/modified timestamp before they can drive live risk counters. Verified-fire cards prioritise authoritative incident details and do not show blank satellite metrics. Satellite fire intensity is shown only when a qualifying satellite cluster exists. Reported fire size is shown only when a current article explicitly states a size. Current temperature, apparent temperature, humidity, conditions, wind and gusts refresh with the same 15-minute dashboard cycle. Wind direction is compared with the bearing from the cluster to the site to indicate whether wind is broadly toward, crosswind or away from the site. The 5-day timeline is a weather outlook, not a fire-spread forecast. For satellite-derived risk, distance is measured to the closest qualifying VIIRS fire-detection point within the cluster. For verified reported fires, distance is measured to the geolocated incident point or published location; where an exact perimeter is unavailable this remains approximate. This is intentionally conservative. The verified-fire feed uses direct official incident checks plus authoritative discovery, with visible source-health status. FireMap.live is included as an independent visual cross-check source, not as a sole automatic trigger because its public site does not expose a documented open incident API. If source coverage is degraded the dashboard says so instead of presenting a misleading zero. Satellite data indicates thermal activity, not an exact flame front or confirmed wildfire perimeter.