South Portland

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 300 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. Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.

   The trip updates realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.

   Estimated effort: Usually a vendor support ticket.

3. Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.

   The service alerts realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.

   Estimated effort: Usually a vendor support ticket.

This feed is exported from Remix. The change happens in your Remix workspace; once your planners update the data there, the published export picks it up.