v0 · … · built 2 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 "Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 (2026-11-10 19:05)".
What you upload. Files are the raw material — run a job against one to turn it into a table or a tile.
Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 — Engine routes
551a37d3-54ac-40cb-812a-e417d3bdadd1
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 "Berthoud Community Fires, Apr 22, 2022: Cushman–Sedona Hills–Rainbow Lake Fire, Apr 22, 2022 (2026-11-10 19:05)".
v0
2 days ago by Thomas Marsh
2 days ago by Thomas Marsh
Each upload of this file is a version. Jobs run against a specific one, so older versions are kept.
Jobs turn this file into something the map can draw — a parquet table, or GeoTIFF tiles.
File to Table(s)
Re-run a job on a timer, for data that changes at the source — a nightly feed, a weekly extract.