Capital District Transportation Authority (CDTA)

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. Re-export the feed with a calendar that reaches further out. Set feed_end_date in feed_info.txt past your next service change.

   Service data ended 39 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.

   This one is about the feed as a whole, so there is no share of it to count.

   Estimated effort: Usually one export setting; export on a schedule so it never lapses again.

2. Remove past service periods the next time you export the feed.

   Some service calendars in the feed have already ended. Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.

   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.

   Estimated effort: One setting in most export tools.

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

   Estimated effort: A review pass in your scheduling software.