GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-08-02

Yakima Transit

Grade F · 28.4 / 100

Unchanged since 2026-08-01.

For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. Each fix is framed as a next step, not a failure.

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 'stop_time_with_arrival_before_previous_departure_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Stop time with arrival before previous departure time (flagged by the MobilityData validator). See the linked rule for what this affects.

    Effort: Varies.

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

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

  3. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.

    327 of 327 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: A default or per-trip field in your export.

Finding handoff

Move one finding to a recheck

Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.

Feed evidence
Stop time with arrival before previous departure time (flagged by the MobilityData validator).
Next action
Review the rule documentation for 'stop_time_with_arrival_before_previous_departure_time' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Recheck
Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text

NTD GTFS readiness: Not ready

Resolve this before you certify on the D-10. 1 validator error to resolve. agency.txt has no nonblank agency_id. Every RY2026 NTD GTFS submission needs a stable value unique among the reporters represented in the feed, crosswalked to each reporter's NTD ID on the P-50 form.

Published Ready
Published at a public URL.
Valid Needs attention
1 validator error to resolve.
Current Ready
Service data covers the next 3438 days.
agency_id provided Not ready
agency.txt has no nonblank agency_id. Every RY2026 NTD GTFS submission needs a stable value unique among the reporters represented in the feed, crosswalked to each reporter's NTD ID on the P-50 form.

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
https://yakimatransit.org/gtfs/yakima_gtfs.zip
Last checked
2026-08-02
Service window
3438 days of service data remain. Last service date 2035-12-31.
Location
Washington

Part of the Washington portfolio: see where this agency sits among the state's feeds before the call.

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.3, validator 8.0.1.