Sound Transit, Metro Transit, City of Seattle - King County Metro

What changed since the last check

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

Top three things to fix

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

   This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

   Effort: A few minutes in your scheduling software.

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

   Route short name too long (flagged by the MobilityData validator). See the linked rule for what this affects.

   This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

   Effort: Varies.

3. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

   47 of 6265 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.

   Fixing this covers 47 of 6,265 stops, under 1% of them.

   Effort: A column in stops.txt; your scheduling software likely has it.

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 170 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 WSDOT Transportation Data. WSDOT builds and publishes GTFS for Washington transit agencies.

Key facts

Feed URL

http://metro.kingcounty.gov/GTFS/google_transit.zip

Last checked

2026-10-07

Service window

170 days of service data remain. Last service date 2027-12-31.

Feed version

FAL26-161.2

Location

Washington