Cat Tran Shuttle

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. Correct feed_end_date in feed_info.txt. Set it to 2025-05-25, the last day in your calendar, or to the last day your schedule is reliable.

   feed_info.txt says this feed ends on 2024-12-13. Your service calendar runs to 2025-05-25. The GTFS standard tells apps to trust a feed only up to its end date. So apps may stop showing your service on the earlier date, even though the calendar goes on.

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

   Estimated effort: One field in feed_info.txt, often an export setting.

2. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

   52 of 52 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

   Fixing this covers all 52 stops in the feed.

   Estimated effort: A column in stops.txt; your scheduling software likely has it.

3. Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.

   The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

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

   Estimated effort: A small file for most flat-fare systems.