During an active incident, responders need a clear view of which observations have arrived, when they were observed and received, how old they are, and which declared information prerequisites remain unknown.
The goal is to support firefighting by keeping incoming evidence, weather context, source timing, and gaps visible as conditions change. The public interface is a synthetic continuous playback that demonstrates this measurement pattern. It is not connected to an active incident or operational data source.
The replay preserves 52 published observations from a bounded early Concow extract in NIST Technical Note 2135, Appendix F. The source clock and observation windows are shown; the extract is not the full incident.
Original incident receipt times are unknown. The replay applies an explicitly assumed reporting delay, so its arrival order is a scenario and not a reconstruction of the actual communications sequence.
NIST Technical Note 2135The interface includes an ignition-period Jarbo Gap summary reported by NIST: sustained wind 18 mph, gusts 40 mph, and relative humidity 23%, with regional foothill and ridgetop winds predominantly from the northeast and a Red Flag Warning covering Nov. 7–9, 2018.
These are historical context values, not current conditions or a minute-by-minute weather feed. Local variation is unresolved; the replay does not supply current temperature, visibility, or fuel moisture.
A continuously updated view can organize arriving observations by source, observation time, receipt time, age, and provenance, while making missing or stale records visible. Weather and access information would need authoritative, time-aligned sources and clearly stated confidence and coverage.
This concept does not estimate fire spread or time to impact, determine whether a route is safe, assess resource readiness, or choose tactics. It displays evidence state and declared gaps; professional incident command remains responsible for interpretation and action.
A practitioner evaluation would need authorized live sources, resilient ingestion, timestamp and location validation, source provenance, latency and outage handling, incident-specific boundaries, and review with fire-service users. The synthetic playback demonstrates only the interface pattern; it does not establish accuracy, operational fitness, or improved response.
The public demo is synthetic continuous playback, not live incident monitoring, a field-ready wildfire instrument, fire prediction, evacuation guidance, dispatch, or a tactical recommendation. It does not establish improved response. A real-time firefighting support system is the intended direction; it would require validated operational sources and field evaluation before use. The Camp Fire material above is historical reference only. No FireSat or WIFIRE data are used.