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. 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.

   50966 of 50966 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.

2. Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').

   Some rider-facing names are in ALL CAPS or all lowercase. ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.

   Effort: Often a bulk fix in your scheduling software.

3. Give each route a distinct short or long name.

   Two or more routes share the same name. Riders can't tell the routes apart in apps.

   Effort: One field per route.

NTD GTFS readiness: Ready

Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.

Published Ready

Published at a public URL.

Valid Ready

Passes validation with no errors.

Current Ready

Service data covers the next 97 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-23

Service window

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

Feed version

20260719-20260814-0900

Location

Oregon