Pasadena Transit

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:

• Many of the feed's trips don't run at all in the next 7 days.

What needs attention next

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

1. Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.

   The vehicle positions 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.

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

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

   446 of 446 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).

   1038 of 1038 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).

Where this agency stands

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