Files
36

What you upload. Files are the raw material — run a job against one to turn it into a table or a tile.

Fire Start Locations.csv

v1
3 weeks ago

headquarters_440901__WeatherHourly__08-02-2026__08-10-2026.fw21

v0
2 weeks ago

Portal: Farsite 08-07-2026 (2026-10-21 19:52)

Built 2 weeks ago
Fire run for the simulation "Portal", from Simulations.
v0
2 weeks ago

Portal: Farsite 08-07-2026 with Treatment (2026-10-21 19:56)

Built 2 weeks ago
Fire run for the simulation "Portal", from Simulations.
v0
2 weeks ago

Portal: Farsite 08-07-2026 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 "Portal: Farsite 08-07-2026 with Treatment (2026-10-21 19:56)".
v0
2 weeks ago

Portal: Farsite 08-07-2026 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 "Portal: Farsite 08-07-2026 with Treatment (2026-10-21 19:56)".
v0
2 weeks ago

Portal: Farsite 08-07-2026 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 "Portal: Farsite 08-07-2026 with Treatment (2026-10-21 19:56)".
v0
2 weeks ago

Portal: Farsite 08-07-2026 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 "Portal: Farsite 08-07-2026 with Treatment (2026-10-21 19:56)".
v0
2 weeks ago

Portal: Farsite 08-07-2026 — 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 "Portal: Farsite 08-07-2026 (2026-10-21 19:52)".
v0
2 weeks ago

Portal: Farsite 08-07-2026 — 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 "Portal: Farsite 08-07-2026 (2026-10-21 19:52)".
v0
2 weeks ago

Portal: Farsite 08-07-2026 — 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 "Portal: Farsite 08-07-2026 (2026-10-21 19:52)".
v0
2 weeks ago

Portal: Farsite 08-07-2026 — 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 "Portal: Farsite 08-07-2026 (2026-10-21 19:52)".
v0
2 weeks ago

Portal: MTT (2026-10-21 19:45)

Built 2 weeks ago
Fire run for the simulation "Portal", from Simulations.
v0
2 weeks ago

Portal: MTT with Treatment (2026-10-21 19:56)

Built 2 weeks ago
Fire run for the simulation "Portal", from Simulations.
v0
2 weeks ago

Portal: MTT 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 "Portal: MTT with Treatment (2026-10-21 19:56)".
v0
2 weeks ago

Portal: MTT 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 "Portal: MTT with Treatment (2026-10-21 19:56)".
v0
2 weeks ago

Portal: MTT 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 "Portal: MTT with Treatment (2026-10-21 19:56)".
v0
2 weeks ago

Portal: MTT 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 "Portal: MTT with Treatment (2026-10-21 19:56)".
v0
2 weeks ago

Portal: MTT with Treatment — 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 "Portal: MTT with Treatment (2026-10-21 19:56)".
v0
2 weeks ago

Portal: MTT 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 "Portal: MTT with Treatment (2026-10-21 19:56)".
v0
2 weeks ago

Portal: MTT 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 "Portal: MTT with Treatment (2026-10-21 19:56)".
v0
2 weeks ago

Portal: MTT 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 "Portal: MTT with Treatment (2026-10-21 19:56)".
v0
2 weeks ago

Portal: MTT 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 "Portal: MTT with Treatment (2026-10-21 19:56)".
v0
2 weeks ago

Portal: MTT — 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 "Portal: MTT (2026-10-21 19:45)".
v0
2 weeks ago

Portal: MTT — 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 "Portal: MTT (2026-10-21 19:45)".
v0
2 weeks ago

Portal: MTT — 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 "Portal: MTT (2026-10-21 19:45)".
v0
2 weeks ago

Portal: MTT — 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 "Portal: MTT (2026-10-21 19:45)".
v0
2 weeks ago

Portal: MTT — 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 "Portal: MTT (2026-10-21 19:45)".
v0
2 weeks ago

Portal: MTT — 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 "Portal: MTT (2026-10-21 19:45)".
v0
2 weeks ago

Portal: MTT — 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 "Portal: MTT (2026-10-21 19:45)".
v0
2 weeks ago

Portal: MTT — 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 "Portal: MTT (2026-10-21 19:45)".
v0
2 weeks ago

Portal: MTT — 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 "Portal: MTT (2026-10-21 19:45)".
v0
2 weeks ago

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

Needs upload
Fire run for the simulation "Ramsey Canyon", from Simulations.
2 weeks ago

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

Needs upload
Fire run for the simulation "Ramsey Canyon", from Simulations.
2 weeks ago

SierraVistaFire.zip

v0
4 months ago

SierraVistaFireStart97thPercentile.zip

v1
4 months ago
Bintel