Vienna U-Bahn & S-Bahn Map

Website: https://salarshk.github.io/vienna-ubahn-live-map/ Product overview: https://salarshk.github.io/vienna-ubahn-live-map/overview/

An interactive map of Vienna's U-Bahn and S-Bahn networks. It shows live U-Bahn departure estimates and scheduled S-Bahn positions.

The Wiener Linien real-time interface publishes departure predictions, not vehicle GPS coordinates. This app walks each prediction backwards along its line's official station sequence and estimated segment timings. Train dots are therefore position estimates, and the interface fades uncertain estimates. When a line has no usable live prediction, hollow dashed dots show timetable simulations so they cannot be mistaken for reported trains.

ÖBB's public feed does not provide S-Bahn vehicle GPS. S-Bahn dots are therefore interpolated between the station times in the official 2026 GTFS timetable and are always drawn hollow and labelled as scheduled estimates.

Features

• U1, U2, U3, U4 and U6 on an interactive MapLibre map
• S1, S2, S3, S4, S7, S40, S45, S50, S60 and S80
• Live Wiener Linien departure predictions
• Scheduled ÖBB S-Bahn positions that respect service calendars and exceptions
• Estimated moving train positions and confidence styling
• Clickable train details with direction, adjacent stations and source confidence
• Live Wiener Linien service disruptions highlighted by line and station
• Search across U-Bahn and S-Bahn stations
• Independent U-Bahn/S-Bahn line and train layers, with a marker legend
• Line filters, light/dark themes and nearest-station location
• S-Bahn timetable validity warnings and automatic monthly refresh checks
• Station departure panels with live countdowns
• Full-screen departure board at ?mode=dashboard
• Automated U-Bahn delay-data collection with chronological holdout evaluation
• Official historical incident import and live disruption context as model features
• Fast prequential calibration that can report leakage-free experimental metrics after 30 completed journeys
• Public MAE, RMSE, R², within-one-minute accuracy and 3+ minute delay metrics
• Button-triggered AI advisor with evidence-backed passenger and operations suggestions
• Shared React codebase for the web and a Capacitor iOS shell
• Opt-in follow-me GPS mode with a nearby-station list (coordinates stay on the device)
• Device-local commute dashboard for up to four saved stations
• Opt-in browser/PWA notifications for newly observed official disruptions
• Update prompt when a newer PWA shell is ready
• Delay evidence timeline separating planned time, operator-reported delay and model estimate
• Experimental Prediction Lab: dwell, headway, disruption clearance, severity, transfers, route reliability, cancellation risk, crowding, weather/event readiness, S-Bahn connections, anomalies and uncertainty calibration

The delay model can publish a clearly marked preliminary score after at least 36 hours spanning two calendar days and a sufficiently large untouched test period. It is automatically promoted to validated status only after the seven-day safeguards are met. Its methodology is documented in docs/ml-delay-model.md.

The AI advisor is an optional, separately hosted secure service and is gated off in the production build for now. The public website never contains an OpenAI key and does not call the rail-data Worker for GPT requests. Its evidence contract and safeguards are documented in docs/llm-rail-advisor.md.

Run locally

npm install
npm run dev

Open http://localhost:5173.

The hosted site is also an installable Progressive Web App. On Android/Chrome use the browser's install prompt; on iPhone/Safari choose Share → Add to Home Screen. The installed shell can reopen during a short network interruption, while live departures refresh when connectivity returns.

The map's My commute panel stores saved stations only in local browser storage. Follow me uses the phone's GPS only after the user starts it; it can be stopped at any time. Disruption notifications are also opt-in and are generated from the official service-message feed while the app is open or installed with notification support. A server-backed push system would require an additional subscription backend and is intentionally not enabled here.

npm test
npm run build

GitHub Pages

Pushes to main are automatically built and published through the Pages workflow in .github/workflows/deploy-pages.yml. The hosted build routes its read-only departure requests through the open-source corsproxy.nl relay because the official endpoint does not provide browser CORS headers. The data still comes directly from Wiener Linien and the relay receives only public station identifiers.

Data pipeline health and optional context feeds

The Cloudflare Worker saves a station-level Wiener Linien summary to R2 each minute, full observation snapshots every five minutes, and dated WienMobil Rad samples every five minutes. Public rail and bike history endpoints mark stale data rather than presenting it as live. A separate scheduled job publishes hourly reliability reports. GitHub Actions restores a recent training window from the long-term R2 archive, saves new observations before training, and publishes model and data-quality reports. Each completed model report also has a dated R2 copy. The map's live feed is separate from these archives.

Traffic-counter locations are public metadata, but measured road values and event records require provider access. Configure these Worker variables only when the corresponding licensed or public endpoint is available:

VIENNA_TRAFFIC_API_URL   measured Vienna traffic-counter feed
EVIS_TRAFFIC_API_URL     EVIS / ITS Vienna Region relay
VIENNA_EVENTS_API_URL    Vienna event-record relay

Until configured, the Urban Mobility panel labels traffic as catalog-only and events as not configured; its forecasts remain time-of-day baselines rather than pretending to be measured traffic or attendance.

Refresh Vienna data

npm run build:vienna-data

That command downloads Wiener Linien's current Open Government Data files and regenerates the compact line, station, identifier, color and segment-timing files in src/data/.

To refresh the S-Bahn routes and timetable from ÖBB's annual GTFS feed:

npm run build:sbahn

The scheduled refresh-sbahn.yml workflow checks for a newer annual feed on the first day of each month, verifies it, and commits the generated timetable only when the source data changed. If the bundled calendar has expired, the app withdraws S-Bahn movements rather than presenting stale scheduled positions.

Data sources and accuracy

• Static station sequences, coordinates and identifiers: Wiener Linien Open Data
• Live departures: Wiener Linien real-time monitor API
• Historical disruptions: Mobilitätsdaten Österreich – Wiener Linien incident history
• S-Bahn routes and timetable: ÖBB GTFS Fahrplan
• Data attribution: Datenquelle Stadt Wien – https://data.wien.gv.at
• Basemap: OpenStreetMap/Esri in a fresh clone

This is an independent project and is not operated or endorsed by Wiener Linien. Live markers are inferred from arrivals and should not be treated as exact train locations.

Acknowledgements

This Vienna adaptation is based on JieGH's original vibe_VLCmetroMap project. The original Git history and Apache 2.0 license are preserved.

Privacy

The locate button requests a high-accuracy device GPS fix, with a browser geolocation fallback for the PWA when the Capacitor bridge is unavailable. It compares that one fix against the station list in the browser. The coordinates are not sent to Wiener Linien or to an application server. A visible accuracy ring and freshness fade prevent an old or imprecise fix from looking exact. Continuous follow mode uses the same browser-local path and is explicitly stopped when the user hides the location or closes the page.

License

Code is licensed under Apache 2.0. Vienna open data is published under CC BY.