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.

2. Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign.

   70557 of 70557 trips lack rider-facing destination or direction text. When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

   Effort: Usually one value per route pattern in your scheduling source.

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 GTFS 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 119 days.

agency_id provided Ready

agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.

agency_id equals NTD ID (optional): Not checked yet. This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.

The bar this score answers to

A local transit-data support resource 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-08-01

Service window

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

Feed version

20260705-20260713-2100

Location

Oregon