Philly PHLASH

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

   645 of 661 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).

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

   Big gap in service (flagged by the MobilityData validator). See the linked rule for what this affects.

   Estimated effort: Varies.

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

3. Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras.

   Some files contain columns that are not part of the GTFS spec. Harmless to riders, but apps ignore these columns and they can hide typos in real column names.

   Estimated effort: A quick look at the flagged files.

This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.

Where this agency stands

Ahead of 99% of all tracked agencies, and ahead of 97% of small agencies nationwide.