GTFS Scorecard

← Back to the full scorecard

Call-prep brief · checked 2026-07-09

Spokane Transit Authority (STA)

Grade B · 82.4 / 100

Unchanged since 2026-07-08.

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

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

  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

Published at a public URL, valid, and current: the three things the NTD GTFS requirement asks of a feed all hold here. Only your own D-10 certification makes 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 76 days.

agency_id and NTD ID: Not checked yet. Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.

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://www.spokanetransit.com/gtfs
Last checked
2026-07-09
Service window
72 days of service data remain. Last service date 2026-09-19.
Feed version
MAY2026v3_20260521
State
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.1, validator 8.0.1.