Feeds
Every tracker connects to a data server for its departure times.
ETR runs its own, using TJ Horner’s transit-tracker-api.
Transit systems covered: Edmonton (ETS, which includes St. Albert, Strathcona County,
Spruce Grove, Fort Saskatchewan, Beaumont and Leduc), Calgary, Red Deer, Lethbridge, Medicine Hat, Grande Prairie,
Roam (Bow Valley) and Wood Buffalo.
October 23, 2026
Second data server, shared real-time cache
Added
realfeeds.edmontontransitriders.org, a second data server where Edmonton routes and stops are coded ets:, the same as upstream's naming. New setups use it.
Changed
- Both servers now share one cached copy of ETS's real-time data instead of each fetching it separately.
Known issues
feeds.edmontontransitriders.org (Edmonton coded kcm:) stays online for trackers set up before the switch. Moving a tracker means re-pushing its routes with ets: codes.
October 22, 2026
Seven more Alberta transit systems
Added
- Calgary, Red Deer, Lethbridge, Medicine Hat, Grande Prairie, Roam (Bow Valley) and Wood Buffalo. Real-time predictions where the agency publishes them: Calgary, Medicine Hat, Roam and Wood Buffalo. The others show scheduled times.
Fixed
- Calgary real-time predictions froze, because Calgary's server asks for its data to be cached for 14 days. They now refresh every 15 seconds.
October 21, 2026
ETR runs its own data server
Added
feeds.edmontontransitriders.org serves ETS schedules and real-time predictions. ETS's data also covers St. Albert, Strathcona County, Spruce Grove, Fort Saskatchewan, Beaumont and Leduc. Schedules refresh daily.
Changed
- Edmonton is coded
kcm: on this server, matching what trackers already in the field have stored.
Fixed
- Looking up departures for a stop went from about 10 seconds to a few milliseconds.
