Sources

Live vehicle locations; useful for a map widget or to confirm a service disruption is real.

LICENCE LINKED 2026-10-12 (owner: a licence link wherever possible): the City's catalogue offers this feed as dataset uyt2-vrrn ('Real Time ... GTFS (PB File)'), licence 'See Terms of Use' (read 2026-10-12), which is the Open Government Licence – City of Edmonton v1.0. ENABLED 2026-10-11: read from the edge only (functions/transit.js), every minute a reader has the layer open, under the same City licence as the service-alert feed (edmonton_transit_service_gtfs_realtime_service_alerts). It had been disabled because the PIPELINE fetches nothing, which left a source the site reads with no record that says it may. | WIRING RECKONING 2026-08-25: WIRED — edge consumer functions/transit.js serves it to readers as /transit (decoded by functions/_gtfsrt.js; reuse_ref LIVE LAYER note); the pipeline itself still fetches nothing | WIRING TRIAGE 2026-08-23 — INSTRUMENT, NOT A SOURCE: a dataset for a page fixture (a number, a map, a table), never a candidate story — wiring it means a fixture and a renderer, which is a product decision with the front end, not a collector. Only 44KB, which is small for a fleet this size — suggests it covers a subset of vehicles, or was captured at a low-service hour (I tested mid-afternoon). Validate coverage before relying on it. Catalogued but NOT WIRED as of 2026-08-21. Its mode has no generic collector and no code refers to this endpoint, so nothing fetched it and no health record ever existed. Disabled so the registry stops counting it as coverage; the entry is kept because the endpoint was verified and this is a wiring backlog, not a dead source. See ops/wiring.py.