Call-prep brief · checked 2026-10-20
Edmonton Transit Service (ETS)
Grade B · 83.8 / 100
Down 0.5 points since 2026-10-19 (B to B).
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the rider information is complete. Each fix is framed as a next step, not a failure.
What changed since the last check
- Correctness no change
- Freshness down 1.7
- Rider experience no change
- Realtime quality down 0.6
Top three things to fix
Remove retired stops from the export, or add them back to the trips that should serve them.
Some stops exist in the feed but no trip ever stops at them. Riders may walk to a stop where no transit vehicle is scheduled to arrive.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
Effort: A review pass in your scheduling software.
Pick a darker/lighter route_text_color for the flagged routes.
Some route colors don't contrast with their text color. Route badges get hard to read, most of all for riders with low vision.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
Effort: One field per route.
Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'.
Some route long names repeat the route's short name inside them. Apps show both names together, so riders see the number twice, like '5 5 Downtown'.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
Effort: One field per flagged route.
Riders and need behind these fixes
- Rider-trip figures come from the United States National Transit Database, which does not cover this feed's country.
- No need reading for this feed was on hand when this was built, so transit need is not known.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- Some stops exist in the feed but no trip ever stops at them.
- Next action
- Remove retired stops from the export, or add them back to the trips that should serve them.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Some route colors don't contrast with their text color.
- Next action
- Pick a darker/lighter route_text_color for the flagged routes.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Some route long names repeat the route's short name inside them.
- Next action
- Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
Key facts
- Feed URL
- https://gtfs.edmonton.ca/TMGTFSRealTimeWebService/GTFS/GTFS.zip
- Last checked
- 2026-10-20
- Service window
- 39 days of service data remain. Last service date 2026-11-28.
- Feed version
- 261002_1029
- Location
- Alberta, Canada
Part of the Canada portfolio: see where this agency sits among the other feeds in that group before the call.
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.4, validator 8.0.1.