Via Mobility

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

Since the previous check, 1 data issue was fixed and verified:

• 8 of 13 trips scheduled during the sampling window had no live predictions.

What needs attention next

Three improvements, in priority order, each sized so the board can see what it is approving:

1. Review the rule documentation for 'empty_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Empty file (flagged by the MobilityData validator). See the linked rule for what this affects.

   Estimated effort: Varies.

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

   169 of 169 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. Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).

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

   Estimated effort: Often one default setting in your export.

   Agencies here usually clear this within about 1 week (based on 5 observed fixes).

This feed is generated by your Passio system from the route and stop data they maintain. Send the fix list to your Passio contact.

Where this agency stands

Ahead of 58% of all tracked agencies, and ahead of 56% of mid-size agencies nationwide.