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 "Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire (2026-11-10 18:52)".
What you upload. Files are the raw material — run a job against one to turn it into a table or a tile.
Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire — Engine routes
2220e9f8-579c-40de-90fd-68fbb8c5bdaa
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 "Horseshoe Park–Willis Farms Fire: Horseshoe Park–Willis Farms Fire (2026-11-10 18:52)".
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.