TriMet, Portland Streetcar

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. Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Block trips with overlapping stop times (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 5 observed fixes).

2. Populate trip_headsign to match what the bus displays.

   93055 of 93055 trips have no headsign. Riders at the stop can't tell which direction a bus is going.

   Estimated effort: Usually a bulk edit in your scheduling software.

3. Delete the empty calendars or set their service days.

   Some service calendars have no days of the week switched on. Trips tied to these calendars never run; they are dead data that can mask real schedule problems.

   Estimated effort: A few minutes in your scheduling software.

Where this agency stands

Ahead of 61% of all tracked agencies, and ahead of 76% of large agencies nationwide.