Product · Transportation systems
VIGO
A local transit workbench built around one persisted network, from GTFS ingestion through routing, scenarios, and evidence export.
The instrument
VIGO makes the map the primary working surface. Tables, time views, findings, routes, and scenario controls explain a selected network object without pushing the network aside.
GTFS and OSM inputs stay on the machine and stream into local SQLite stores. Routes, schedules, findings, and scenarios all read from that persisted network, so the path back to source data stays visible.
What it does
- Load local GTFS and OSM data into a reproducible project workspace.
- Trace service through linked maps, route patterns, stops, schedules, and source lineage.
- Route journeys, compute matrices and regional ranges, and compare service scenarios.
- Review findings and export evidence packages with assumptions and source fingerprints.
Version 0.2.5
Version 0.2.5 makes GTFS and OSM preparation recoverable after interruption. Failed and cancelled jobs retain their source for retry, and an interrupted job no longer remains stuck as Preparing. The desktop, local API, command line, and Python interface now report the same routing status.
Accessibility analysis now returns every reached street edge through the resident native search. Timetable results remain exact within the declared service model; stochastic headways, some transfer semantics, interlining, and full pathway-accessibility constraints remain outside the current coverage.