Edmonton Transit Service (ETS)

What this grade measures

The quality of the schedule data in the feed scored here for trip-planning apps: whether riders using Google Maps, Apple Maps, or Transit see current, correct, and complete information. It measures the data feed, not service quality or operations.

Progress this period

No newly cleared items this period. The score and trend above reflect where the feed stands today.

What needs attention next

Three improvements, in priority order, each sized so the board can see what it is approving:

1. 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.

   Estimated effort: A review pass in your scheduling software.

2. 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.

   Estimated effort: One field per route.

3. 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'.

   Estimated effort: One field per flagged route.