Fire Behavior

Ash Canyon: Run 1 (2026-10-20 16:56)

Built 2 weeks ago

Fire run for the simulation "Ash Canyon", from Simulations.

v0

2 weeks ago

Ash Canyon: Run 1 — Assets reached

Built 2 weeks 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 "Ash Canyon: Run 1 (2026-10-20 16:56)".

v0

2 weeks ago

Ash Canyon: Run 1 — Burning edge by time

Built 2 weeks 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 "Ash Canyon: Run 1 (2026-10-20 16:56)".

v0

2 weeks ago

Ash Canyon: Run 1 — Fire pathways

Built 2 weeks 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 "Ash Canyon: Run 1 (2026-10-20 16:56)".

v0

2 weeks ago

Ash Canyon: Run 1 — Perimeters by time

Built 2 weeks 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 "Ash Canyon: Run 1 (2026-10-20 16:56)".

v0

2 weeks ago

Ash Canyon: Run 1 — Roads cut off

Built 2 weeks 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 "Ash Canyon: Run 1 (2026-10-20 16:56)".

v0

2 weeks ago

Ash Canyon: Run 1 — Roads reached

Built 2 weeks 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 "Ash Canyon: Run 1 (2026-10-20 16:56)".

v0

2 weeks ago

Ash Canyon: Run 1 — Spot landings

Built 2 weeks 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 "Ash Canyon: Run 1 (2026-10-20 16:56)".

v0

2 weeks ago

Ash Canyon: Run 1 — Spotting

Built 2 weeks 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 "Ash Canyon: Run 1 (2026-10-20 16:56)".

v0

2 weeks ago

Ash Canyon: Run 2 (2026-10-20 17:06)

Built 2 weeks ago

Fire run for the simulation "Ash Canyon", from Simulations.

v0

2 weeks ago

Ash Canyon: Run 2 (2026-10-20 20:55)

Built 2 weeks ago

Fire run for the simulation "Ash Canyon", from Simulations.

v0

2 weeks ago

Ash Canyon: Run 2 — Assets reached

Built 2 weeks 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 "Ash Canyon: Run 2 (2026-10-20 20:55)".

v0

2 weeks ago

Ash Canyon: Run 2 — Assets reached

Built 2 weeks 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 "Ash Canyon: Run 2 (2026-10-20 17:06)".

v0

2 weeks ago

Ash Canyon: Run 2 — Burning edge by time

Built 2 weeks 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 "Ash Canyon: Run 2 (2026-10-20 17:06)".

v0

2 weeks ago

Ash Canyon: Run 2 — Burning edge by time

Built 2 weeks 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 "Ash Canyon: Run 2 (2026-10-20 20:55)".

v0

2 weeks ago

Ash Canyon: Run 2 — Fire pathways

Built 2 weeks 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 "Ash Canyon: Run 2 (2026-10-20 20:55)".

v0

2 weeks ago

Ash Canyon: Run 2 — Fire pathways

Built 2 weeks 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 "Ash Canyon: Run 2 (2026-10-20 17:06)".

v0

2 weeks ago

Ash Canyon: Run 2 — Perimeters by time

Built 2 weeks 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 "Ash Canyon: Run 2 (2026-10-20 20:55)".

v0

2 weeks ago

Ash Canyon: Run 2 — Perimeters by time

Built 2 weeks 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 "Ash Canyon: Run 2 (2026-10-20 17:06)".

v0

2 weeks ago

Ash Canyon: Run 2 — Roads cut off

Built 2 weeks 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 "Ash Canyon: Run 2 (2026-10-20 17:06)".

v0

2 weeks ago

Ash Canyon: Run 2 — Roads cut off

Built 2 weeks 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 "Ash Canyon: Run 2 (2026-10-20 20:55)".

v0

2 weeks ago

Ash Canyon: Run 2 — Roads reached

Built 2 weeks 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 "Ash Canyon: Run 2 (2026-10-20 17:06)".

v0

2 weeks ago

Ash Canyon: Run 2 — Roads reached

Built 2 weeks 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 "Ash Canyon: Run 2 (2026-10-20 20:55)".

v0

2 weeks ago

Ash Canyon: Run 2 — Spot landings

Built 2 weeks 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 "Ash Canyon: Run 2 (2026-10-20 17:06)".

v0

2 weeks ago

Ash Canyon: Run 2 — Spot landings

Built 2 weeks 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 "Ash Canyon: Run 2 (2026-10-20 20:55)".

v0

2 weeks ago

Ash Canyon: Run 2 — Spotting

Built 2 weeks 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 "Ash Canyon: Run 2 (2026-10-20 20:55)".

v0

2 weeks ago

Ash Canyon: Run 2 — Spotting

Built 2 weeks 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 "Ash Canyon: Run 2 (2026-10-20 17:06)".

v0

2 weeks ago

Ash Canyon: Run 3 (2026-10-20 17:41)

Built 2 weeks ago

Fire run for the simulation "Ash Canyon", from Simulations.

v0

2 weeks ago

Ash Canyon: Run 3 — Assets reached

Built 2 weeks 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 "Ash Canyon: Run 3 (2026-10-20 17:41)".

v0

2 weeks ago

Ash Canyon: Run 3 — Burning edge by time

Built 2 weeks 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 "Ash Canyon: Run 3 (2026-10-20 17:41)".

v0

2 weeks ago

Ash Canyon: Run 3 — Fire pathways

Built 2 weeks 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 "Ash Canyon: Run 3 (2026-10-20 17:41)".

v0

2 weeks ago

Ash Canyon: Run 3 — Perimeters by time

Built 2 weeks 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 "Ash Canyon: Run 3 (2026-10-20 17:41)".

v0

2 weeks ago

Ash Canyon: Run 3 — Roads cut off

Built 2 weeks 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 "Ash Canyon: Run 3 (2026-10-20 17:41)".

v0

2 weeks ago

Ash Canyon: Run 3 — Roads reached

Built 2 weeks 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 "Ash Canyon: Run 3 (2026-10-20 17:41)".

v0

2 weeks ago

Ash Canyon: Run 3 — Spot landings

Built 2 weeks 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 "Ash Canyon: Run 3 (2026-10-20 17:41)".

v0

2 weeks ago

Ash Canyon: Run 3 — Spotting

Built 2 weeks 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 "Ash Canyon: Run 3 (2026-10-20 17:41)".

v0

2 weeks ago

Ash Canyon: Run 4 (2026-10-20 17:52)

Built 2 weeks ago

Fire run for the simulation "Ash Canyon", from Simulations.

v0

2 weeks ago

Ash Canyon: Run 4 — Assets reached

Built 2 weeks 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 "Ash Canyon: Run 4 (2026-10-20 17:52)".

v0

2 weeks ago

Ash Canyon: Run 4 — Burning edge by time

Built 2 weeks 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 "Ash Canyon: Run 4 (2026-10-20 17:52)".

v0

2 weeks ago

Ash Canyon: Run 4 — Fire pathways

Built 2 weeks 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 "Ash Canyon: Run 4 (2026-10-20 17:52)".

v0

2 weeks ago

Ash Canyon: Run 4 — Perimeters by time

Built 2 weeks 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 "Ash Canyon: Run 4 (2026-10-20 17:52)".

v0

2 weeks ago

Ash Canyon: Run 4 — Roads cut off

Built 2 weeks 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 "Ash Canyon: Run 4 (2026-10-20 17:52)".

v0

2 weeks ago

Ash Canyon: Run 4 — Roads reached

Built 2 weeks 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 "Ash Canyon: Run 4 (2026-10-20 17:52)".

v0

2 weeks ago

Ash Canyon: Run 4 — Spot landings

Built 2 weeks 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 "Ash Canyon: Run 4 (2026-10-20 17:52)".

v0

2 weeks ago

Ash Canyon: Run 4 — Spotting

Built 2 weeks 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 "Ash Canyon: Run 4 (2026-10-20 17:52)".

v0

2 weeks ago

B Test 2: Defensible Space Treatment (2026-10-20 19:59)

Needs upload

Fire run for the simulation "B Test 2", from Simulations.

2 weeks ago

B Test 2: Defensible Space Treatment (2026-10-20 20:01)

Needs upload

Fire run for the simulation "B Test 2", from Simulations.

2 weeks ago

B Test 2: Defensible Space Treatment (2026-10-20 20:05)

Needs upload

Fire run for the simulation "B Test 2", from Simulations.

2 weeks ago

B Test 2: Defensible Space Treatment (2026-10-20 20:18)

Needs upload

Fire run for the simulation "B Test 2", from Simulations.

2 weeks ago

B Test 2: Defensible Space Treatment (2026-10-20 21:12)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Defensible Space Treatment — Assets reached

Built 2 weeks 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 "B Test 2: Defensible Space Treatment (2026-10-20 21:12)".

v0

2 weeks ago

B Test 2: Defensible Space Treatment — Burning edge by time

Built 2 weeks 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 "B Test 2: Defensible Space Treatment (2026-10-20 21:12)".

v0

2 weeks ago

B Test 2: Defensible Space Treatment — Fire pathways

Built 2 weeks 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 "B Test 2: Defensible Space Treatment (2026-10-20 21:12)".

v0

2 weeks ago

B Test 2: Defensible Space Treatment — Perimeters by time

Built 2 weeks 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 "B Test 2: Defensible Space Treatment (2026-10-20 21:12)".

v0

2 weeks ago

B Test 2: Defensible Space Treatment — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Defensible Space Treatment (2026-10-20 21:12)".

v0

2 weeks ago

B Test 2: Defensible Space Treatment — Spot landings

Built 2 weeks 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 "B Test 2: Defensible Space Treatment (2026-10-20 21:12)".

v0

2 weeks ago

B Test 2: Defensible Space Treatment — Spotting

Built 2 weeks 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 "B Test 2: Defensible Space Treatment (2026-10-20 21:12)".

v0

2 weeks ago

B Test 2: Fuel Break Treatment (2026-10-20 18:30)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Fuel Break Treatment — Burning edge by time

Built 2 weeks 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 "B Test 2: Fuel Break Treatment (2026-10-20 18:30)".

v0

2 weeks ago

B Test 2: Fuel Break Treatment — Fire pathways

Built 2 weeks 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 "B Test 2: Fuel Break Treatment (2026-10-20 18:30)".

v0

2 weeks ago

B Test 2: Fuel Break Treatment — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Fuel Break Treatment (2026-10-20 18:30)".

v0

2 weeks ago

B Test 2: Fuel Break Treatment — Spot landings

Built 2 weeks 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 "B Test 2: Fuel Break Treatment (2026-10-20 18:30)".

v0

2 weeks ago

B Test 2: Fuel Break Treatment — Spotting

Built 2 weeks 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 "B Test 2: Fuel Break Treatment (2026-10-20 18:30)".

v0

2 weeks ago

B Test 2: Grazed or Mowed Treatment (2026-10-20 18:48)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Grazed or Mowed Treatment — Burning edge by time

Built 2 weeks 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 "B Test 2: Grazed or Mowed Treatment (2026-10-20 18:48)".

v0

2 weeks ago

B Test 2: Grazed or Mowed Treatment — Fire pathways

Built 2 weeks 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 "B Test 2: Grazed or Mowed Treatment (2026-10-20 18:48)".

v0

2 weeks ago

B Test 2: Grazed or Mowed Treatment — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Grazed or Mowed Treatment (2026-10-20 18:48)".

v0

2 weeks ago

B Test 2: Grazed or Mowed Treatment — Spot landings

Built 2 weeks 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 "B Test 2: Grazed or Mowed Treatment (2026-10-20 18:48)".

v0

2 weeks ago

B Test 2: Grazed or Mowed Treatment — Spotting

Built 2 weeks 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 "B Test 2: Grazed or Mowed Treatment (2026-10-20 18:48)".

v0

2 weeks ago

B Test 2: New Development Treatment (2026-10-20 18:51)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: New Development Treatment — Burning edge by time

Built 2 weeks 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 "B Test 2: New Development Treatment (2026-10-20 18:51)".

v0

2 weeks ago

B Test 2: New Development Treatment — Fire pathways

Built 2 weeks 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 "B Test 2: New Development Treatment (2026-10-20 18:51)".

v0

2 weeks ago

B Test 2: New Development Treatment — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: New Development Treatment (2026-10-20 18:51)".

v0

2 weeks ago

B Test 2: New Development Treatment — Spot landings

Built 2 weeks 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 "B Test 2: New Development Treatment (2026-10-20 18:51)".

v0

2 weeks ago

B Test 2: New Development Treatment — Spotting

Built 2 weeks 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 "B Test 2: New Development Treatment (2026-10-20 18:51)".

v0

2 weeks ago

B Test 2: No Treatment (2026-10-20 19:06)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: No Treatment — Burning edge by time

Built 2 weeks 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 "B Test 2: No Treatment (2026-10-20 19:06)".

v0

2 weeks ago

B Test 2: No Treatment — Fire pathways

Built 2 weeks 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 "B Test 2: No Treatment (2026-10-20 19:06)".

v0

2 weeks ago

B Test 2: No Treatment — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: No Treatment (2026-10-20 19:06)".

v0

2 weeks ago

B Test 2: No Treatment — Spot landings

Built 2 weeks 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 "B Test 2: No Treatment (2026-10-20 19:06)".

v0

2 weeks ago

B Test 2: No Treatment — Spotting

Built 2 weeks 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 "B Test 2: No Treatment (2026-10-20 19:06)".

v0

2 weeks ago

B Test 2: Recent Burn Treatment (2026-10-20 18:29)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Recent Burn Treatment — Burning edge by time

Built 2 weeks 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 "B Test 2: Recent Burn Treatment (2026-10-20 18:29)".

v0

2 weeks ago

B Test 2: Recent Burn Treatment — Fire pathways

Built 2 weeks 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 "B Test 2: Recent Burn Treatment (2026-10-20 18:29)".

v0

2 weeks ago

B Test 2: Recent Burn Treatment — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Recent Burn Treatment (2026-10-20 18:29)".

v0

2 weeks ago

B Test 2: Recent Burn Treatment — Spot landings

Built 2 weeks 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 "B Test 2: Recent Burn Treatment (2026-10-20 18:29)".

v0

2 weeks ago

B Test 2: Recent Burn Treatment — Spotting

Built 2 weeks 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 "B Test 2: Recent Burn Treatment (2026-10-20 18:29)".

v0

2 weeks ago

B Test 2: Run 1 (2026-10-19 17:37)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Run 1 (2026-10-19 17:40)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Run 1 (2026-10-19 17:43)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Run 1 — Burning edge by time

Built 2 weeks 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 "B Test 2: Run 1 (2026-10-19 17:40)".

v0

2 weeks ago

B Test 2: Run 1 — Burning edge by time

Built 2 weeks 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 "B Test 2: Run 1 (2026-10-19 17:37)".

v0

2 weeks ago

B Test 2: Run 1 — Burning edge by time

Built 2 weeks 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 "B Test 2: Run 1 (2026-10-19 17:43)".

v0

2 weeks ago

B Test 2: Run 1 — Fire pathways

Built 2 weeks ago

The routes the fire took, traced back from its edge along its arrival time. `use` counts the traced paths through a piece: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "B Test 2: Run 1 (2026-10-19 17:40)".

v0

2 weeks ago

B Test 2: Run 1 — Fire pathways

Built 2 weeks ago

The routes the fire took, traced back from its edge along its arrival time. `use` counts the traced paths through a piece: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "B Test 2: Run 1 (2026-10-19 17:37)".

v0

2 weeks ago

B Test 2: Run 1 — Fire pathways

Built 2 weeks ago

The routes the fire took, traced back from its edge along its arrival time. `use` counts the traced paths through a piece: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "B Test 2: Run 1 (2026-10-19 17:43)".

v0

2 weeks ago

B Test 2: Run 1 — Perimeters by time

Built 2 weeks 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 "B Test 2: Run 1 (2026-10-19 17:37)".

v2

2 weeks ago

B Test 2: Run 1 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Run 1 (2026-10-19 17:37)".

v0

2 weeks ago

B Test 2: Run 1 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Run 1 (2026-10-19 17:40)".

v0

2 weeks ago

B Test 2: Run 1 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Run 1 (2026-10-19 17:43)".

v0

2 weeks ago

B Test 2: Run 1 — Spot landings

Built 2 weeks 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 "B Test 2: Run 1 (2026-10-19 17:43)".

v0

2 weeks ago

B Test 2: Run 1 — Spot landings

Built 2 weeks 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 "B Test 2: Run 1 (2026-10-19 17:40)".

v0

2 weeks ago

B Test 2: Run 1 — Spot landings

Built 2 weeks 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 "B Test 2: Run 1 (2026-10-19 17:37)".

v0

2 weeks ago

B Test 2: Run 1 — Spotting

Built 2 weeks 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 "B Test 2: Run 1 (2026-10-19 17:40)".

v0

2 weeks ago

B Test 2: Run 1 — Spotting

Built 2 weeks 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 "B Test 2: Run 1 (2026-10-19 17:37)".

v0

2 weeks ago

B Test 2: Run 1 — Spotting

Built 2 weeks 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 "B Test 2: Run 1 (2026-10-19 17:43)".

v0

2 weeks ago

B Test 2: Run 11 (2026-10-20 15:49)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Run 11 (copy) (2026-10-20 15:57)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Run 11 (copy) — Burning edge by time

Built 2 weeks 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 "B Test 2: Run 11 (copy) (2026-10-20 15:57)".

v0

2 weeks ago

B Test 2: Run 11 (copy) — Debris flows (projected)

Built 2 weeks ago

Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "B Test 2: Run 11 (copy) (2026-10-20 15:57)".

v0

2 weeks ago

B Test 2: Run 11 (copy) — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "B Test 2: Run 11 (copy) (2026-10-20 15:57)".

v0

2 weeks ago

B Test 2: Run 11 (copy) — Fire pathways

Built 2 weeks 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 "B Test 2: Run 11 (copy) (2026-10-20 15:57)".

v0

2 weeks ago

B Test 2: Run 11 (copy) — Perimeters by time

Built 2 weeks 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 "B Test 2: Run 11 (copy) (2026-10-20 15:57)".

v0

2 weeks ago

B Test 2: Run 11 (copy) — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Run 11 (copy) (2026-10-20 15:57)".

v0

2 weeks ago

B Test 2: Run 11 (copy) — Spot landings

Built 2 weeks 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 "B Test 2: Run 11 (copy) (2026-10-20 15:57)".

v0

2 weeks ago

B Test 2: Run 11 (copy) — Spotting

Built 2 weeks 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 "B Test 2: Run 11 (copy) (2026-10-20 15:57)".

v0

2 weeks ago

B Test 2: Run 11 — Burning edge by time

Built 2 weeks 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 "B Test 2: Run 11 (2026-10-20 15:49)".

v0

2 weeks ago

B Test 2: Run 11 — Debris flows (projected)

Built 2 weeks ago

Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "B Test 2: Run 11 (2026-10-20 15:49)".

v0

2 weeks ago

B Test 2: Run 11 — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "B Test 2: Run 11 (2026-10-20 15:49)".

v0

2 weeks ago

B Test 2: Run 11 — Fire pathways

Built 2 weeks 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 "B Test 2: Run 11 (2026-10-20 15:49)".

v0

2 weeks ago

B Test 2: Run 11 — Perimeters by time

Built 2 weeks 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 "B Test 2: Run 11 (2026-10-20 15:49)".

v0

2 weeks ago

B Test 2: Run 11 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Run 11 (2026-10-20 15:49)".

v0

2 weeks ago

B Test 2: Run 11 — Spot landings

Built 2 weeks 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 "B Test 2: Run 11 (2026-10-20 15:49)".

v0

2 weeks ago

B Test 2: Run 11 — Spotting

Built 2 weeks 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 "B Test 2: Run 11 (2026-10-20 15:49)".

v0

2 weeks ago

B Test 2: Run 13 (2026-10-20 17:08)

Needs upload

Fire run for the simulation "B Test 2", from Simulations.

2 weeks ago

B Test 2: Run 13 (2026-10-20 17:10)

Needs upload

Fire run for the simulation "B Test 2", from Simulations.

2 weeks ago

B Test 2: Run 13 (2026-10-20 17:13)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Run 13 (copy 2) (2026-10-20 17:35)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Run 13 (copy 2) — Assets reached

Built 2 weeks 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 "B Test 2: Run 13 (copy 2) (2026-10-20 17:35)".

v1

2 weeks ago

B Test 2: Run 13 (copy 2) — Burning edge by time

Built 2 weeks 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 "B Test 2: Run 13 (copy 2) (2026-10-20 17:35)".

v0

2 weeks ago

B Test 2: Run 13 (copy 2) — Fire pathways

Built 2 weeks 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 "B Test 2: Run 13 (copy 2) (2026-10-20 17:35)".

v0

2 weeks ago

B Test 2: Run 13 (copy 2) — Perimeters by time

Built 2 weeks 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 "B Test 2: Run 13 (copy 2) (2026-10-20 17:35)".

v1

2 weeks ago

B Test 2: Run 13 (copy 2) — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Run 13 (copy 2) (2026-10-20 17:35)".

v0

2 weeks ago

B Test 2: Run 13 (copy 2) — Spot landings

Built 2 weeks 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 "B Test 2: Run 13 (copy 2) (2026-10-20 17:35)".

v0

2 weeks ago

B Test 2: Run 13 (copy 2) — Spotting

Built 2 weeks 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 "B Test 2: Run 13 (copy 2) (2026-10-20 17:35)".

v0

2 weeks ago

B Test 2: Run 13 (copy 3) (2026-10-20 17:50)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Run 13 (copy 3) — Assets reached

Built 2 weeks 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 "B Test 2: Run 13 (copy 3) (2026-10-20 17:50)".

v1

2 weeks ago

B Test 2: Run 13 (copy 3) — Burning edge by time

Built 2 weeks 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 "B Test 2: Run 13 (copy 3) (2026-10-20 17:50)".

v0

2 weeks ago

B Test 2: Run 13 (copy 3) — Fire pathways

Built 2 weeks 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 "B Test 2: Run 13 (copy 3) (2026-10-20 17:50)".

v0

2 weeks ago

B Test 2: Run 13 (copy 3) — Perimeters by time

Built 2 weeks 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 "B Test 2: Run 13 (copy 3) (2026-10-20 17:50)".

v1

2 weeks ago

B Test 2: Run 13 (copy 3) — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Run 13 (copy 3) (2026-10-20 17:50)".

v0

2 weeks ago

B Test 2: Run 13 (copy 3) — Spot landings

Built 2 weeks 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 "B Test 2: Run 13 (copy 3) (2026-10-20 17:50)".

v0

2 weeks ago

B Test 2: Run 13 (copy 3) — Spotting

Built 2 weeks 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 "B Test 2: Run 13 (copy 3) (2026-10-20 17:50)".

v0

2 weeks ago

B Test 2: Run 13 (copy 4) (2026-10-20 18:13)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Run 13 (copy 4) — Assets reached

Built 2 weeks 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 "B Test 2: Run 13 (copy 4) (2026-10-20 18:13)".

v1

2 weeks ago

B Test 2: Run 13 (copy 4) — Burning edge by time

Built 2 weeks 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 "B Test 2: Run 13 (copy 4) (2026-10-20 18:13)".

v0

2 weeks ago

B Test 2: Run 13 (copy 4) — Fire pathways

Built 2 weeks 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 "B Test 2: Run 13 (copy 4) (2026-10-20 18:13)".

v0

2 weeks ago

B Test 2: Run 13 (copy 4) — Perimeters by time

Built 2 weeks 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 "B Test 2: Run 13 (copy 4) (2026-10-20 18:13)".

v1

2 weeks ago

B Test 2: Run 13 (copy 4) — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Run 13 (copy 4) (2026-10-20 18:13)".

v0

2 weeks ago

B Test 2: Run 13 (copy 4) — Spot landings

Built 2 weeks 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 "B Test 2: Run 13 (copy 4) (2026-10-20 18:13)".

v0

2 weeks ago

B Test 2: Run 13 (copy 4) — Spotting

Built 2 weeks 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 "B Test 2: Run 13 (copy 4) (2026-10-20 18:13)".

v0

2 weeks ago

B Test 2: Run 13 (copy) (2026-10-20 17:22)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Run 13 (copy) — Assets reached

Built 2 weeks 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 "B Test 2: Run 13 (copy) (2026-10-20 17:22)".

v1

2 weeks ago

B Test 2: Run 13 (copy) — Burning edge by time

Built 2 weeks 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 "B Test 2: Run 13 (copy) (2026-10-20 17:22)".

v0

2 weeks ago

B Test 2: Run 13 (copy) — Fire pathways

Built 2 weeks 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 "B Test 2: Run 13 (copy) (2026-10-20 17:22)".

v0

2 weeks ago

B Test 2: Run 13 (copy) — Perimeters by time

Built 2 weeks 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 "B Test 2: Run 13 (copy) (2026-10-20 17:22)".

v1

2 weeks ago

B Test 2: Run 13 (copy) — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Run 13 (copy) (2026-10-20 17:22)".

v0

2 weeks ago

B Test 2: Run 13 (copy) — Spot landings

Built 2 weeks 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 "B Test 2: Run 13 (copy) (2026-10-20 17:22)".

v0

2 weeks ago

B Test 2: Run 13 (copy) — Spotting

Built 2 weeks 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 "B Test 2: Run 13 (copy) (2026-10-20 17:22)".

v0

2 weeks ago

B Test 2: Run 13 No Treatment (2026-10-20 17:57)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Run 13 No Treatment — Assets reached

Built 2 weeks 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 "B Test 2: Run 13 No Treatment (2026-10-20 17:57)".

v1

2 weeks ago

B Test 2: Run 13 No Treatment — Burning edge by time

Built 2 weeks 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 "B Test 2: Run 13 No Treatment (2026-10-20 17:57)".

v0

2 weeks ago

B Test 2: Run 13 No Treatment — Fire pathways

Built 2 weeks 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 "B Test 2: Run 13 No Treatment (2026-10-20 17:57)".

v0

2 weeks ago

B Test 2: Run 13 No Treatment — Perimeters by time

Built 2 weeks 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 "B Test 2: Run 13 No Treatment (2026-10-20 17:57)".

v1

2 weeks ago

B Test 2: Run 13 No Treatment — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Run 13 No Treatment (2026-10-20 17:57)".

v0

2 weeks ago

B Test 2: Run 13 No Treatment — Spot landings

Built 2 weeks 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 "B Test 2: Run 13 No Treatment (2026-10-20 17:57)".

v0

2 weeks ago

B Test 2: Run 13 No Treatment — Spotting

Built 2 weeks 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 "B Test 2: Run 13 No Treatment (2026-10-20 17:57)".

v0

2 weeks ago

B Test 2: Run 13 — Assets reached

Built 2 weeks 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 "B Test 2: Run 13 (2026-10-20 17:13)".

v1

2 weeks ago

B Test 2: Run 13 — Burning edge by time

Built 2 weeks 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 "B Test 2: Run 13 (2026-10-20 17:13)".

v0

2 weeks ago

B Test 2: Run 13 — Fire pathways

Built 2 weeks 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 "B Test 2: Run 13 (2026-10-20 17:13)".

v0

2 weeks ago

B Test 2: Run 13 — Perimeters by time

Built 2 weeks 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 "B Test 2: Run 13 (2026-10-20 17:13)".

v1

2 weeks ago

B Test 2: Run 13 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Run 13 (2026-10-20 17:13)".

v0

2 weeks ago

B Test 2: Run 13 — Spot landings

Built 2 weeks 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 "B Test 2: Run 13 (2026-10-20 17:13)".

v0

2 weeks ago

B Test 2: Run 13 — Spotting

Built 2 weeks 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 "B Test 2: Run 13 (2026-10-20 17:13)".

v0

2 weeks ago

B Test 2: Run 18 (2026-10-20 20:28)

Needs upload

Fire run for the simulation "B Test 2", from Simulations.

2 weeks ago

B Test 2: Run 18 (2026-10-20 20:30)

Needs upload

Fire run for the simulation "B Test 2", from Simulations.

2 weeks ago

B Test 2: Run 18 (2026-10-20 20:36)

Needs upload

Fire run for the simulation "B Test 2", from Simulations.

2 weeks ago

B Test 2: Run 18 (2026-10-20 21:23)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Run 18 (copy) (2026-10-20 21:33)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Run 18 (copy) — Assets reached

Built 2 weeks 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 "B Test 2: Run 18 (copy) (2026-10-20 21:33)".

v0

2 weeks ago

B Test 2: Run 18 (copy) — Burning edge by time

Built 2 weeks 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 "B Test 2: Run 18 (copy) (2026-10-20 21:33)".

v0

2 weeks ago

B Test 2: Run 18 (copy) — Debris flows (projected)

Built 2 weeks ago

Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "B Test 2: Run 18 (copy) (2026-10-20 21:33)".

v0

2 weeks ago

B Test 2: Run 18 (copy) — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "B Test 2: Run 18 (copy) (2026-10-20 21:33)".

v0

2 weeks ago

B Test 2: Run 18 (copy) — Fire pathways

Built 2 weeks 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 "B Test 2: Run 18 (copy) (2026-10-20 21:33)".

v0

2 weeks ago

B Test 2: Run 18 (copy) — Perimeters by time

Built 2 weeks 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 "B Test 2: Run 18 (copy) (2026-10-20 21:33)".

v0

2 weeks ago

B Test 2: Run 18 (copy) — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Run 18 (copy) (2026-10-20 21:33)".

v0

2 weeks ago

B Test 2: Run 18 (copy) — Spot landings

Built 2 weeks 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 "B Test 2: Run 18 (copy) (2026-10-20 21:33)".

v0

2 weeks ago

B Test 2: Run 18 (copy) — Spotting

Built 2 weeks 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 "B Test 2: Run 18 (copy) (2026-10-20 21:33)".

v0

2 weeks ago

B Test 2: Run 18 — Assets reached

Built 2 weeks 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 "B Test 2: Run 18 (2026-10-20 21:23)".

v0

2 weeks ago

B Test 2: Run 18 — Burning edge by time

Built 2 weeks 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 "B Test 2: Run 18 (2026-10-20 21:23)".

v0

2 weeks ago

B Test 2: Run 18 — Debris flows (projected)

Built 2 weeks ago

Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "B Test 2: Run 18 (2026-10-20 21:23)".

v0

2 weeks ago

B Test 2: Run 18 — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "B Test 2: Run 18 (2026-10-20 21:23)".

v0

2 weeks ago

B Test 2: Run 18 — Fire pathways

Built 2 weeks 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 "B Test 2: Run 18 (2026-10-20 21:23)".

v0

2 weeks ago

B Test 2: Run 18 — Perimeters by time

Built 2 weeks 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 "B Test 2: Run 18 (2026-10-20 21:23)".

v0

2 weeks ago

B Test 2: Run 18 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Run 18 (2026-10-20 21:23)".

v0

2 weeks ago

B Test 2: Run 18 — Spot landings

Built 2 weeks 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 "B Test 2: Run 18 (2026-10-20 21:23)".

v0

2 weeks ago

B Test 2: Run 18 — Spotting

Built 2 weeks 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 "B Test 2: Run 18 (2026-10-20 21:23)".

v0

2 weeks ago

B Test 2: Run 2 (2026-10-19 17:51)

Needs upload

Fire run for the simulation "B Test 2", from Simulations.

2 weeks ago

B Test 2: Run 3 (2026-10-19 19:10)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Run 3 — Burning edge by time

Built 2 weeks 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 "B Test 2: Run 3 (2026-10-19 19:10)".

v0

2 weeks ago

B Test 2: Run 3 — Fire pathways

Built 2 weeks ago

The routes the fire took, traced back from its edge along its arrival time. `use` counts the traced paths through a piece: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "B Test 2: Run 3 (2026-10-19 19:10)".

v0

2 weeks ago

B Test 2: Run 3 — Perimeters by time

Built 2 weeks 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 "B Test 2: Run 3 (2026-10-19 19:10)".

v0

2 weeks ago

B Test 2: Run 3 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Run 3 (2026-10-19 19:10)".

v0

2 weeks ago

B Test 2: Run 3 — Spot landings

Built 2 weeks 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 "B Test 2: Run 3 (2026-10-19 19:10)".

v0

2 weeks ago

B Test 2: Run 3 — Spotting

Built 2 weeks 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 "B Test 2: Run 3 (2026-10-19 19:10)".

v0

2 weeks ago

B Test 2: Run 4 (2026-10-19 19:32)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Run 4 — Burning edge by time

Built 2 weeks 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 "B Test 2: Run 4 (2026-10-19 19:32)".

v0

2 weeks ago

B Test 2: Run 4 — Fire pathways

Built 2 weeks ago

The routes the fire took, traced back from its edge along its arrival time. `use` counts the traced paths through a piece: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "B Test 2: Run 4 (2026-10-19 19:32)".

v0

2 weeks ago

B Test 2: Run 4 — Perimeters by time

Built 2 weeks 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 "B Test 2: Run 4 (2026-10-19 19:32)".

v0

2 weeks ago

B Test 2: Run 4 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Run 4 (2026-10-19 19:32)".

v0

2 weeks ago

B Test 2: Run 4 — Spot landings

Built 2 weeks 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 "B Test 2: Run 4 (2026-10-19 19:32)".

v0

2 weeks ago

B Test 2: Run 4 — Spotting

Built 2 weeks 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 "B Test 2: Run 4 (2026-10-19 19:32)".

v0

2 weeks ago

B Test 2: Run 5 (2026-10-19 19:42)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Run 5 — Burning edge by time

Built 2 weeks 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 "B Test 2: Run 5 (2026-10-19 19:42)".

v0

2 weeks ago

B Test 2: Run 5 — Fire pathways

Built 2 weeks ago

The routes the fire took, traced back from its edge along its arrival time. `use` counts the traced paths through a piece: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "B Test 2: Run 5 (2026-10-19 19:42)".

v0

2 weeks ago

B Test 2: Run 5 — Perimeters by time

Built 2 weeks 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 "B Test 2: Run 5 (2026-10-19 19:42)".

v0

2 weeks ago

B Test 2: Run 5 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Run 5 (2026-10-19 19:42)".

v0

2 weeks ago

B Test 2: Run 5 — Spot landings

Built 2 weeks 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 "B Test 2: Run 5 (2026-10-19 19:42)".

v0

2 weeks ago

B Test 2: Run 5 — Spotting

Built 2 weeks 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 "B Test 2: Run 5 (2026-10-19 19:42)".

v0

2 weeks ago

B Test 2: Run 6 (2026-10-19 19:49)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Run 6 (copy) (2026-10-20 15:40)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Run 6 (copy) — Burning edge by time

Built 2 weeks 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 "B Test 2: Run 6 (copy) (2026-10-20 15:40)".

v0

2 weeks ago

B Test 2: Run 6 (copy) — Debris flows (projected)

Built 2 weeks ago

Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "B Test 2: Run 6 (copy) (2026-10-20 15:40)".

v0

2 weeks ago

B Test 2: Run 6 (copy) — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "B Test 2: Run 6 (copy) (2026-10-20 15:40)".

v0

2 weeks ago

B Test 2: Run 6 (copy) — Fire pathways

Built 2 weeks 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 "B Test 2: Run 6 (copy) (2026-10-20 15:40)".

v0

2 weeks ago

B Test 2: Run 6 (copy) — Perimeters by time

Built 2 weeks 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 "B Test 2: Run 6 (copy) (2026-10-20 15:40)".

v0

2 weeks ago

B Test 2: Run 6 (copy) — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Run 6 (copy) (2026-10-20 15:40)".

v0

2 weeks ago

B Test 2: Run 6 (copy) — Spot landings

Built 2 weeks 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 "B Test 2: Run 6 (copy) (2026-10-20 15:40)".

v0

2 weeks ago

B Test 2: Run 6 (copy) — Spotting

Built 2 weeks 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 "B Test 2: Run 6 (copy) (2026-10-20 15:40)".

v0

2 weeks ago

B Test 2: Run 6 — Burning edge by time

Built 2 weeks 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 "B Test 2: Run 6 (2026-10-19 19:49)".

v0

2 weeks ago

B Test 2: Run 6 — Debris flows (projected)

Built 2 weeks ago

Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "B Test 2: Run 6 (2026-10-19 19:49)".

v0

2 weeks ago

B Test 2: Run 6 — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "B Test 2: Run 6 (2026-10-19 19:49)".

v0

2 weeks ago

B Test 2: Run 6 — Fire pathways

Built 2 weeks ago

The routes the fire took, traced back from its edge along its arrival time. `use` counts the traced paths through a piece: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "B Test 2: Run 6 (2026-10-19 19:49)".

v0

2 weeks ago

B Test 2: Run 6 — Perimeters by time

Built 2 weeks 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 "B Test 2: Run 6 (2026-10-19 19:49)".

v0

2 weeks ago

B Test 2: Run 6 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Run 6 (2026-10-19 19:49)".

v0

2 weeks ago

B Test 2: Run 6 — Spot landings

Built 2 weeks 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 "B Test 2: Run 6 (2026-10-19 19:49)".

v0

2 weeks ago

B Test 2: Run 6 — Spotting

Built 2 weeks 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 "B Test 2: Run 6 (2026-10-19 19:49)".

v0

2 weeks ago

B Test 2: Run 7 (2026-10-20 15:25)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Run 7 — Burning edge by time

Built 2 weeks 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 "B Test 2: Run 7 (2026-10-20 15:25)".

v0

2 weeks ago

B Test 2: Run 7 — Fire pathways

Built 2 weeks 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 "B Test 2: Run 7 (2026-10-20 15:25)".

v0

2 weeks ago

B Test 2: Run 7 — Perimeters by time

Built 2 weeks 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 "B Test 2: Run 7 (2026-10-20 15:25)".

v0

2 weeks ago

B Test 2: Run 7 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Run 7 (2026-10-20 15:25)".

v0

2 weeks ago

B Test 2: Run 7 — Spot landings

Built 2 weeks 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 "B Test 2: Run 7 (2026-10-20 15:25)".

v0

2 weeks ago

B Test 2: Run 7 — Spotting

Built 2 weeks 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 "B Test 2: Run 7 (2026-10-20 15:25)".

v0

2 weeks ago

B Test 2: Run 9 (2026-10-20 15:34)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Run 9 — Burning edge by time

Built 2 weeks 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 "B Test 2: Run 9 (2026-10-20 15:34)".

v0

2 weeks ago

B Test 2: Run 9 — Debris flows (projected)

Built 2 weeks ago

Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "B Test 2: Run 9 (2026-10-20 15:34)".

v0

2 weeks ago

B Test 2: Run 9 — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "B Test 2: Run 9 (2026-10-20 15:34)".

v0

2 weeks ago

B Test 2: Run 9 — Fire pathways

Built 2 weeks 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 "B Test 2: Run 9 (2026-10-20 15:34)".

v0

2 weeks ago

B Test 2: Run 9 — Perimeters by time

Built 2 weeks 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 "B Test 2: Run 9 (2026-10-20 15:34)".

v0

2 weeks ago

B Test 2: Run 9 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Run 9 (2026-10-20 15:34)".

v0

2 weeks ago

B Test 2: Run 9 — Spot landings

Built 2 weeks 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 "B Test 2: Run 9 (2026-10-20 15:34)".

v0

2 weeks ago

B Test 2: Run 9 — Spotting

Built 2 weeks 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 "B Test 2: Run 9 (2026-10-20 15:34)".

v0

2 weeks ago

B Test 2: Thinning Treatment (2026-10-20 18:41)

Built 2 weeks ago

Fire run for the simulation "B Test 2", from Simulations.

v0

2 weeks ago

B Test 2: Thinning Treatment — Burning edge by time

Built 2 weeks 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 "B Test 2: Thinning Treatment (2026-10-20 18:41)".

v0

2 weeks ago

B Test 2: Thinning Treatment — Fire pathways

Built 2 weeks 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 "B Test 2: Thinning Treatment (2026-10-20 18:41)".

v0

2 weeks ago

B Test 2: Thinning Treatment — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "B Test 2: Thinning Treatment (2026-10-20 18:41)".

v0

2 weeks ago

B Test 2: Thinning Treatment — Spot landings

Built 2 weeks 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 "B Test 2: Thinning Treatment (2026-10-20 18:41)".

v0

2 weeks ago

B Test 2: Thinning Treatment — Spotting

Built 2 weeks 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 "B Test 2: Thinning Treatment (2026-10-20 18:41)".

v0

2 weeks ago

Carr Canyon: Run 1 (2026-10-20 18:18)

Built 2 weeks ago

Fire run for the simulation "Carr Canyon", from Simulations.

v0

2 weeks ago

Carr Canyon: Run 1 — Assets reached

Built 2 weeks 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 "Carr Canyon: Run 1 (2026-10-20 18:18)".

v0

2 weeks ago

Carr Canyon: Run 1 — Burning edge by time

Built 2 weeks 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 "Carr Canyon: Run 1 (2026-10-20 18:18)".

v0

2 weeks ago

Carr Canyon: Run 1 — Fire pathways

Built 2 weeks 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 "Carr Canyon: Run 1 (2026-10-20 18:18)".

v0

2 weeks ago

Carr Canyon: Run 1 — Perimeters by time

Built 2 weeks 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 "Carr Canyon: Run 1 (2026-10-20 18:18)".

v0

2 weeks ago

Carr Canyon: Run 1 — Roads cut off

Built 2 weeks 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 "Carr Canyon: Run 1 (2026-10-20 18:18)".

v0

2 weeks ago

Carr Canyon: Run 1 — Roads reached

Built 2 weeks 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 "Carr Canyon: Run 1 (2026-10-20 18:18)".

v0

2 weeks ago

Carr Canyon: Run 1 — Spot landings

Built 2 weeks 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 "Carr Canyon: Run 1 (2026-10-20 18:18)".

v0

2 weeks ago

Carr Canyon: Run 1 — Spotting

Built 2 weeks 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 "Carr Canyon: Run 1 (2026-10-20 18:18)".

v0

2 weeks ago

Carr Canyon: Run 2 (2026-10-20 18:19)

Built 2 weeks ago

Fire run for the simulation "Carr Canyon", from Simulations.

v0

2 weeks ago

Carr Canyon: Run 2 (2026-10-20 20:54)

Built 2 weeks ago

Fire run for the simulation "Carr Canyon", from Simulations.

v0

2 weeks ago

Carr Canyon: Run 2 — Assets reached

Built 2 weeks 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 "Carr Canyon: Run 2 (2026-10-20 18:19)".

v0

2 weeks ago

Carr Canyon: Run 2 — Assets reached

Built 2 weeks 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 "Carr Canyon: Run 2 (2026-10-20 20:54)".

v0

2 weeks ago

Carr Canyon: Run 2 — Burning edge by time

Built 2 weeks 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 "Carr Canyon: Run 2 (2026-10-20 18:19)".

v0

2 weeks ago

Carr Canyon: Run 2 — Burning edge by time

Built 2 weeks 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 "Carr Canyon: Run 2 (2026-10-20 20:54)".

v0

2 weeks ago

Carr Canyon: Run 2 — Fire pathways

Built 2 weeks 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 "Carr Canyon: Run 2 (2026-10-20 20:54)".

v0

2 weeks ago

Carr Canyon: Run 2 — Fire pathways

Built 2 weeks 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 "Carr Canyon: Run 2 (2026-10-20 18:19)".

v0

2 weeks ago

Carr Canyon: Run 2 — Perimeters by time

Built 2 weeks 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 "Carr Canyon: Run 2 (2026-10-20 20:54)".

v0

2 weeks ago

Carr Canyon: Run 2 — Perimeters by time

Built 2 weeks 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 "Carr Canyon: Run 2 (2026-10-20 18:19)".

v0

2 weeks ago

Carr Canyon: Run 2 — Roads cut off

Built 2 weeks 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 "Carr Canyon: Run 2 (2026-10-20 20:54)".

v0

2 weeks ago

Carr Canyon: Run 2 — Roads cut off

Built 2 weeks 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 "Carr Canyon: Run 2 (2026-10-20 18:19)".

v0

2 weeks ago

Carr Canyon: Run 2 — Roads reached

Built 2 weeks 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 "Carr Canyon: Run 2 (2026-10-20 18:19)".

v0

2 weeks ago

Carr Canyon: Run 2 — Roads reached

Built 2 weeks 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 "Carr Canyon: Run 2 (2026-10-20 20:54)".

v0

2 weeks ago

Carr Canyon: Run 2 — Spot landings

Built 2 weeks 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 "Carr Canyon: Run 2 (2026-10-20 18:19)".

v0

2 weeks ago

Carr Canyon: Run 2 — Spot landings

Built 2 weeks 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 "Carr Canyon: Run 2 (2026-10-20 20:54)".

v0

2 weeks ago

Carr Canyon: Run 2 — Spotting

Built 2 weeks 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 "Carr Canyon: Run 2 (2026-10-20 20:54)".

v0

2 weeks ago

Carr Canyon: Run 2 — Spotting

Built 2 weeks 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 "Carr Canyon: Run 2 (2026-10-20 18:19)".

v0

2 weeks ago

Carr Canyon: Run 3 (2026-10-20 18:29)

Built 2 weeks ago

Fire run for the simulation "Carr Canyon", from Simulations.

v0

2 weeks ago

Carr Canyon: Run 3 — Assets reached

Built 2 weeks 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 "Carr Canyon: Run 3 (2026-10-20 18:29)".

v0

2 weeks ago

Carr Canyon: Run 3 — Burning edge by time

Built 2 weeks 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 "Carr Canyon: Run 3 (2026-10-20 18:29)".

v0

2 weeks ago

Carr Canyon: Run 3 — Fire pathways

Built 2 weeks 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 "Carr Canyon: Run 3 (2026-10-20 18:29)".

v0

2 weeks ago

Carr Canyon: Run 3 — Perimeters by time

Built 2 weeks 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 "Carr Canyon: Run 3 (2026-10-20 18:29)".

v0

2 weeks ago

Carr Canyon: Run 3 — Roads cut off

Built 2 weeks 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 "Carr Canyon: Run 3 (2026-10-20 18:29)".

v0

2 weeks ago

Carr Canyon: Run 3 — Roads reached

Built 2 weeks 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 "Carr Canyon: Run 3 (2026-10-20 18:29)".

v0

2 weeks ago

Carr Canyon: Run 3 — Spot landings

Built 2 weeks 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 "Carr Canyon: Run 3 (2026-10-20 18:29)".

v0

2 weeks ago

Carr Canyon: Run 3 — Spotting

Built 2 weeks 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 "Carr Canyon: Run 3 (2026-10-20 18:29)".

v0

2 weeks ago

Cochise Weather CARR 20250614 - 20250620.wxs

v0

4 months ago

Cochise Weather HEADQUARTERS 20250615-20250621.wxs

v0

4 months ago

COCHISE-CARR-21411-weatherHourly-02-03-2006-02-17-2026.fw21

v0

8 months ago

COCHISE_HEADQUARTERS_weatherHourly-06-25-2006-07-09-2026.fw21

v0

4 months ago

CochiseCountyBurnProbability97.zip

v0

8 months ago

CochiseLCPwithAddition-60m-Auto97th.zip

v0

8 months ago

CochiseLCPwithAddition.zip

v0

8 months ago

Douglas: Farsite (2026-10-21 21:44)

Built 2 weeks ago

Fire run for the simulation "Douglas", from Simulations.

v0

2 weeks ago

Douglas: Farsite with Treatment (2026-10-21 21:45)

Built 2 weeks ago

Fire run for the simulation "Douglas", from Simulations.

v0

2 weeks ago

Douglas: Farsite with Treatment — Assets reached

Built 2 weeks 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 "Douglas: Farsite with Treatment (2026-10-21 21:45)".

v0

2 weeks ago

Douglas: Farsite with Treatment — Burning edge by time

Built 2 weeks 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 "Douglas: Farsite with Treatment (2026-10-21 21:45)".

v0

2 weeks ago

Douglas: Farsite with Treatment — Debris flows (projected)

Built 2 weeks ago

Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "Douglas: Farsite with Treatment (2026-10-21 21:45)".

v0

2 weeks ago

Douglas: Farsite with Treatment — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Douglas: Farsite with Treatment (2026-10-21 21:45)".

v0

2 weeks ago

Douglas: Farsite with Treatment — Fire pathways

Built 2 weeks 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 "Douglas: Farsite with Treatment (2026-10-21 21:45)".

v0

2 weeks ago

Douglas: Farsite with Treatment — Perimeters by time

Built 2 weeks 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 "Douglas: Farsite with Treatment (2026-10-21 21:45)".

v0

2 weeks ago

Douglas: Farsite with Treatment — Roads reached

Built 2 weeks 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 "Douglas: Farsite with Treatment (2026-10-21 21:45)".

v0

2 weeks ago

Douglas: Farsite with Treatment — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Douglas: Farsite with Treatment (2026-10-21 21:45)".

v0

2 weeks ago

Douglas: Farsite with Treatment — Spot landings

Built 2 weeks 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 "Douglas: Farsite with Treatment (2026-10-21 21:45)".

v0

2 weeks ago

Douglas: Farsite with Treatment — Spotting

Built 2 weeks 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 "Douglas: Farsite with Treatment (2026-10-21 21:45)".

v0

2 weeks ago

Douglas: Farsite — Assets reached

Built 2 weeks 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 "Douglas: Farsite (2026-10-21 21:44)".

v0

2 weeks ago

Douglas: Farsite — Burning edge by time

Built 2 weeks 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 "Douglas: Farsite (2026-10-21 21:44)".

v0

2 weeks ago

Douglas: Farsite — Debris flows (projected)

Built 2 weeks ago

Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "Douglas: Farsite (2026-10-21 21:44)".

v0

2 weeks ago

Douglas: Farsite — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Douglas: Farsite (2026-10-21 21:44)".

v0

2 weeks ago

Douglas: Farsite — Fire pathways

Built 2 weeks 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 "Douglas: Farsite (2026-10-21 21:44)".

v0

2 weeks ago

Douglas: Farsite — Perimeters by time

Built 2 weeks 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 "Douglas: Farsite (2026-10-21 21:44)".

v0

2 weeks ago

Douglas: Farsite — Roads cut off

Built 2 weeks 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 "Douglas: Farsite (2026-10-21 21:44)".

v0

2 weeks ago

Douglas: Farsite — Roads reached

Built 2 weeks 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 "Douglas: Farsite (2026-10-21 21:44)".

v0

2 weeks ago

Douglas: Farsite — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Douglas: Farsite (2026-10-21 21:44)".

v0

2 weeks ago

Douglas: Farsite — Spot landings

Built 2 weeks 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 "Douglas: Farsite (2026-10-21 21:44)".

v0

2 weeks ago

Douglas: Farsite — Spotting

Built 2 weeks 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 "Douglas: Farsite (2026-10-21 21:44)".

v0

2 weeks ago

Hunter Canyon: MM Test Run 1 (2026-10-29 18:18)

Built 4 days ago

Fire run for the simulation "Hunter Canyon", from Simulations.

v0

4 days ago

Hunter Canyon: MM Test Run 1 — Assets reached

Built 4 days 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 "Hunter Canyon: MM Test Run 1 (2026-10-29 18:18)".

v0

4 days ago

Hunter Canyon: MM Test Run 1 — Burning edge by time

Built 4 days 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 "Hunter Canyon: MM Test Run 1 (2026-10-29 18:18)".

v0

4 days ago

Hunter Canyon: MM Test Run 1 — Damage per structure (estimate)

Built 4 days 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 "Hunter Canyon: MM Test Run 1 (2026-10-29 18:18)".

v0

4 days ago

Hunter Canyon: MM Test Run 1 — Engine routes

Built 4 days 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 "Hunter Canyon: MM Test Run 1 (2026-10-29 18:18)".

v0

4 days ago

Hunter Canyon: MM Test Run 1 — Fire pathways

Built 4 days 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 "Hunter Canyon: MM Test Run 1 (2026-10-29 18:18)".

v0

4 days ago

Hunter Canyon: MM Test Run 1 — Perimeters by time

Built 4 days 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 "Hunter Canyon: MM Test Run 1 (2026-10-29 18:18)".

v0

4 days ago

Hunter Canyon: MM Test Run 1 — Roads cut off

Built 4 days 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 "Hunter Canyon: MM Test Run 1 (2026-10-29 18:18)".

v0

4 days ago

Hunter Canyon: MM Test Run 1 — Roads reached

Built 4 days 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 "Hunter Canyon: MM Test Run 1 (2026-10-29 18:18)".

v0

4 days ago

Hunter Canyon: MM Test Run 1 — Spot landings

Built 4 days 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 "Hunter Canyon: MM Test Run 1 (2026-10-29 18:18)".

v0

4 days ago

Hunter Canyon: MM Test Run 1 — Spotting

Built 4 days 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 "Hunter Canyon: MM Test Run 1 (2026-10-29 18:18)".

v0

4 days ago

Hunter Canyon: MM Test Run 1 — Treatment edges, held or breached

Built 4 days ago

Each treatment's edge where the fire reached it: `status` held (the fire came within a cell and stopped) or breached (it burned across, on both sides of the edge), `treatment` its index in the run and `name`, `minutes` when the fire first came near. Worked out in DuckDB from the run's burned area. Written by each run of the fire simulation whose output file is "Hunter Canyon: MM Test Run 1 (2026-10-29 18:18)".

v0

4 days ago

Hunter Canyon: MTT Run 1 (2026-10-29 17:26)

Built 4 days ago

Fire run for the simulation "Hunter Canyon", from Simulations.

v0

4 days ago

Hunter Canyon: MTT Run 1 — Assets reached

Built 4 days 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 "Hunter Canyon: MTT Run 1 (2026-10-29 17:26)".

v0

4 days ago

Hunter Canyon: MTT Run 1 — Burning edge by time

Built 4 days 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 "Hunter Canyon: MTT Run 1 (2026-10-29 17:26)".

v0

4 days ago

Hunter Canyon: MTT Run 1 — Damage per structure (estimate)

Built 4 days 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 "Hunter Canyon: MTT Run 1 (2026-10-29 17:26)".

v0

4 days ago

Hunter Canyon: MTT Run 1 — Engine routes

Built 4 days 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 "Hunter Canyon: MTT Run 1 (2026-10-29 17:26)".

v0

4 days ago

Hunter Canyon: MTT Run 1 — Fire pathways

Built 4 days 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 "Hunter Canyon: MTT Run 1 (2026-10-29 17:26)".

v0

4 days ago

Hunter Canyon: MTT Run 1 — Perimeters by time

Built 4 days 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 "Hunter Canyon: MTT Run 1 (2026-10-29 17:26)".

v0

4 days ago

Hunter Canyon: MTT Run 1 — Roads cut off

Built 4 days 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 "Hunter Canyon: MTT Run 1 (2026-10-29 17:26)".

v0

4 days ago

Hunter Canyon: MTT Run 1 — Roads reached

Built 4 days 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 "Hunter Canyon: MTT Run 1 (2026-10-29 17:26)".

v0

4 days ago

Hunter Canyon: MTT Run 1 — Spot landings

Built 4 days 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 "Hunter Canyon: MTT Run 1 (2026-10-29 17:26)".

v0

4 days ago

Hunter Canyon: MTT Run 1 — Spotting

Built 4 days 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 "Hunter Canyon: MTT Run 1 (2026-10-29 17:26)".

v0

4 days ago

Hunter Canyon: MTT Run with Treatments (2026-10-29 17:27)

Built 4 days ago

Fire run for the simulation "Hunter Canyon", from Simulations.

v0

4 days ago

Hunter Canyon: MTT Run with Treatments — Assets reached

Built 4 days 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 "Hunter Canyon: MTT Run with Treatments (2026-10-29 17:27)".

v0

4 days ago

Hunter Canyon: MTT Run with Treatments — Burning edge by time

Built 4 days 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 "Hunter Canyon: MTT Run with Treatments (2026-10-29 17:27)".

v0

4 days ago

Hunter Canyon: MTT Run with Treatments — Damage per structure (estimate)

Built 4 days 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 "Hunter Canyon: MTT Run with Treatments (2026-10-29 17:27)".

v0

4 days ago

Hunter Canyon: MTT Run with Treatments — Engine routes

Built 4 days 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 "Hunter Canyon: MTT Run with Treatments (2026-10-29 17:27)".

v0

4 days ago

Hunter Canyon: MTT Run with Treatments — Fire pathways

Built 4 days 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 "Hunter Canyon: MTT Run with Treatments (2026-10-29 17:27)".

v0

4 days ago

Hunter Canyon: MTT Run with Treatments — Perimeters by time

Built 4 days 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 "Hunter Canyon: MTT Run with Treatments (2026-10-29 17:27)".

v0

4 days ago

Hunter Canyon: MTT Run with Treatments — Roads cut off

Built 4 days 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 "Hunter Canyon: MTT Run with Treatments (2026-10-29 17:27)".

v0

4 days ago

Hunter Canyon: MTT Run with Treatments — Roads reached

Built 4 days 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 "Hunter Canyon: MTT Run with Treatments (2026-10-29 17:27)".

v0

4 days ago

Hunter Canyon: MTT Run with Treatments — Spot landings

Built 4 days 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 "Hunter Canyon: MTT Run with Treatments (2026-10-29 17:27)".

v0

4 days ago

Hunter Canyon: MTT Run with Treatments — Spotting

Built 4 days 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 "Hunter Canyon: MTT Run with Treatments (2026-10-29 17:27)".

v0

4 days ago

Hunter Canyon: MTT Run with Treatments — Treatment edges, held or breached

Built 4 days ago

Each treatment's edge where the fire reached it: `status` held (the fire came within a cell and stopped) or breached (it burned across, on both sides of the edge), `treatment` its index in the run and `name`, `minutes` when the fire first came near. Worked out in DuckDB from the run's burned area. Written by each run of the fire simulation whose output file is "Hunter Canyon: MTT Run with Treatments (2026-10-29 17:27)".

v0

4 days ago

Hunter Canyon: Run 1 (2026-10-20 17:18)

Built 2 weeks ago

Fire run for the simulation "Hunter Canyon", from Simulations.

v0

2 weeks ago

Hunter Canyon: Run 1 — Assets reached

Built 2 weeks 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 "Hunter Canyon: Run 1 (2026-10-20 17:18)".

v0

2 weeks ago

Hunter Canyon: Run 1 — Burning edge by time

Built 2 weeks 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 "Hunter Canyon: Run 1 (2026-10-20 17:18)".

v0

2 weeks ago

Hunter Canyon: Run 1 — Fire pathways

Built 2 weeks 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 "Hunter Canyon: Run 1 (2026-10-20 17:18)".

v0

2 weeks ago

Hunter Canyon: Run 1 — Perimeters by time

Built 2 weeks 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 "Hunter Canyon: Run 1 (2026-10-20 17:18)".

v0

2 weeks ago

Hunter Canyon: Run 1 — Roads cut off

Built 2 weeks 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 "Hunter Canyon: Run 1 (2026-10-20 17:18)".

v0

2 weeks ago

Hunter Canyon: Run 1 — Roads reached

Built 2 weeks 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 "Hunter Canyon: Run 1 (2026-10-20 17:18)".

v0

2 weeks ago

Hunter Canyon: Run 1 — Spot landings

Built 2 weeks 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 "Hunter Canyon: Run 1 (2026-10-20 17:18)".

v0

2 weeks ago

Hunter Canyon: Run 1 — Spotting

Built 2 weeks 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 "Hunter Canyon: Run 1 (2026-10-20 17:18)".

v0

2 weeks ago

Hunter Canyon: Run 2 (2026-10-20 20:07)

Needs upload

Fire run for the simulation "Hunter Canyon", from Simulations.

2 weeks ago

Hunter Canyon: Run 2 (2026-10-20 20:36)

Needs upload

Fire run for the simulation "Hunter Canyon", from Simulations.

2 weeks ago

Hunter Canyon: Run 2 (2026-10-20 20:50)

Built 2 weeks ago

Fire run for the simulation "Hunter Canyon", from Simulations.

v0

2 weeks ago

Hunter Canyon: Run 2 — Assets reached

Built 2 weeks 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 "Hunter Canyon: Run 2 (2026-10-20 20:50)".

v0

2 weeks ago

Hunter Canyon: Run 2 — Burning edge by time

Built 2 weeks 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 "Hunter Canyon: Run 2 (2026-10-20 20:50)".

v0

2 weeks ago

Hunter Canyon: Run 2 — Fire pathways

Built 2 weeks 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 "Hunter Canyon: Run 2 (2026-10-20 20:50)".

v0

2 weeks ago

Hunter Canyon: Run 2 — Perimeters by time

Built 2 weeks 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 "Hunter Canyon: Run 2 (2026-10-20 20:50)".

v0

2 weeks ago

Hunter Canyon: Run 2 — Roads cut off

Built 2 weeks 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 "Hunter Canyon: Run 2 (2026-10-20 20:50)".

v0

2 weeks ago

Hunter Canyon: Run 2 — Roads reached

Built 2 weeks 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 "Hunter Canyon: Run 2 (2026-10-20 20:50)".

v0

2 weeks ago

Hunter Canyon: Run 2 — Spot landings

Built 2 weeks 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 "Hunter Canyon: Run 2 (2026-10-20 20:50)".

v0

2 weeks ago

Hunter Canyon: Run 2 — Spotting

Built 2 weeks 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 "Hunter Canyon: Run 2 (2026-10-20 20:50)".

v0

2 weeks ago

Hunter Canyon: Run 3 (2026-10-20 20:17)

Needs upload

Fire run for the simulation "Hunter Canyon", from Simulations.

2 weeks ago

Hunter Canyon: Run 3 (2026-10-20 21:41)

Built 2 weeks ago

Fire run for the simulation "Hunter Canyon", from Simulations.

v0

2 weeks ago

Hunter Canyon: Run 3 (2026-10-20 21:50)

Built 2 weeks ago

Fire run for the simulation "Hunter Canyon", from Simulations.

v0

2 weeks ago

Hunter Canyon: Run 3 — Assets reached

Built 2 weeks 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 "Hunter Canyon: Run 3 (2026-10-20 21:41)".

v0

2 weeks ago

Hunter Canyon: Run 3 — Assets reached

Built 2 weeks 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 "Hunter Canyon: Run 3 (2026-10-20 21:50)".

v0

2 weeks ago

Hunter Canyon: Run 3 — Burning edge by time

Built 2 weeks 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 "Hunter Canyon: Run 3 (2026-10-20 21:41)".

v0

2 weeks ago

Hunter Canyon: Run 3 — Burning edge by time

Built 2 weeks 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 "Hunter Canyon: Run 3 (2026-10-20 21:50)".

v0

2 weeks ago

Hunter Canyon: Run 3 — Fire pathways

Built 2 weeks 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 "Hunter Canyon: Run 3 (2026-10-20 21:50)".

v0

2 weeks ago

Hunter Canyon: Run 3 — Fire pathways

Built 2 weeks 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 "Hunter Canyon: Run 3 (2026-10-20 21:41)".

v0

2 weeks ago

Hunter Canyon: Run 3 — Perimeters by time

Built 2 weeks 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 "Hunter Canyon: Run 3 (2026-10-20 21:41)".

v0

2 weeks ago

Hunter Canyon: Run 3 — Perimeters by time

Built 2 weeks 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 "Hunter Canyon: Run 3 (2026-10-20 21:50)".

v0

2 weeks ago

Hunter Canyon: Run 3 — Roads cut off

Built 2 weeks 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 "Hunter Canyon: Run 3 (2026-10-20 21:41)".

v0

2 weeks ago

Hunter Canyon: Run 3 — Roads cut off

Built 2 weeks 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 "Hunter Canyon: Run 3 (2026-10-20 21:50)".

v0

2 weeks ago

Hunter Canyon: Run 3 — Roads reached

Built 2 weeks 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 "Hunter Canyon: Run 3 (2026-10-20 21:41)".

v0

2 weeks ago

Hunter Canyon: Run 3 — Roads reached

Built 2 weeks 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 "Hunter Canyon: Run 3 (2026-10-20 21:50)".

v0

2 weeks ago

Hunter Canyon: Run 3 — Spot landings

Built 2 weeks 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 "Hunter Canyon: Run 3 (2026-10-20 21:50)".

v0

2 weeks ago

Hunter Canyon: Run 3 — Spot landings

Built 2 weeks 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 "Hunter Canyon: Run 3 (2026-10-20 21:41)".

v0

2 weeks ago

Hunter Canyon: Run 3 — Spotting

Built 2 weeks 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 "Hunter Canyon: Run 3 (2026-10-20 21:41)".

v0

2 weeks ago

Hunter Canyon: Run 3 — Spotting

Built 2 weeks 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 "Hunter Canyon: Run 3 (2026-10-20 21:50)".

v0

2 weeks ago

Miller Canyon: Run 1 (2026-10-20 18:26)

Built 2 weeks ago

Fire run for the simulation "Miller Canyon", from Simulations.

v0

2 weeks ago

Miller Canyon: Run 1 (2026-10-20 19:05)

Built 2 weeks ago

Fire run for the simulation "Miller Canyon", from Simulations.

v0

2 weeks ago

Miller Canyon: Run 1 — Assets reached

Built 2 weeks 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 "Miller Canyon: Run 1 (2026-10-20 19:05)".

v0

2 weeks ago

Miller Canyon: Run 1 — Assets reached

Built 2 weeks 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 "Miller Canyon: Run 1 (2026-10-20 18:26)".

v0

2 weeks ago

Miller Canyon: Run 1 — Burning edge by time

Built 2 weeks 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 "Miller Canyon: Run 1 (2026-10-20 18:26)".

v0

2 weeks ago

Miller Canyon: Run 1 — Burning edge by time

Built 2 weeks 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 "Miller Canyon: Run 1 (2026-10-20 19:05)".

v0

2 weeks ago

Miller Canyon: Run 1 — Fire pathways

Built 2 weeks 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 "Miller Canyon: Run 1 (2026-10-20 19:05)".

v0

2 weeks ago

Miller Canyon: Run 1 — Fire pathways

Built 2 weeks 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 "Miller Canyon: Run 1 (2026-10-20 18:26)".

v0

2 weeks ago

Miller Canyon: Run 1 — Perimeters by time

Built 2 weeks 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 "Miller Canyon: Run 1 (2026-10-20 18:26)".

v0

2 weeks ago

Miller Canyon: Run 1 — Perimeters by time

Built 2 weeks 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 "Miller Canyon: Run 1 (2026-10-20 19:05)".

v0

2 weeks ago

Miller Canyon: Run 1 — Roads cut off

Built 2 weeks 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 "Miller Canyon: Run 1 (2026-10-20 18:26)".

v0

2 weeks ago

Miller Canyon: Run 1 — Roads cut off

Built 2 weeks 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 "Miller Canyon: Run 1 (2026-10-20 19:05)".

v0

2 weeks ago

Miller Canyon: Run 1 — Roads reached

Built 2 weeks 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 "Miller Canyon: Run 1 (2026-10-20 19:05)".

v0

2 weeks ago

Miller Canyon: Run 1 — Roads reached

Built 2 weeks 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 "Miller Canyon: Run 1 (2026-10-20 18:26)".

v0

2 weeks ago

Miller Canyon: Run 1 — Spot landings

Built 2 weeks 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 "Miller Canyon: Run 1 (2026-10-20 19:05)".

v0

2 weeks ago

Miller Canyon: Run 1 — Spot landings

Built 2 weeks 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 "Miller Canyon: Run 1 (2026-10-20 18:26)".

v0

2 weeks ago

Miller Canyon: Run 1 — Spotting

Built 2 weeks 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 "Miller Canyon: Run 1 (2026-10-20 18:26)".

v0

2 weeks ago

Miller Canyon: Run 1 — Spotting

Built 2 weeks 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 "Miller Canyon: Run 1 (2026-10-20 19:05)".

v0

2 weeks ago

Miller Canyon: Run 2 (2026-10-20 19:05)

Built 2 weeks ago

Fire run for the simulation "Miller Canyon", from Simulations.

v0

2 weeks ago

Miller Canyon: Run 2 (2026-10-20 20:53)

Built 2 weeks ago

Fire run for the simulation "Miller Canyon", from Simulations.

v0

2 weeks ago

Miller Canyon: Run 2 — Assets reached

Built 2 weeks 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 "Miller Canyon: Run 2 (2026-10-20 19:05)".

v0

2 weeks ago

Miller Canyon: Run 2 — Assets reached

Built 2 weeks 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 "Miller Canyon: Run 2 (2026-10-20 20:53)".

v0

2 weeks ago

Miller Canyon: Run 2 — Burning edge by time

Built 2 weeks 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 "Miller Canyon: Run 2 (2026-10-20 19:05)".

v0

2 weeks ago

Miller Canyon: Run 2 — Burning edge by time

Built 2 weeks 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 "Miller Canyon: Run 2 (2026-10-20 20:53)".

v0

2 weeks ago

Miller Canyon: Run 2 — Fire pathways

Built 2 weeks 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 "Miller Canyon: Run 2 (2026-10-20 20:53)".

v0

2 weeks ago

Miller Canyon: Run 2 — Fire pathways

Built 2 weeks 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 "Miller Canyon: Run 2 (2026-10-20 19:05)".

v0

2 weeks ago

Miller Canyon: Run 2 — Perimeters by time

Built 2 weeks 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 "Miller Canyon: Run 2 (2026-10-20 19:05)".

v0

2 weeks ago

Miller Canyon: Run 2 — Perimeters by time

Built 2 weeks 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 "Miller Canyon: Run 2 (2026-10-20 20:53)".

v0

2 weeks ago

Miller Canyon: Run 2 — Roads cut off

Built 2 weeks 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 "Miller Canyon: Run 2 (2026-10-20 20:53)".

v0

2 weeks ago

Miller Canyon: Run 2 — Roads cut off

Built 2 weeks 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 "Miller Canyon: Run 2 (2026-10-20 19:05)".

v0

2 weeks ago

Miller Canyon: Run 2 — Roads reached

Built 2 weeks 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 "Miller Canyon: Run 2 (2026-10-20 19:05)".

v0

2 weeks ago

Miller Canyon: Run 2 — Roads reached

Built 2 weeks 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 "Miller Canyon: Run 2 (2026-10-20 20:53)".

v0

2 weeks ago

Miller Canyon: Run 2 — Spot landings

Built 2 weeks 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 "Miller Canyon: Run 2 (2026-10-20 20:53)".

v0

2 weeks ago

Miller Canyon: Run 2 — Spot landings

Built 2 weeks 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 "Miller Canyon: Run 2 (2026-10-20 19:05)".

v0

2 weeks ago

Miller Canyon: Run 2 — Spotting

Built 2 weeks 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 "Miller Canyon: Run 2 (2026-10-20 19:05)".

v0

2 weeks ago

Miller Canyon: Run 2 — Spotting

Built 2 weeks 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 "Miller Canyon: Run 2 (2026-10-20 20:53)".

v0

2 weeks ago

Miller Canyon: Run 3 (2026-10-20 19:24)

Built 2 weeks ago

Fire run for the simulation "Miller Canyon", from Simulations.

v0

2 weeks ago

Miller Canyon: Run 3 (2026-10-20 21:27)

Built 2 weeks ago

Fire run for the simulation "Miller Canyon", from Simulations.

v0

2 weeks ago

Miller Canyon: Run 3 — Assets reached

Built 2 weeks 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 "Miller Canyon: Run 3 (2026-10-20 19:24)".

v0

2 weeks ago

Miller Canyon: Run 3 — Assets reached

Built 2 weeks 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 "Miller Canyon: Run 3 (2026-10-20 21:27)".

v0

2 weeks ago

Miller Canyon: Run 3 — Burning edge by time

Built 2 weeks 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 "Miller Canyon: Run 3 (2026-10-20 21:27)".

v0

2 weeks ago

Miller Canyon: Run 3 — Burning edge by time

Built 2 weeks 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 "Miller Canyon: Run 3 (2026-10-20 19:24)".

v0

2 weeks ago

Miller Canyon: Run 3 — Fire pathways

Built 2 weeks 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 "Miller Canyon: Run 3 (2026-10-20 21:27)".

v0

2 weeks ago

Miller Canyon: Run 3 — Fire pathways

Built 2 weeks 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 "Miller Canyon: Run 3 (2026-10-20 19:24)".

v0

2 weeks ago

Miller Canyon: Run 3 — Perimeters by time

Built 2 weeks 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 "Miller Canyon: Run 3 (2026-10-20 21:27)".

v0

2 weeks ago

Miller Canyon: Run 3 — Perimeters by time

Built 2 weeks 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 "Miller Canyon: Run 3 (2026-10-20 19:24)".

v0

2 weeks ago

Miller Canyon: Run 3 — Roads cut off

Built 2 weeks 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 "Miller Canyon: Run 3 (2026-10-20 21:27)".

v0

2 weeks ago

Miller Canyon: Run 3 — Roads cut off

Built 2 weeks 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 "Miller Canyon: Run 3 (2026-10-20 19:24)".

v0

2 weeks ago

Miller Canyon: Run 3 — Roads reached

Built 2 weeks 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 "Miller Canyon: Run 3 (2026-10-20 19:24)".

v0

2 weeks ago

Miller Canyon: Run 3 — Roads reached

Built 2 weeks 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 "Miller Canyon: Run 3 (2026-10-20 21:27)".

v0

2 weeks ago

Miller Canyon: Run 3 — Spot landings

Built 2 weeks 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 "Miller Canyon: Run 3 (2026-10-20 19:24)".

v0

2 weeks ago

Miller Canyon: Run 3 — Spot landings

Built 2 weeks 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 "Miller Canyon: Run 3 (2026-10-20 21:27)".

v0

2 weeks ago

Miller Canyon: Run 3 — Spotting

Built 2 weeks 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 "Miller Canyon: Run 3 (2026-10-20 21:27)".

v0

2 weeks ago

Miller Canyon: Run 3 — Spotting

Built 2 weeks 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 "Miller Canyon: Run 3 (2026-10-20 19:24)".

v0

2 weeks ago

Miller Canyon: Run 4 (2026-10-20 19:30)

Built 2 weeks ago

Fire run for the simulation "Miller Canyon", from Simulations.

v0

2 weeks ago

Miller Canyon: Run 4 — Assets reached

Built 2 weeks 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 "Miller Canyon: Run 4 (2026-10-20 19:30)".

v0

2 weeks ago

Miller Canyon: Run 4 — Burning edge by time

Built 2 weeks 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 "Miller Canyon: Run 4 (2026-10-20 19:30)".

v0

2 weeks ago

Miller Canyon: Run 4 — Fire pathways

Built 2 weeks 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 "Miller Canyon: Run 4 (2026-10-20 19:30)".

v0

2 weeks ago

Miller Canyon: Run 4 — Perimeters by time

Built 2 weeks 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 "Miller Canyon: Run 4 (2026-10-20 19:30)".

v0

2 weeks ago

Miller Canyon: Run 4 — Roads cut off

Built 2 weeks 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 "Miller Canyon: Run 4 (2026-10-20 19:30)".

v0

2 weeks ago

Miller Canyon: Run 4 — Roads reached

Built 2 weeks 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 "Miller Canyon: Run 4 (2026-10-20 19:30)".

v0

2 weeks ago

Miller Canyon: Run 4 — Spot landings

Built 2 weeks 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 "Miller Canyon: Run 4 (2026-10-20 19:30)".

v0

2 weeks ago

Miller Canyon: Run 4 — Spotting

Built 2 weeks 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 "Miller Canyon: Run 4 (2026-10-20 19:30)".

v0

2 weeks ago

Miller Canyon: Run 5 (2026-10-20 19:33)

Needs upload

Fire run for the simulation "Miller Canyon", from Simulations.

2 weeks ago

Miller Canyon: Run 5 (2026-10-20 19:35)

Built 2 weeks ago

Fire run for the simulation "Miller Canyon", from Simulations.

v0

2 weeks ago

Miller Canyon: Run 5 — Assets reached

Built 2 weeks 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 "Miller Canyon: Run 5 (2026-10-20 19:35)".

v0

2 weeks ago

Miller Canyon: Run 5 — Burning edge by time

Built 2 weeks 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 "Miller Canyon: Run 5 (2026-10-20 19:35)".

v0

2 weeks ago

Miller Canyon: Run 5 — Fire pathways

Built 2 weeks 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 "Miller Canyon: Run 5 (2026-10-20 19:35)".

v0

2 weeks ago

Miller Canyon: Run 5 — Perimeters by time

Built 2 weeks 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 "Miller Canyon: Run 5 (2026-10-20 19:35)".

v0

2 weeks ago

Miller Canyon: Run 5 — Roads reached

Built 2 weeks 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 "Miller Canyon: Run 5 (2026-10-20 19:35)".

v0

2 weeks ago

Miller Canyon: Run 5 — Spot landings

Built 2 weeks 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 "Miller Canyon: Run 5 (2026-10-20 19:35)".

v0

2 weeks ago

Miller Canyon: Run 5 — Spotting

Built 2 weeks 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 "Miller Canyon: Run 5 (2026-10-20 19:35)".

v0

2 weeks ago

Ramsey Canyon: Run 1 (2026-10-20 16:45)

Built 2 weeks ago

Fire run for the simulation "Ramsey Canyon", from Simulations.

v0

2 weeks ago

Ramsey Canyon: Run 1 — Assets reached

Built 2 weeks 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 "Ramsey Canyon: Run 1 (2026-10-20 16:45)".

v0

2 weeks ago

Ramsey Canyon: Run 1 — Burning edge by time

Built 2 weeks 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 "Ramsey Canyon: Run 1 (2026-10-20 16:45)".

v0

2 weeks ago

Ramsey Canyon: Run 1 — Fire pathways

Built 2 weeks 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 "Ramsey Canyon: Run 1 (2026-10-20 16:45)".

v0

2 weeks ago

Ramsey Canyon: Run 1 — Perimeters by time

Built 2 weeks 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 "Ramsey Canyon: Run 1 (2026-10-20 16:45)".

v0

2 weeks ago

Ramsey Canyon: Run 1 — Roads cut off

Built 2 weeks 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 "Ramsey Canyon: Run 1 (2026-10-20 16:45)".

v0

2 weeks ago

Ramsey Canyon: Run 1 — Roads reached

Built 2 weeks 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 "Ramsey Canyon: Run 1 (2026-10-20 16:45)".

v0

2 weeks ago

Ramsey Canyon: Run 1 — Spot landings

Built 2 weeks 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 "Ramsey Canyon: Run 1 (2026-10-20 16:45)".

v0

2 weeks ago

Ramsey Canyon: Run 1 — Spotting

Built 2 weeks 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 "Ramsey Canyon: Run 1 (2026-10-20 16:45)".

v0

2 weeks ago

Ramsey Canyon: Run 2 (2026-10-20 17:01)

Built 2 weeks ago

Fire run for the simulation "Ramsey Canyon", from Simulations.

v0

2 weeks ago

Ramsey Canyon: Run 2 (2026-10-20 20:56)

Built 2 weeks ago

Fire run for the simulation "Ramsey Canyon", from Simulations.

v0

2 weeks ago

Ramsey Canyon: Run 2 — Assets reached

Built 2 weeks 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 "Ramsey Canyon: Run 2 (2026-10-20 17:01)".

v0

2 weeks ago

Ramsey Canyon: Run 2 — Assets reached

Built 2 weeks 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 "Ramsey Canyon: Run 2 (2026-10-20 20:56)".

v0

2 weeks ago

Ramsey Canyon: Run 2 — Burning edge by time

Built 2 weeks 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 "Ramsey Canyon: Run 2 (2026-10-20 17:01)".

v0

2 weeks ago

Ramsey Canyon: Run 2 — Burning edge by time

Built 2 weeks 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 "Ramsey Canyon: Run 2 (2026-10-20 20:56)".

v0

2 weeks ago

Ramsey Canyon: Run 2 — Debris flows (projected)

Built 2 weeks ago

Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "Ramsey Canyon: Run 2 (2026-10-20 17:01)".

v0

2 weeks ago

Ramsey Canyon: Run 2 — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Ramsey Canyon: Run 2 (2026-10-20 17:01)".

v0

2 weeks ago

Ramsey Canyon: Run 2 — Fire pathways

Built 2 weeks 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 "Ramsey Canyon: Run 2 (2026-10-20 17:01)".

v0

2 weeks ago

Ramsey Canyon: Run 2 — Fire pathways

Built 2 weeks 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 "Ramsey Canyon: Run 2 (2026-10-20 20:56)".

v0

2 weeks ago

Ramsey Canyon: Run 2 — Perimeters by time

Built 2 weeks 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 "Ramsey Canyon: Run 2 (2026-10-20 17:01)".

v0

2 weeks ago

Ramsey Canyon: Run 2 — Perimeters by time

Built 2 weeks 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 "Ramsey Canyon: Run 2 (2026-10-20 20:56)".

v0

2 weeks ago

Ramsey Canyon: Run 2 — Roads cut off

Built 2 weeks 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 "Ramsey Canyon: Run 2 (2026-10-20 17:01)".

v0

2 weeks ago

Ramsey Canyon: Run 2 — Roads cut off

Built 2 weeks 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 "Ramsey Canyon: Run 2 (2026-10-20 20:56)".

v0

2 weeks ago

Ramsey Canyon: Run 2 — Roads reached

Built 2 weeks 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 "Ramsey Canyon: Run 2 (2026-10-20 17:01)".

v0

2 weeks ago

Ramsey Canyon: Run 2 — Roads reached

Built 2 weeks 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 "Ramsey Canyon: Run 2 (2026-10-20 20:56)".

v0

2 weeks ago

Ramsey Canyon: Run 2 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Ramsey Canyon: Run 2 (2026-10-20 17:01)".

v0

2 weeks ago

Ramsey Canyon: Run 2 — Spot landings

Built 2 weeks 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 "Ramsey Canyon: Run 2 (2026-10-20 17:01)".

v0

2 weeks ago

Ramsey Canyon: Run 2 — Spot landings

Built 2 weeks 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 "Ramsey Canyon: Run 2 (2026-10-20 20:56)".

v0

2 weeks ago

Ramsey Canyon: Run 2 — Spotting

Built 2 weeks 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 "Ramsey Canyon: Run 2 (2026-10-20 20:56)".

v0

2 weeks ago

Ramsey Canyon: Run 2 — Spotting

Built 2 weeks 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 "Ramsey Canyon: Run 2 (2026-10-20 17:01)".

v0

2 weeks ago

Ramsey Canyon: Run 3 (2026-10-20 21:07)

Needs upload

Fire run for the simulation "Ramsey Canyon", from Simulations.

2 weeks ago

Ramsey Canyon: Run 3 (2026-10-20 21:12)

Built 2 weeks ago

Fire run for the simulation "Ramsey Canyon", from Simulations.

v0

2 weeks ago

Ramsey Canyon: Run 3 — Assets reached

Built 2 weeks 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 "Ramsey Canyon: Run 3 (2026-10-20 21:12)".

v0

2 weeks ago

Ramsey Canyon: Run 3 — Burning edge by time

Built 2 weeks 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 "Ramsey Canyon: Run 3 (2026-10-20 21:12)".

v0

2 weeks ago

Ramsey Canyon: Run 3 — Fire pathways

Built 2 weeks 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 "Ramsey Canyon: Run 3 (2026-10-20 21:12)".

v0

2 weeks ago

Ramsey Canyon: Run 3 — Perimeters by time

Built 2 weeks 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 "Ramsey Canyon: Run 3 (2026-10-20 21:12)".

v0

2 weeks ago

Ramsey Canyon: Run 3 — Roads cut off

Built 2 weeks 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 "Ramsey Canyon: Run 3 (2026-10-20 21:12)".

v0

2 weeks ago

Ramsey Canyon: Run 3 — Roads reached

Built 2 weeks 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 "Ramsey Canyon: Run 3 (2026-10-20 21:12)".

v0

2 weeks ago

Ramsey Canyon: Run 3 — Spot landings

Built 2 weeks 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 "Ramsey Canyon: Run 3 (2026-10-20 21:12)".

v0

2 weeks ago

Ramsey Canyon: Run 3 — Spotting

Built 2 weeks 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 "Ramsey Canyon: Run 3 (2026-10-20 21:12)".

v0

2 weeks ago

Ramsey Canyon: Run 4 (2026-10-20 22:22)

Built 2 weeks ago

Fire run for the simulation "Ramsey Canyon", from Simulations.

v0

2 weeks ago

Ramsey Canyon: Run 4 — Assets reached

Built 2 weeks 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 "Ramsey Canyon: Run 4 (2026-10-20 22:22)".

v0

2 weeks ago

Ramsey Canyon: Run 4 — Burning edge by time

Built 2 weeks 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 "Ramsey Canyon: Run 4 (2026-10-20 22:22)".

v0

2 weeks ago

Ramsey Canyon: Run 4 — Fire pathways

Built 2 weeks 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 "Ramsey Canyon: Run 4 (2026-10-20 22:22)".

v0

2 weeks ago

Ramsey Canyon: Run 4 — Perimeters by time

Built 2 weeks 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 "Ramsey Canyon: Run 4 (2026-10-20 22:22)".

v0

2 weeks ago

Ramsey Canyon: Run 4 — Roads cut off

Built 2 weeks 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 "Ramsey Canyon: Run 4 (2026-10-20 22:22)".

v0

2 weeks ago

Ramsey Canyon: Run 4 — Roads reached

Built 2 weeks 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 "Ramsey Canyon: Run 4 (2026-10-20 22:22)".

v0

2 weeks ago

T - Test2: Run 1 (2026-10-19 17:17)

Built 2 weeks ago

Fire run for the simulation "T - Test2", from Simulations.

v0

2 weeks ago

T - Test2: Run 1 (copy) (2026-10-20 20:47)

Built 2 weeks ago

Fire run for the simulation "T - Test2", from Simulations.

v0

2 weeks ago

T - Test2: Run 1 (copy) — Assets reached

Built 2 weeks 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 "T - Test2: Run 1 (copy) (2026-10-20 20:47)".

v0

2 weeks ago

T - Test2: Run 1 (copy) — Burning edge by time

Built 2 weeks 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 "T - Test2: Run 1 (copy) (2026-10-20 20:47)".

v0

2 weeks ago

T - Test2: Run 1 (copy) — Debris flows (projected)

Built 2 weeks ago

Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "T - Test2: Run 1 (copy) (2026-10-20 20:47)".

v0

2 weeks ago

T - Test2: Run 1 (copy) — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "T - Test2: Run 1 (copy) (2026-10-20 20:47)".

v0

2 weeks ago

T - Test2: Run 1 (copy) — Fire pathways

Built 2 weeks 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 "T - Test2: Run 1 (copy) (2026-10-20 20:47)".

v0

2 weeks ago

T - Test2: Run 1 (copy) — Perimeters by time

Built 2 weeks 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 "T - Test2: Run 1 (copy) (2026-10-20 20:47)".

v0

2 weeks ago

T - Test2: Run 1 (copy) — Roads cut off

Built 2 weeks 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 "T - Test2: Run 1 (copy) (2026-10-20 20:47)".

v0

2 weeks ago

T - Test2: Run 1 (copy) — Roads reached

Built 2 weeks 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 "T - Test2: Run 1 (copy) (2026-10-20 20:47)".

v0

2 weeks ago

T - Test2: Run 1 (copy) — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "T - Test2: Run 1 (copy) (2026-10-20 20:47)".

v0

2 weeks ago

T - Test2: Run 1 (copy) — Spot landings

Built 2 weeks 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 "T - Test2: Run 1 (copy) (2026-10-20 20:47)".

v0

2 weeks ago

T - Test2: Run 1 (copy) — Spotting

Built 2 weeks 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 "T - Test2: Run 1 (copy) (2026-10-20 20:47)".

v0

2 weeks ago

T - Test2: Run 1 — Assets reached

Built 2 weeks 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 "T - Test2: Run 1 (2026-10-19 17:17)".

v0

2 weeks ago

T - Test2: Run 1 — Burning edge by time

Built 2 weeks 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 "T - Test2: Run 1 (2026-10-19 17:17)".

v0

2 weeks ago

T - Test2: Run 1 — Debris flows (projected)

Built 2 weeks ago

Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "T - Test2: Run 1 (2026-10-19 17:17)".

v0

2 weeks ago

T - Test2: Run 1 — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "T - Test2: Run 1 (2026-10-19 17:17)".

v0

2 weeks ago

T - Test2: Run 1 — Fire pathways

Built 2 weeks ago

The routes the fire took, traced back from its edge along its arrival time. `use` counts the traced paths through a piece: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "T - Test2: Run 1 (2026-10-19 17:17)".

v0

2 weeks ago

T - Test2: Run 1 — Perimeters by time

Built 2 weeks 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 "T - Test2: Run 1 (2026-10-19 17:17)".

v0

2 weeks ago

T - Test2: Run 1 — Roads cut off

Built 2 weeks 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 "T - Test2: Run 1 (2026-10-19 17:17)".

v0

2 weeks ago

T - Test2: Run 1 — Roads reached

Built 2 weeks 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 "T - Test2: Run 1 (2026-10-19 17:17)".

v0

2 weeks ago

T - Test2: Run 1 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "T - Test2: Run 1 (2026-10-19 17:17)".

v0

2 weeks ago

T - Test2: Run 1 — Spot landings

Built 2 weeks 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 "T - Test2: Run 1 (2026-10-19 17:17)".

v0

2 weeks ago

T - Test2: Run 1 — Spotting

Built 2 weeks 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 "T - Test2: Run 1 (2026-10-19 17:17)".

v0

2 weeks ago

T - Test2: Run 3 (2026-10-20 20:52)

Built 2 weeks ago

Fire run for the simulation "T - Test2", from Simulations.

v0

2 weeks ago

T - Test2: Run 3 — Assets reached

Built 2 weeks 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 "T - Test2: Run 3 (2026-10-20 20:52)".

v0

2 weeks ago

T - Test2: Run 3 — Burning edge by time

Built 2 weeks 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 "T - Test2: Run 3 (2026-10-20 20:52)".

v0

2 weeks ago

T - Test2: Run 3 — Fire pathways

Built 2 weeks 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 "T - Test2: Run 3 (2026-10-20 20:52)".

v0

2 weeks ago

T - Test2: Run 3 — Perimeters by time

Built 2 weeks 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 "T - Test2: Run 3 (2026-10-20 20:52)".

v0

2 weeks ago

Test 1: Run 1 (2026-10-19 16:42)

Needs upload

Fire run for the simulation "Test 1", from Simulations.

2 weeks ago

Test 1: Run 1 (2026-10-19 16:51)

Needs upload

Fire run for the simulation "Test 1", from Simulations.

2 weeks ago

Test 1: Run 1 (2026-10-19 16:53)

Needs upload

Fire run for the simulation "Test 1", from Simulations.

2 weeks ago

Test 1: Run 1 (2026-10-19 16:54)

Built 2 weeks ago

Fire run for the simulation "Test 1", from Simulations.

v0

2 weeks ago

Test 1: Run 1 (2026-10-19 17:08)

Built 2 weeks ago

Fire run for the simulation "Test 1", from Simulations.

v0

2 weeks ago

Test 1: Run 1 (2026-10-19 17:10)

Built 2 weeks ago

Fire run for the simulation "Test 1", from Simulations.

v0

2 weeks ago

Test 1: Run 2 (2026-10-19 16:45)

Needs upload

Fire run for the simulation "Test 1", from Simulations.

2 weeks ago

Test 1: Run 2 (2026-10-19 16:47)

Needs upload

Fire run for the simulation "Test 1", from Simulations.

2 weeks ago

Test 1: Run 2 (2026-10-19 16:49)

Needs upload

Fire run for the simulation "Test 1", from Simulations.

2 weeks ago

Test 1: Run 2 (2026-10-19 17:19)

Built 2 weeks ago

Fire run for the simulation "Test 1", from Simulations.

v0

2 weeks ago

Test 1: Run 2 — Assets reached

Built 2 weeks 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 "Test 1: Run 2 (2026-10-19 17:19)".

v0

2 weeks ago

Test 1: Run 2 — Burning edge by time

Built 2 weeks 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 "Test 1: Run 2 (2026-10-19 17:19)".

v0

2 weeks ago

Test 1: Run 2 — Fire pathways

Built 2 weeks ago

The routes the fire took, traced back from its edge along its arrival time. `use` counts the traced paths through a piece: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Test 1: Run 2 (2026-10-19 17:19)".

v0

2 weeks ago

Test 1: Run 2 — Perimeters by time

Built 2 weeks 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 "Test 1: Run 2 (2026-10-19 17:19)".

v0

2 weeks ago

Test 1: Run 2 — Roads cut off

Built 2 weeks 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 "Test 1: Run 2 (2026-10-19 17:19)".

v0

2 weeks ago

Test 1: Run 2 — Roads reached

Built 2 weeks 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 "Test 1: Run 2 (2026-10-19 17:19)".

v0

2 weeks ago

Test 1: Run 2 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Test 1: Run 2 (2026-10-19 17:19)".

v0

2 weeks ago

Test 1: Run 2 — Spot landings

Built 2 weeks 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 "Test 1: Run 2 (2026-10-19 17:19)".

v0

2 weeks ago

Test 1: Run 2 — Spotting

Built 2 weeks 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 "Test 1: Run 2 (2026-10-19 17:19)".

v0

2 weeks ago

Test 1: Run 3 (2026-10-19 17:19)

Built 2 weeks ago

Fire run for the simulation "Test 1", from Simulations.

v0

2 weeks ago

Test 1: Run 3 (2026-10-19 17:46)

Built 2 weeks ago

Fire run for the simulation "Test 1", from Simulations.

v0

2 weeks ago

Test 1: Run 3 — Assets reached

Built 2 weeks 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 "Test 1: Run 3 (2026-10-19 17:19)".

v1

2 weeks ago

Test 1: Run 3 — Burning edge by time

Built 2 weeks 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 "Test 1: Run 3 (2026-10-19 17:19)".

v0

2 weeks ago

Test 1: Run 3 — Burning edge by time

Built 2 weeks 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 "Test 1: Run 3 (2026-10-19 17:46)".

v0

2 weeks ago

Test 1: Run 3 — Fire pathways

Built 2 weeks ago

The routes the fire took, traced back from its edge along its arrival time. `use` counts the traced paths through a piece: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Test 1: Run 3 (2026-10-19 17:19)".

v0

2 weeks ago

Test 1: Run 3 — Fire pathways

Built 2 weeks ago

The routes the fire took, traced back from its edge along its arrival time. `use` counts the traced paths through a piece: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Test 1: Run 3 (2026-10-19 17:46)".

v0

2 weeks ago

Test 1: Run 3 — Perimeters by time

Built 2 weeks 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 "Test 1: Run 3 (2026-10-19 17:19)".

v1

2 weeks ago

Test 1: Run 3 — Roads cut off

Built 2 weeks 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 "Test 1: Run 3 (2026-10-19 17:19)".

v0

2 weeks ago

Test 1: Run 3 — Roads cut off

Built 2 weeks 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 "Test 1: Run 3 (2026-10-19 17:46)".

v0

2 weeks ago

Test 1: Run 3 — Roads reached

Built 2 weeks 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 "Test 1: Run 3 (2026-10-19 17:19)".

v0

2 weeks ago

Test 1: Run 3 — Roads reached

Built 2 weeks 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 "Test 1: Run 3 (2026-10-19 17:46)".

v0

2 weeks ago

Test 1: Run 3 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Test 1: Run 3 (2026-10-19 17:19)".

v0

2 weeks ago

Test 1: Run 3 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Test 1: Run 3 (2026-10-19 17:46)".

v0

2 weeks ago

Test 1: Run 3 — Spot landings

Built 2 weeks 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 "Test 1: Run 3 (2026-10-19 17:46)".

v0

2 weeks ago

Test 1: Run 3 — Spot landings

Built 2 weeks 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 "Test 1: Run 3 (2026-10-19 17:19)".

v0

2 weeks ago

Test 1: Run 3 — Spotting

Built 2 weeks 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 "Test 1: Run 3 (2026-10-19 17:46)".

v0

2 weeks ago

Test 1: Run 3 — Spotting

Built 2 weeks 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 "Test 1: Run 3 (2026-10-19 17:19)".

v0

2 weeks ago

Test 1: Run 4 (2026-10-19 20:15)

Built 2 weeks ago

Fire run for the simulation "Test 1", from Simulations.

v0

2 weeks ago

Test 1: Run 4 (copy) (2026-10-20 16:48)

Built 2 weeks ago

Fire run for the simulation "Test 1", from Simulations.

v0

2 weeks ago

Test 1: Run 4 (copy) — Assets reached

Built 2 weeks 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 "Test 1: Run 4 (copy) (2026-10-20 16:48)".

v0

2 weeks ago

Test 1: Run 4 (copy) — Burning edge by time

Built 2 weeks 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 "Test 1: Run 4 (copy) (2026-10-20 16:48)".

v0

2 weeks ago

Test 1: Run 4 (copy) — Debris flows (projected)

Built 2 weeks ago

Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "Test 1: Run 4 (copy) (2026-10-20 16:48)".

v0

2 weeks ago

Test 1: Run 4 (copy) — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Test 1: Run 4 (copy) (2026-10-20 16:48)".

v0

2 weeks ago

Test 1: Run 4 (copy) — Fire pathways

Built 2 weeks 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 "Test 1: Run 4 (copy) (2026-10-20 16:48)".

v0

2 weeks ago

Test 1: Run 4 (copy) — Perimeters by time

Built 2 weeks 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 "Test 1: Run 4 (copy) (2026-10-20 16:48)".

v0

2 weeks ago

Test 1: Run 4 (copy) — Roads reached

Built 2 weeks 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 "Test 1: Run 4 (copy) (2026-10-20 16:48)".

v0

2 weeks ago

Test 1: Run 4 (copy) — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Test 1: Run 4 (copy) (2026-10-20 16:48)".

v0

2 weeks ago

Test 1: Run 4 (copy) — Spot landings

Built 2 weeks 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 "Test 1: Run 4 (copy) (2026-10-20 16:48)".

v0

2 weeks ago

Test 1: Run 4 (copy) — Spotting

Built 2 weeks 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 "Test 1: Run 4 (copy) (2026-10-20 16:48)".

v0

2 weeks ago

Test 1: Run 4 — Assets reached

Built 2 weeks 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 "Test 1: Run 4 (2026-10-19 20:15)".

v0

2 weeks ago

Test 1: Run 4 — Burning edge by time

Built 2 weeks 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 "Test 1: Run 4 (2026-10-19 20:15)".

v0

2 weeks ago

Test 1: Run 4 — Debris flows (projected)

Built 2 weeks ago

Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "Test 1: Run 4 (2026-10-19 20:15)".

v0

2 weeks ago

Test 1: Run 4 — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Test 1: Run 4 (2026-10-19 20:15)".

v0

2 weeks ago

Test 1: Run 4 — Fire pathways

Built 2 weeks ago

The routes the fire took, traced back from its edge along its arrival time. `use` counts the traced paths through a piece: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Test 1: Run 4 (2026-10-19 20:15)".

v0

2 weeks ago

Test 1: Run 4 — Perimeters by time

Built 2 weeks 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 "Test 1: Run 4 (2026-10-19 20:15)".

v0

2 weeks ago

Test 1: Run 4 — Roads cut off

Built 2 weeks 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 "Test 1: Run 4 (2026-10-19 20:15)".

v0

2 weeks ago

Test 1: Run 4 — Roads reached

Built 2 weeks 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 "Test 1: Run 4 (2026-10-19 20:15)".

v0

2 weeks ago

Test 1: Run 4 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Test 1: Run 4 (2026-10-19 20:15)".

v0

2 weeks ago

Test 1: Run 4 — Spot landings

Built 2 weeks 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 "Test 1: Run 4 (2026-10-19 20:15)".

v0

2 weeks ago

Test 1: Run 4 — Spotting

Built 2 weeks 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 "Test 1: Run 4 (2026-10-19 20:15)".

v0

2 weeks ago

Test 1: Run 6 (2026-10-20 20:12)

Needs upload

Fire run for the simulation "Test 1", from Simulations.

2 weeks ago

Test 3: Run 1 (2026-10-19 17:22)

Needs upload

Fire run for the simulation "Test 3", from Simulations.

2 weeks ago

Test 3: Run 1 (2026-10-19 17:25)

Built 2 weeks ago

Fire run for the simulation "Test 3", from Simulations.

v0

2 weeks ago

Test 3: Run 1 — Assets reached

Built 2 weeks 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 "Test 3: Run 1 (2026-10-19 17:25)".

v0

2 weeks ago

Test 3: Run 1 — Burning edge by time

Built 2 weeks 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 "Test 3: Run 1 (2026-10-19 17:25)".

v0

2 weeks ago

Test 3: Run 1 — Debris flows (projected)

Built 2 weeks ago

Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "Test 3: Run 1 (2026-10-19 17:25)".

v0

2 weeks ago

Test 3: Run 1 — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Test 3: Run 1 (2026-10-19 17:25)".

v0

2 weeks ago

Test 3: Run 1 — Fire pathways

Built 2 weeks ago

The routes the fire took, traced back from its edge along its arrival time. `use` counts the traced paths through a piece: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Test 3: Run 1 (2026-10-19 17:25)".

v0

2 weeks ago

Test 3: Run 1 — Perimeters by time

Built 2 weeks 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 "Test 3: Run 1 (2026-10-19 17:25)".

v0

2 weeks ago

Test 3: Run 1 — Roads cut off

Built 2 weeks 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 "Test 3: Run 1 (2026-10-19 17:25)".

v0

2 weeks ago

Test 3: Run 1 — Roads reached

Built 2 weeks 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 "Test 3: Run 1 (2026-10-19 17:25)".

v0

2 weeks ago

Test 3: Run 1 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Test 3: Run 1 (2026-10-19 17:25)".

v0

2 weeks ago

Test 3: Run 1 — Spot landings

Built 2 weeks 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 "Test 3: Run 1 (2026-10-19 17:25)".

v0

2 weeks ago

Test 3: Run 1 — Spotting

Built 2 weeks 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 "Test 3: Run 1 (2026-10-19 17:25)".

v0

2 weeks ago

Test 78403: Run 1 (2026-10-19 20:11)

Built 2 weeks ago

Fire run for the simulation "Test 78403", from Simulations.

v0

2 weeks ago

Test 78403: Run 1 — Assets reached

Built 2 weeks 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 "Test 78403: Run 1 (2026-10-19 20:11)".

v0

2 weeks ago

Test 78403: Run 1 — Burning edge by time

Built 2 weeks 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 "Test 78403: Run 1 (2026-10-19 20:11)".

v0

2 weeks ago

Test 78403: Run 1 — Debris flows (projected)

Built 2 weeks ago

Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "Test 78403: Run 1 (2026-10-19 20:11)".

v0

2 weeks ago

Test 78403: Run 1 — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Test 78403: Run 1 (2026-10-19 20:11)".

v0

2 weeks ago

Test 78403: Run 1 — Fire pathways

Built 2 weeks ago

The routes the fire took, traced back from its edge along its arrival time. `use` counts the traced paths through a piece: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Test 78403: Run 1 (2026-10-19 20:11)".

v0

2 weeks ago

Test 78403: Run 1 — Perimeters by time

Built 2 weeks 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 "Test 78403: Run 1 (2026-10-19 20:11)".

v0

2 weeks ago

Test 78403: Run 1 — Roads cut off

Built 2 weeks 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 "Test 78403: Run 1 (2026-10-19 20:11)".

v0

2 weeks ago

Test 78403: Run 1 — Roads reached

Built 2 weeks 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 "Test 78403: Run 1 (2026-10-19 20:11)".

v0

2 weeks ago

Test 78403: Run 1 — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Test 78403: Run 1 (2026-10-19 20:11)".

v0

2 weeks ago

Test 78403: Run 1 — Spot landings

Built 2 weeks 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 "Test 78403: Run 1 (2026-10-19 20:11)".

v0

2 weeks ago

Test 78403: Run 1 — Spotting

Built 2 weeks 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 "Test 78403: Run 1 (2026-10-19 20:11)".

v0

2 weeks ago

Test 78403: Run 2 - Grazing (2026-10-19 20:32)

Built 2 weeks ago

Fire run for the simulation "Test 78403", from Simulations.

v0

2 weeks ago

Test 78403: Run 2 - Grazing — Assets reached

Built 2 weeks 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 "Test 78403: Run 2 - Grazing (2026-10-19 20:32)".

v0

2 weeks ago

Test 78403: Run 2 - Grazing — Burning edge by time

Built 2 weeks 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 "Test 78403: Run 2 - Grazing (2026-10-19 20:32)".

v0

2 weeks ago

Test 78403: Run 2 - Grazing — Debris flows (projected)

Built 2 weeks ago

Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "Test 78403: Run 2 - Grazing (2026-10-19 20:32)".

v0

2 weeks ago

Test 78403: Run 2 - Grazing — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Test 78403: Run 2 - Grazing (2026-10-19 20:32)".

v0

2 weeks ago

Test 78403: Run 2 - Grazing — Fire pathways

Built 2 weeks ago

The routes the fire took, traced back from its edge along its arrival time. `use` counts the traced paths through a piece: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Test 78403: Run 2 - Grazing (2026-10-19 20:32)".

v0

2 weeks ago

Test 78403: Run 2 - Grazing — Perimeters by time

Built 2 weeks 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 "Test 78403: Run 2 - Grazing (2026-10-19 20:32)".

v0

2 weeks ago

Test 78403: Run 2 - Grazing — Roads cut off

Built 2 weeks 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 "Test 78403: Run 2 - Grazing (2026-10-19 20:32)".

v0

2 weeks ago

Test 78403: Run 2 - Grazing — Roads reached

Built 2 weeks 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 "Test 78403: Run 2 - Grazing (2026-10-19 20:32)".

v0

2 weeks ago

Test 78403: Run 2 - Grazing — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Test 78403: Run 2 - Grazing (2026-10-19 20:32)".

v0

2 weeks ago

Test 78403: Run 2 - Grazing — Spot landings

Built 2 weeks 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 "Test 78403: Run 2 - Grazing (2026-10-19 20:32)".

v0

2 weeks ago

Test 78403: Run 2 - Grazing — Spotting

Built 2 weeks 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 "Test 78403: Run 2 - Grazing (2026-10-19 20:32)".

v0

2 weeks ago

Test 78403: Run 3 - Shaded fuel break (2026-10-19 20:59)

Built 2 weeks ago

Fire run for the simulation "Test 78403", from Simulations.

v0

2 weeks ago

Test 78403: Run 3 - Shaded fuel break — Assets reached

Built 2 weeks 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 "Test 78403: Run 3 - Shaded fuel break (2026-10-19 20:59)".

v0

2 weeks ago

Test 78403: Run 3 - Shaded fuel break — Burning edge by time

Built 2 weeks 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 "Test 78403: Run 3 - Shaded fuel break (2026-10-19 20:59)".

v0

2 weeks ago

Test 78403: Run 3 - Shaded fuel break — Debris flows (projected)

Built 2 weeks ago

Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "Test 78403: Run 3 - Shaded fuel break (2026-10-19 20:59)".

v0

2 weeks ago

Test 78403: Run 3 - Shaded fuel break — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Test 78403: Run 3 - Shaded fuel break (2026-10-19 20:59)".

v0

2 weeks ago

Test 78403: Run 3 - Shaded fuel break — Fire pathways

Built 2 weeks ago

The routes the fire took, traced back from its edge along its arrival time. `use` counts the traced paths through a piece: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Test 78403: Run 3 - Shaded fuel break (2026-10-19 20:59)".

v0

2 weeks ago

Test 78403: Run 3 - Shaded fuel break — Perimeters by time

Built 2 weeks 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 "Test 78403: Run 3 - Shaded fuel break (2026-10-19 20:59)".

v0

2 weeks ago

Test 78403: Run 3 - Shaded fuel break — Roads cut off

Built 2 weeks 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 "Test 78403: Run 3 - Shaded fuel break (2026-10-19 20:59)".

v0

2 weeks ago

Test 78403: Run 3 - Shaded fuel break — Roads reached

Built 2 weeks 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 "Test 78403: Run 3 - Shaded fuel break (2026-10-19 20:59)".

v0

2 weeks ago

Test 78403: Run 3 - Shaded fuel break — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Test 78403: Run 3 - Shaded fuel break (2026-10-19 20:59)".

v0

2 weeks ago

Test 78403: Run 3 - Shaded fuel break — Spot landings

Built 2 weeks 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 "Test 78403: Run 3 - Shaded fuel break (2026-10-19 20:59)".

v0

2 weeks ago

Test 78403: Run 3 - Shaded fuel break — Spotting

Built 2 weeks 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 "Test 78403: Run 3 - Shaded fuel break (2026-10-19 20:59)".

v0

2 weeks ago

Test 78403: Run 4 - Both & Extended (2026-10-19 21:22)

Built 2 weeks ago

Fire run for the simulation "Test 78403", from Simulations.

v0

2 weeks ago

Test 78403: Run 4 - Both & Extended — Assets reached

Built 2 weeks 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 "Test 78403: Run 4 - Both & Extended (2026-10-19 21:22)".

v0

2 weeks ago

Test 78403: Run 4 - Both & Extended — Burning edge by time

Built 2 weeks 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 "Test 78403: Run 4 - Both & Extended (2026-10-19 21:22)".

v0

2 weeks ago

Test 78403: Run 4 - Both & Extended — Debris flows (projected)

Built 2 weeks ago

Projected post-fire debris-flow channels (USGS pfdf on the simulated burn), one row per channel per design storm: `storm` (peak 15-minute rainfall, mm/h), `likelihood` (Staley 2017 M1), `volume` in cubic metres (Gartner 2014) and `hazard` 1-3 (Cannon 2010). Filter on `storm` to pick one. A projection from fire behaviour, not a mapped burn. Written by each run of the fire simulation whose output file is "Test 78403: Run 4 - Both & Extended (2026-10-19 21:22)".

v0

2 weeks ago

Test 78403: Run 4 - Both & Extended — Debris-flow basins (projected)

Built 2 weeks ago

The outlet basins of the projected debris-flow channels, one row per basin per design storm, with the outlet channel's likelihood, volume and hazard and the outlet's `outletLon`/`outletLat`. Filter on `storm` to pick one. Written by each run of the fire simulation whose output file is "Test 78403: Run 4 - Both & Extended (2026-10-19 21:22)".

v0

2 weeks ago

Test 78403: Run 4 - Both & Extended — Fire pathways

Built 2 weeks ago

The routes the fire took, traced back from its edge along its arrival time. `use` counts the traced paths through a piece: the higher, the more the fire ran that way. Written by each run of the fire simulation whose output file is "Test 78403: Run 4 - Both & Extended (2026-10-19 21:22)".

v0

2 weeks ago

Test 78403: Run 4 - Both & Extended — Perimeters by time

Built 2 weeks 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 "Test 78403: Run 4 - Both & Extended (2026-10-19 21:22)".

v0

2 weeks ago

Test 78403: Run 4 - Both & Extended — Roads cut off

Built 2 weeks 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 "Test 78403: Run 4 - Both & Extended (2026-10-19 21:22)".

v0

2 weeks ago

Test 78403: Run 4 - Both & Extended — Roads reached

Built 2 weeks 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 "Test 78403: Run 4 - Both & Extended (2026-10-19 21:22)".

v0

2 weeks ago

Test 78403: Run 4 - Both & Extended — Smoke (screening estimate)

Built 2 weeks ago

Ground-level PM2.5 from the fire, by the hour, as areas in each EPA AQI category above Good (`class` 1 Moderate to 5 Hazardous; `val`/`valTo` the µg/m³ range; `hour` since ignition). A Gaussian plume screening estimate, not a forecast. Written by each run of the fire simulation whose output file is "Test 78403: Run 4 - Both & Extended (2026-10-19 21:22)".

v0

2 weeks ago

Test 78403: Run 4 - Both & Extended — Spot landings

Built 2 weeks 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 "Test 78403: Run 4 - Both & Extended (2026-10-19 21:22)".

v0

2 weeks ago

Test 78403: Run 4 - Both & Extended — Spotting

Built 2 weeks 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 "Test 78403: Run 4 - Both & Extended (2026-10-19 21:22)".

v0

2 weeks ago

Fire Behavior

Files