Link Transit

What changed since the last check

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

Top three things to fix

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

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

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

2. Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).

   2293 of 2293 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

   Effort: Often one default setting in your export.

   Agencies here usually clear this within about 1 week (based on 5 observed fixes).

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

   Stop too far from shape using user distance (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 6 observed fixes).

NTD certification readiness: Ready

This feed looks ready for your NTD certification: published at a public URL, valid, and current. The official check is still your D-10 certification.

Published Ready

Published at a public URL.

Valid Ready

Passes validation with no errors.

Current Ready

Service data covers the next 189 days.

agency_id and NTD ID: Not aligned. Your feed's agency_id is 0; your National Transit Database ID is 40252. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id, so a difference here is a heads-up, not an error. Optionally set the agency_id for your service to 40252 in agency.txt (and the matching agency_id in routes.txt) so the feed lines up with your NTD record. It is a convenience, not a required feed change: FTA also links agency_id to your NTD ID on your P-50 form.

The bar this score answers to

The state transit-data program is WSDOT Transportation Data. WSDOT builds and publishes GTFS for Washington transit agencies.

Key facts

Feed URL

https://link.rideralerts.com/InfoPoint/gtfs-zip.ashx

Last checked

2026-07-09

Service window

179 days of service data remain. Last service date 2027-01-04.

Feed version

20260629

State

Washington