Edmonton Daily Brief · Sources

Sources

<a href="/sources.html">Sources</a>

EDB · Sections
  1. Front page
  2. Weather & Alerts
  3. City Hall
  4. Public Safety
  5. Development & Business
  6. Courts & Legal
  7. Sports
  8. Schools & Campus
  9. Community & Events
  10. Tech & Research
  11. The Province
  12. What’s On — every listing, weeks ahead
  13. Buses — the live tracker
  14. Search the paper

Edmonton Transit Service — GTFS-Realtime Trip Updates

Read
yes, on the basis of an open licence
What the paper uses
figures and listings, credited
How it is read
transit feed
Terms
its terms, read 2026-08-23
Licence
Open Government Licence – City of Edmonton — linked wherever the paper credits it
Permission
not yet asked
Decided by
the paper's editor, 2026-10-11 (DECISIONS #39 (2026-10-11): read by the edge with no enabled record; evidence as its enabled sibling's, owner approved recording the clear cases; same feed family and licence as edmonton_transit_service_gtfs_realtime_service_alerts)
Notes

Systemwide delay data — you could compute an 'ETS on-time performance yesterday' metric, which no one else publishes.

LICENCE LINKED 2026-10-12 (owner: a licence link wherever possible): the City's catalogue offers this feed as dataset dp5u-srkp ('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/stopeta.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/stopeta.js serves per-stop departures as /stopeta (decodeTripUpdates in functions/_gtfsrt.js; reuse_ref LIVE LAYER note); the on-time-performance METRIC remains unbuilt, but the feed is no longer unread | 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. VERY HIGH VOLUME — 4.5 MB per poll. Do NOT poll this frequently unless you're building an analytics pipeline; it is not directly brief-worthy on its own. Aggregate, don't republish. 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.

If this is yours and you want it left out, write to [email protected]. We stop reading it and withdraw everything that cited it, past editions included. Every source · How this paper is made