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.1
Version 0.2.1 keeps the resident Rust routing kernel, SQLite-native project stores, desktop shell, and shared route, matrix, command-line, and Python interfaces.
Timetable search is exact within the declared service model. Internal Pareto state covers arrival and boardings; the five-route interface is a bounded usefulness selection, not a frontier over fare, reliability, or crowding. Historical benchmarks keep the release label that produced them.