Megacity Transit Optimisation Platform
Five live feeds at five different rates, reconciled onto one clock.
Captured from the running product. transitoptimizer.terranexamaps.com
Subway telemetry arrives every 10 seconds, PATH every 15, bus CAD/AVL every 30, ferry AIS every 45 and commuter-rail block occupancy every 60 — roughly 1,040 records a minute. All five are snapped onto one ten-minute decision clock with explicit staleness accounting, so a decision is never made on a feed that has quietly gone quiet.
When a surge pushes platform load past the 92% target, the engine prices the timetable change: interval, extra departures, rolling stock, riders absorbed and cost per hour. When the cause is degraded track rather than demand, it proposes load diversion and street bridging instead — because more trains cannot pass a failed interlocking.
What is actually running
- Five feeds at five different rates reconciled onto one 10-minute decision clock, with staleness accounting.
- Demand measured against service in the same units across 464 stations, so load factor reflects throughput.
- Dynamic headway adjustment prices a timetable change when load passes the 92% target.
- Correct response chosen by cause: timetable change for demand surges, diversion and street bridging for track faults.
Built with
Open the live product
This is the deployed application, not a recording. It opens in a new tab and runs in your browser.