TriMet, Portland Streetcar

What changed since the last check

• Correctness no change
• Freshness no change
• Rider experience no change

Top three things to fix

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.

   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.

   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.

   Effort: A few minutes in your scheduling software.

NTD certification readiness: Needs attention

This feed is close to NTD-ready. 1 validator error to resolve.

Published Ready

Published at a public URL.

Valid Needs attention

1 validator error to resolve.

Current Ready

Service data covers the next 149 days.

agency_id and NTD ID: Not checked yet. Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.

The bar this score answers to

The state transit-data program is Oregon ODOT Public Transportation. ODOT's Public Transportation Division, which supports statewide GTFS.

Key facts

Feed URL

http://developer.trimet.org/schedule/gtfs.zip

Last checked

2026-07-09

Service window

142 days of service data remain. Last service date 2026-11-28.

Feed version

20260531-20260701-2100

State

Oregon