Software · Transportation systems
VIGO
Understand a transit network, from a single departure to a citywide service change. VIGO brings network inspection, journey planning, and scheduled accessibility into one local workspace.
From network to journey
Timetables, street networks, and vehicle reports describe different parts of a journey. VIGO brings them into the same City so a network question can be followed through to a route, stop, trip, and source record.
Network shows reporting coverage and service alerts. Routes connects trip times, station boards, and line views. Experimental Ask lets a configured model use transit tools with sources and an inspectable activity trail. Its interpretations remain subject to review.
Test the service people can reach
Route plans transit, walking, and driving journeys, including ordered via points. Reach maps travel time from an origin and supports comparisons of planned transit changes in Studio’s Analyze view. Matrix computes travel times between sets of places through the command line and Python interface.
A shared Rust engine supports Studio, the command line, and a separate Python interface. Computed results retain the request, City identity, warnings, and timing, so an analysis can be inspected alongside its inputs.
Keep the model visible
Scheduled queries and supported realtime snapshots are separate routing modes. Matrix and Reach remain scheduled. A calculated journey describes the supplied network and service model; it does not establish delivered-service reliability.
The 0.4.2 source prepares driving hierarchies during City builds, shares endpoint work in native matrix queries, and aligns route shapes in Rust. September’s follow-up bounds queued work and retained caches, and lets Studio recover from an Engine exit while keeping its window open. Failed requests remain visible and are not silently replayed.
The latest public desktop download remains the 0.4.1 pre-release. The source repository includes the newer 0.4.2 work.