Trinity 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

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

   70 of 73 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.

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

   Trip distance exceeds shape distance below threshold (flagged by the MobilityData validator). See the linked rule for what this affects.

   Estimated effort: Varies.

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

   Stop too far from shape using user distance (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 6 observed fixes).

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.

Where this agency stands

Ahead of 96% of all tracked agencies, and ahead of 94% of small agencies nationwide.