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

511 Alberta — traffic cameras API

Read
yes, on the basis of a feed or service it offers for others to read
What the paper uses
figures and listings, credited
How it is read
open-data API
Terms
its terms, read 2026-10-11: “The information has been posted with the intent that it be readily available for personal and public non-commercial (educational) use, and except where otherwise prohibited, may be reproduced, in part or in whole and by any means, without charge or further permission from the Government of Alberta.”
Licence
511 Alberta terms of use (Government of Alberta) — linked wherever the paper credits it
Robots
robots.txt allows our reader (checked 2026-10-11)
Offers its feed to readers
yes
Permission
not yet asked
Credit
511 Alberta (Government of Alberta) — locations only
Decided by
the paper's publisher, 2026-10-12 (docs/DECISIONS.md #41, recommendation accepted 2026-10-12)
Notes

Supplies live roadside imagery URLs to illustrate a closure or a storm in a visual brief.

RECORDED 2026-10-12 (DECISIONS #41, the owner accepted the recommendation): read as names and coordinates only, by functions/mapfeed.js shapeCameras. The images stay with 511 and are LINKED, NEVER EMBEDDED — some are third-party, and the owner's ruling of 2026-08-26 ('we link to them, we don't post their live feed') stands; tests/test_mapfeed.py holds that no view URL enters the payload. Every credit links the terms page as the licence. WIRING RECKONING 2026-08-26: WIRED — edge consumer functions/mapfeed.js shapeCameras serves NAMES AND COORDINATES ONLY as the map's camera-glyph layer (cameramap.js), under the owner's ruling verbatim: 'we link to them, we don't post their live feed.' The register's Views[].Url is the live JPEG and NEVER enters the payload (a test holds the invariant); a camera with no Enabled view is dropped. The popup links to 511's own map with its camera layer on (map#:Cameras — the fragment format their app itself writes); 511 publishes no per-camera reader page (/cameras 302s to /notfound, /tooltip/Cameras/<id> is a map partial that answers 200 for bogus ids, /map/Cctv/<id> is the raw image), so no per-camera link ships — an unverifiable link shape cannot be held to the pins-must-not-strand rule. The imagery-permission question is CLOSED by the ruling; do not draft that email. | 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. Metadata only — you still fetch each image separately, and those fetches are not covered by the API throttle but should be rate-limited voluntarily. Check image licensing before republishing in a commercial product. 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 hello@edmontondailybrief.ca. We stop reading it and withdraw everything that cited it, past editions included. Every source · How this paper is made