The Current

What this grade measures

The quality of the schedule data this agency publishes 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, and set feed_info feed_end_date past your next service change.

   Service data ended 1712 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.

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

2. Re-generate shape distances in your export; flag to your vendor if it persists.

   Some trips have stop times whose distances along the route go backwards. Apps can show buses jumping backwards or mis-order stops.

   Estimated effort: Usually an export-tool fix, not hand editing.

3. Add the required column named in the finding to the flagged file.

   A file is missing a column that GTFS requires. Apps may reject the whole file, so riders could lose the affected routes or stops.

   Estimated effort: Often an export setting; ask your vendor if it recurs.

Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.