Cotton Express and Central Arizona Regional Transit

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-12-31, 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-31. Your service calendar runs to 2025-12-31. 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_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.

   46 of 46 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

   Fixing this covers all 46 trips in the feed.

   Estimated effort: A default or per-trip field in your export.

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