Votran

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 1702 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. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

   2073 of 2073 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.

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

3. Ask your AVL vendor to check vehicle-to-trip assignments for the flagged trips.

   1 of 1 sampled vehicle positions were far from their assigned route (worst: 537 m). A bus shown off its route usually means a wrong trip assignment; riders watch their bus drive the wrong streets.

   Estimated effort: A vendor support ticket with the trip ids attached.