Fire Simulations

Building Footprints

v0

3 hours ago

Example Simulation: Oceanside MTT (2026-11-03 17:51)

Built 2 hours ago

Fire run for the simulation "Example Simulation", from Simulations.

v0

2 hours ago

Example Simulation: Oceanside MTT 2 MM (2026-11-03 18:45)

Built 51 minutes ago

Fire run for the simulation "Example Simulation", from Simulations.

v0

49 minutes ago

Example Simulation: Oceanside MTT 2 MM — Assets reached

Built 51 minutes ago

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulation: Oceanside MTT 2 MM (2026-11-03 18:45)".

v0

49 minutes ago

Example Simulation: Oceanside MTT 2 MM — Burning edge by time

Built 51 minutes ago

The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Example Simulation: Oceanside MTT 2 MM (2026-11-03 18:45)".

v0

49 minutes ago

Example Simulation: Oceanside MTT 2 MM — Engine routes

Built 51 minutes ago

Every engine's drive and every crew's walk: the line it took, with `times` the minute at each vertex in order (comma-separated), and when it left and got there. `kind` is engine or crew. Written by each run of the fire simulation whose output file is "Example Simulation: Oceanside MTT 2 MM (2026-11-03 18:45)".

v0

49 minutes ago

Example Simulation: Oceanside MTT 2 MM — Evacuation zones

Built 51 minutes ago

Each evacuation zone as Order (the fire within about half a mile in the next hour), Warning (within about two miles in the next three hours) or not at risk, with the minute it became each. Written by each run of the fire simulation whose output file is "Example Simulation: Oceanside MTT 2 MM (2026-11-03 18:45)".

v0

49 minutes ago

Example Simulation: Oceanside MTT 2 MM — Fire pathways

Built 51 minutes ago

The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Example Simulation: Oceanside MTT 2 MM (2026-11-03 18:45)".

v0

49 minutes ago

Example Simulation: Oceanside MTT 2 MM — Perimeters by time

Built 51 minutes ago

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulation: Oceanside MTT 2 MM (2026-11-03 18:45)".

v0

49 minutes ago

Example Simulation: Oceanside MTT 2 MM — Roads reached

Built 51 minutes ago

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulation: Oceanside MTT 2 MM (2026-11-03 18:45)".

v0

49 minutes ago

Example Simulation: Oceanside MTT 2 MM — Spot landings

Built 51 minutes ago

Where each spotting source's farthest ember lands, as points, with the same columns as Spotting. `spotFire` true: landed outside the fire, ahead of the front. Written by each run of the fire simulation whose output file is "Example Simulation: Oceanside MTT 2 MM (2026-11-03 18:45)".

v0

49 minutes ago

Example Simulation: Oceanside MTT 2 MM — Spotting

Built 51 minutes ago

Embers, one line per spotting source: from a burning cell with a maximum spot distance to where its farthest ember lands (FlamMap's maximum spot distance and direction under the run's wind, not the engine's random draws). `minutes` when the source burned, `distanceMeters`, `fireType` 1 surface / 2 passive crown / 3 active crown at the source, `landingMinutes` when the fire reached the landing, `spotFire` true when the landing was outside the fire at the time (worked out in DuckDB against the arrival table). The longest in each part of the fire when there are more than a map can draw. Written by each run of the fire simulation whose output file is "Example Simulation: Oceanside MTT 2 MM (2026-11-03 18:45)".

v0

49 minutes ago

Example Simulation: Oceanside MTT — Assets reached

Built 2 hours ago

Every asset the fire reached, with the minute and the clock time it did. Written by each run of the fire simulation whose output file is "Example Simulation: Oceanside MTT (2026-11-03 17:51)".

v0

2 hours ago

Example Simulation: Oceanside MTT — Burning edge by time

Built 2 hours ago

The part of the fire's edge still burning at each time step: next to ground the front reached within the step or not yet in the black (worked out in DuckDB from the arrival and cooled tables). An edge stopped by a treatment drops out once it cools. Written by each run of the fire simulation whose output file is "Example Simulation: Oceanside MTT (2026-11-03 17:51)".

v0

2 hours ago

Example Simulation: Oceanside MTT — Burning homes by time

Built 2 hours ago

Homes lit house to house (not by the wildland fire itself), drawn as the fire's ground: each time band's homes with their yards, neighbors within about 30 m joined into one shape (grown and shrunk in DuckDB). One ring per band, `minutes` its end and `homes` how many it lit. Shown only: the run's acres stay the wildland's. Written by each run of the fire simulation whose output file is "Example Simulation: Oceanside MTT (2026-11-03 17:51)".

v0

2 hours ago

Example Simulation: Oceanside MTT — Damage per structure (estimate)

Built 2 hours ago

Each structure the fire reached, classed on the DINS field scale (Destroyed, Major, Minor, Affected) from how it burned: house to house, flame length, or only reached. A screening estimate, not an assessment. Written by each run of the fire simulation whose output file is "Example Simulation: Oceanside MTT (2026-11-03 17:51)".

v0

2 hours ago

Example Simulation: Oceanside MTT — Engine routes

Built 2 hours ago

Every engine's drive and every crew's walk: the line it took, with `times` the minute at each vertex in order (comma-separated), and when it left and got there. `kind` is engine or crew. Written by each run of the fire simulation whose output file is "Example Simulation: Oceanside MTT (2026-11-03 17:51)".

v0

2 hours ago

Example Simulation: Oceanside MTT — Evacuation zones

Built 2 hours ago

Each evacuation zone as Order (the fire within about half a mile in the next hour), Warning (within about two miles in the next three hours) or not at risk, with the minute it became each. Written by each run of the fire simulation whose output file is "Example Simulation: Oceanside MTT (2026-11-03 17:51)".

v0

2 hours ago

Example Simulation: Oceanside MTT — Fire pathways

Built 2 hours ago

The main routes the fire took: its arrival time read like a DEM, each cell stepping back to the neighbour the fire came from, and the ways most of the burned area ran through kept. `use` counts the burned cells whose way back runs through a piece and `share` is that over all of them: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Example Simulation: Oceanside MTT (2026-11-03 17:51)".

v0

2 hours ago

Example Simulation: Oceanside MTT — Perimeters by time

Built 2 hours ago

The fire's extent at each time step of the run, one polygon per step, cumulative. Filter on `hours` or `clockTime` to pick one perimeter. Written by each run of the fire simulation whose output file is "Example Simulation: Oceanside MTT (2026-11-03 17:51)".

v0

2 hours ago

Example Simulation: Oceanside MTT — Roads cut off

Built 2 hours ago

Roads that lose every way out of the simulated area, and while: walked as a network in DuckDB at each time step, with burning roads closed and roads in the black open again. Written by each run of the fire simulation whose output file is "Example Simulation: Oceanside MTT (2026-11-03 17:51)".

v0

2 hours ago

Example Simulation: Oceanside MTT — Roads reached

Built 2 hours ago

Every stretch of road the fire reached, cut where it crosses each time step, with the minute and clock time it was cut. Worked out in DuckDB from the arrival table. Written by each run of the fire simulation whose output file is "Example Simulation: Oceanside MTT (2026-11-03 17:51)".

v0

2 hours ago

Example Simulation: Oceanside MTT — Spot landings

Built 2 hours ago

Where each spotting source's farthest ember lands, as points, with the same columns as Spotting. `spotFire` true: landed outside the fire, ahead of the front. Written by each run of the fire simulation whose output file is "Example Simulation: Oceanside MTT (2026-11-03 17:51)".

v0

2 hours ago

Example Simulation: Oceanside MTT — Spotting

Built 2 hours ago

Embers, one line per spotting source: from a burning cell with a maximum spot distance to where its farthest ember lands (FlamMap's maximum spot distance and direction under the run's wind, not the engine's random draws). `minutes` when the source burned, `distanceMeters`, `fireType` 1 surface / 2 passive crown / 3 active crown at the source, `landingMinutes` when the fire reached the landing, `spotFire` true when the landing was outside the fire at the time (worked out in DuckDB against the arrival table). The longest in each part of the fire when there are more than a map can draw. Written by each run of the fire simulation whose output file is "Example Simulation: Oceanside MTT (2026-11-03 17:51)".

v0

2 hours ago

Fire Stations

v0

3 hours ago

TillamookLCP.zip

v0

3 hours ago

tl_2026_41057_roads.zip

v0

3 hours ago

Fire Simulations

Files