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)".
Details
What you upload. Files are the raw material — run a job against one to turn it into a table or a tile.
Miller Canyon: Run 2 — Fire pathways
5464a1ef-a181-4e1e-85ac-444af9119d38
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 by rachelle.wilson@bintel.io
2 weeks ago by rachelle.wilson@bintel.io
Versions
Each upload of this file is a version. Jobs run against a specific one, so older versions are kept.
Jobs
Jobs turn this file into something the map can draw — a parquet table, or GeoTIFF tiles.
File to Table(s)
Schedules
Re-run a job on a timer, for data that changes at the source — a nightly feed, a weekly extract.
