Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
Spokane Transit Authority (STA)
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 88% of all tracked agencies and 97% of large agencies. Operates in Washington.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.1, validator 8.0.1.
Checked for changes 8 hours ago; last changed 3 days ago.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool
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.
⏱ Often a bulk fix in your scheduling software.worth about +6 points
Delete the empty calendars or set their service days.Likely your export tool
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.
⏱ A few minutes in your scheduling software.worth about +6 points
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.
⏱ Varies.worth about +6 points
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Delete the empty calendars or set their service days. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
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. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 8 kinds of issue across 87 instances (0 error, 77 warning, 10 informational).
Service data covers the next 72 days.
100% of stops state wheelchair accessibility (96% marked accessible, 4% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
100% of stops state accessibility (96% marked accessible). Reflects what the feed states, not verified physical usability.
Fares are applied to trips.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 1 (purple)
- 11 (green)
- 12 (green)
- 124 (pink)
- 14 (blue)
- 144 (pink)
- 173 (gray)
- 190 (gray)
- 20 (red)
- 21 (red)
- 22 (blue)
- 223 (pink)
- 23 (blue)
- 247 (pink)
- 25 (red)
- 27 (blue)
- 28 (red)
- 294 (pink)
- 31 (blue)
- 32 (blue)
- 33 (red)
- 34 (blue)
- 342 (green)
- 343 (green)
- 35 (blue)
- 36 (blue)
- 4 (red)
- 43 (blue)
- 45 (blue)
- 6 (gray)
- 61 (blue)
- 62 (blue)
- 63 (blue)
- 633 (pink)
- 65 (blue)
- 66 (gray)
- 661 (gray)
- 662 (gray)
- 663 (gray)
- 664 (gray)
- 68 (blue)
- 7 (gray)
- 722 (gray)
- 724 (gray)
- 771 (gray)
- 9 (red)
- 93 (blue)
- 94 (blue)
- 95 (blue)
- 96 (blue)
- 97 (blue)
- 98 (blue)
| Route | Type | Line color |
|---|---|---|
| 1 City Line | Bus | purple |
| 11 Downtown/North Bank Shuttle | Bus | green |
| 12 Southside Medical Shuttle | Bus | green |
| 124 North Express | Bus | pink |
| 14 South Adams/Napa | Bus | blue |
| 144 South Express | Bus | pink |
| 173 VTC Express | Bus | gray |
| 190 Valley Express | Bus | gray |
| 20 SFCC | Bus | red |
| 21 West Broadway | Bus | red |
| 22 NW Blvd | Bus | blue |
| 223 Shadle/Indian Trail | Bus | pink |
| 23 Maple/Ash | Bus | blue |
| 247 Lincoln Park/Ferris | Bus | pink |
| 25 Division | Bus | red |
| 27 Crestline | Bus | blue |
| 28 Nevada | Bus | red |
| 294 East 8th | Bus | pink |
| 31 Minnehaha/Lidgerwood | Bus | blue |
| 32 Trent/Montgomery | Bus | blue |
| 33 Wellesley | Bus | red |
| 34 Freya | Bus | blue |
| 342 Fairgrounds Shuttle | Bus | green |
| 343 Bureau Fair Shuttle | Bus | green |
| 35 Francis/Market | Bus | blue |
| 36 North Central | Bus | blue |
| 4 Monroe-Regal | Bus | red |
| 43 Lincoln/37th Ave | Bus | blue |
| 45 Perry District | Bus | blue |
| 6 Cheney | Bus | gray |
| 61 Highway 2/Fairchild | Bus | blue |
| 62 Medical Lake | Bus | blue |
| 63 Geiger/Airport | Bus | blue |
| 633 Geiger Shuttle | Bus | pink |
| 65 Airway Heights | Bus | blue |
| 66 EWU | Bus | gray |
| 661 EWU Express | Bus | gray |
| 662 EWU North Express | Bus | gray |
| 663 EWU VTC Express | Bus | gray |
| 664 EWU South Hill Express | Bus | gray |
| 68 Cheney Loop | Bus | blue |
| 7 Valley/Airport | Bus | gray |
| 722 Liberty Lake Express | Bus | gray |
| 724 Liberty Lake Tech Express | Bus | gray |
| 771 Mirabeau Express | Bus | gray |
| 9 Sprague | Bus | red |
| 93 Molter Loop | Bus | blue |
| 94 East Central/Millwood | Bus | blue |
| 95 Mid-Valley | Bus | blue |
| 96 Pines/Sullivan | Bus | blue |
| 97 South Valley | Bus | blue |
| 98 Greenacres/Liberty Lake | Bus | blue |
| T 1. Turnback | Bus | teal (no shape in feed) |
| T 11. Turnback | Bus | teal (no shape in feed) |
| T 12. Turnback | Bus | teal (no shape in feed) |
| T 124. Turnback | Bus | teal (no shape in feed) |
| T 144. Turnback | Bus | teal (no shape in feed) |
| T 173 Turnback | Bus | teal (no shape in feed) |
| T 190 Turnback | Bus | teal (no shape in feed) |
| T 20. Turnback | Bus | teal (no shape in feed) |
| T 21 Turnback | Bus | teal (no shape in feed) |
| T 23. Turnback | Bus | teal (no shape in feed) |
| T 25. Turnback | Bus | teal (no shape in feed) |
| T 27. Turnback | Bus | teal (no shape in feed) |
| T 28. Turnback | Bus | teal (no shape in feed) |
| T 31 Turnback | Bus | teal (no shape in feed) |
| T 4. Turnback | Bus | teal (no shape in feed) |
| T 45. Turnback | Bus | teal (no shape in feed) |
| T 6. Turnback | Bus | teal (no shape in feed) |
| T 60. Turnback | Bus | teal (no shape in feed) |
| T 61. Turnback | Bus | teal (no shape in feed) |
| T 62. Turnback | Bus | teal (no shape in feed) |
| T 633. Turnback | Bus | teal (no shape in feed) |
| T 66. Turnback | Bus | teal (no shape in feed) |
| T 661. Turnback | Bus | teal (no shape in feed) |
| T 68. Turnback | Bus | teal (no shape in feed) |
| T 7 Turnback | Bus | teal (no shape in feed) |
| T 722. Turnback | Bus | teal (no shape in feed) |
| T 724. Turnback | Bus | teal (no shape in feed) |
| T 74. Turnback | Bus | teal (no shape in feed) |
| T 771. Turnback | Bus | teal (no shape in feed) |
| T 9. Turnback | Bus | teal (no shape in feed) |
| T 94. Turnback | Bus | teal (no shape in feed) |
This feed has 1665 stops.
List every stop
- 10th @ Hayford
- 10th @ Hayden
- 10th @ Hayden
- 10th @ Lyons
- 10th @ Lyons
- 10th @ Madison
- 12th @ Hayford
- 12th @ Hayford
- 14th @ Adams
- 14th @ Adams
- 14th @ Lincoln
- 14th @ Lincoln
- 14th @ Madison
- 14th @ Madison
- 16th @ Evergreen
- 16th @ E. 14204
- 16th @ 14210 E
- 16th @ Adams
- 16th @ Adams
- 16th @ Progress
- 16th @ Progress
- 17th @ Cook
- 17th @ Cook
- 17th @ Fiske
- 17th @ Fiske
- 17th @ Madelia
- 17th @ Madelia
- 18th @ Freya
- 18th @ Freya
- 18th @ Hogan
- 18th @ Hogan
- 18th @ Ray
- 1st @ W 800
- 1st @ Adams
- 1st @ Adams
- 1st @ A Street
- 1st @ Buena Vista
- 1st @ Calispel
- 1st @ Cheney Spokane
- 1st @ College Hill
- 1st @ D Street Cheney Library
- 1st @ G Street
- 1st @ Jefferson
- 1st @ Monroe
- 1st @ Pine
- 1st @ Union
- 1st @ Vine
- 1st @ Washington
- 29th @ Arthur
- 29th @ Arthur
- 29th @ Bernard
- 29th @ Bernard
- 29th @ Division
- 29th @ Division
- 29th Av @ Garfield St (Manito Center)
- 29th @ Grand
- 29th @ Hatch
- 29th @ Martin
- 29th @ Martin
- 29th @ Perry
- 29th @ Pinecrest
- 29th @ Pittsburg
- 29th @ Pittsburg
- 29th @ Post
- 29th @ Post
- 29th @ Ray
- 29th @ Ray
- 29th @ Regal
- 29th @ Regal
- 29th @ Rosauers
- 29th @ Rosauers
- 29th @ Southeast
- 29th @ Stone
- 29th @ Thor
- 29th @ Thor
- 2nd @ Arthur
- 2nd @ Browne
- 2nd @ Cowley
- 2nd @ Hatch
- 2nd @ Jefferson
- 2nd @ Maple
- 2nd @ Monroe
- 2nd @ Post
- 2nd @ Sherman
- 2nd @ Spruce
- 2nd @ Washington
- 32nd @ Bowdish
- 32nd @ Bowdish
- 32nd @ Clinton
- 32nd @ Clinton
- 32nd @ Collins
- 32nd @ Collins
- 32nd @ Fox
- 32nd @ Fox
- 32nd @ SR 27
- 32nd @ Mamer
- 32nd @ Mamer
- 32nd @ Pierce
- 32nd @ Pierce
- 32nd @ Pines (U High)
- 32nd @ Pines (U High)
- 32nd @ University
- 32nd @ University
- 32nd @ Woodlawn
- 32nd @ Woodlawn
- 37th @ Arthur
- 37th @ Arthur
- 37th @ Bernard
- 37th @ Bernard
- 37th @ Cook
- 37th @ Cook
- 37th @ Crestline
- 37th @ Crestline
- 37th @ Grand
- 37th @ Grand
- 37th @ Hatch
- 37th @ Helena
- 37th @ Helena
- 37th @ Latawah
- 37th @ Manito
- 37th @ Manito
- 37th @ Perry
- 37th @ Perry
- 37th @ Pittsburg
- 37th @ Pittsburg
- 37th @ Regal
- 37th @ Regal
- 37th @ Regal
- 37th @ Skyview
- 37th @ Skyview
- 3rd @ Arthur
- 3rd @ Cedar
- 3rd @ Cowley
- 3rd @ Jefferson
- 3rd @ Liberty Park Pl.
- 3rd @ Maple
- 3rd & Pine
- 3rd @ Sherman
- 3rd @ Sprague
- 3rd @ Washington
- SR 904 @ 1st (Four Lakes)
- SR 904 @ 1st (Four Lakes)
- 4th @ Cowley
- 4th @ Minnie
- 4th @ Pittsburg
- 57th @ Freya
- 57th @ Crestline
- 57th @ Crestline
- 57th @ Freya
- 57th @ Hailee
- 57th @ Hailee
- 57th @ Perry
- 57th @ Perry
- 57th E @ Regal
- 57th @ Regal
- 5th @ McClellan
- 5 Mile Park & Ride
- 5th @ Bernard
- 5th @ Browne
- 5th @ Browne
- 5th @ Deaconess Hospital
- 5th @ Division
- 5th @ Florida
- 5th @ Florida
- 5th @ Freya
- 5th @ Freya
- 5th @ Greene
- 5th @ Greene
- 5th @ Haven
- 5th @ Haven
- 5th @ Jefferson
- 5th @ Jefferson
- 5th @ McClellan
- 5th @ Monroe
- 5th @ Monroe
- 5th @ Rebecca
- 5th @ Rebecca
- 5th @ Smith
- 5th @ Smith
- 5th @ Stone
- 5th @ Stone
- 5th @ Thor
- 5th @ Thor
- 6th @ Cheney High School
- 6th @ Aspen
- 6th @ Aspen
- 6th @ Bernard
- 6th @ Betz
- 6th @ Betz
- 6th @ Elm
- 6th @ Elm
- 6th @ Golden Hills
- 6th @ Golden Hills
- 6th @ Ketchum
- 6th @ Ketchum
- 6th @ Lawson
- 6th @ Lawson
- 6th @ Lundstrom
- 6th @ Lundstrom
- 6th @ McKeehan
- 6th @ Oak
- 6th @ Oak
- 6th @ Simpson Parkway
- 6th @ Solar
- 6th @ Solar
- 6th @ Stevens
- 6th @ Stevens
- 6th @ Washington
- 6th @ Washington
- 7th @ Browne (Heart Institute)
- 7th @ Browne
- 8th @ 6th
- 8th @ 6th
- 8th @ Carnahan
- 8th @ Carnahan
- 8th @ Coleman
- 8th @ Coleman
- 8th @ Cowley
- 8th @ Cowley
- 8th @ Custer
- 8th @ Custer
- 8th @ Eastern
- 8th @ Eastern
- 8th @ Havana
- 8th @ McClellan
- 8th @ McClellan
- 8th @ McKinnion
- 8th @ McKinnon
- 8th @ Park
- 8th @ Park
- 8th @ Thierman
- 8th @ Thierman
- 8th @ Woodlawn
- 8th @ Woodlawn
- 9th @ McClellan
- Adams @ 10th
- Adams @ 6th
- Adams @ 6th
- Adams @ 8th
- Addison @ Francis
- Addison @ Francis
- Addison @ Francis
- Addison @ Longfellow
- Addison @ Longfellow
- Addison @ Lyons
- Addison @ Lyons
- Addison @ Lyons
- Addison @ Walton
- Addison @ Walton
- Airway Heights Correctional Center
- and 1415 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 21 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 82.5 | first check |
| 2026-06-20 | 82.5 | no change |
| 2026-06-21 | 82.5 | no change |
| 2026-06-22 | 82.5 | no change |
| 2026-06-23 | 82.5 | no change |
| 2026-06-24 | 82.5 | no change |
| 2026-06-25 | 82.5 | no change |
| 2026-06-26 | 82.5 | no change |
| 2026-06-27 | 82.5 | no change |
| 2026-06-28 | 82.4 | down 0.1 |
| 2026-06-29 | 82.5 | up 0.1 |
| 2026-06-30 | 82.4 | down 0.1 |
| 2026-07-01 | 82.4 | no change |
| 2026-07-02 | 82.4 | no change |
| 2026-07-03 | 82.4 | no change |
| 2026-07-04 | 82.4 | no change |
| 2026-07-05 | 82.5 | up 0.1 |
| 2026-07-06 | 82.4 | down 0.1 |
| 2026-07-07 | 82.4 | no change |
| 2026-07-08 | 82.4 | no change |
| 2026-07-09 | 82.4 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-08.
Same feed file as 2026-07-08; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
- Warning43 instances
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.
Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning21 instances
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.
Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)
Validator rule: service_has_no_active_day_of_the_week · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning9 instances
Stop too far from shape using user distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: 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. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some service calendars in the feed have already ended.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Missing feed contact email and url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Agencies here usually clear this within about 2 weeks (based on 8 observed fixes).
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some trips serve fewer than two stops.
A trip with one stop can't be ridden; planners ignore it and it may signal an export problem.
Fix: Check the flagged trips in your scheduling software; remove them or restore their missing stops. (Worth a vendor question if it appears often.)
Validator rule: unusable_trip · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info10 instances
Big gap in service (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'big_gap_in_service' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 13 observed fixes).
Validator rule: big_gap_in_service · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs have nobody to email when they spot a problem with your feed, so problems linger.
Fix: Add feed_contact_email to feed_info.txt. (One field.)
Agencies here usually clear this within about 1 week (based on 10 observed fixes).
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
The feed publishes fare products but no rider_categories.txt defining who qualifies for each fare.
Consider: Add rider_categories.txt for the fares you already offer, then reference those categories from your fare products.
1596 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Washington @ North River Drive", "5th @ Deaconess Hospital", "6th @ Stevens", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Some fixes we can make for you
These are the safe mechanical fixes, applied to a copy of your feed. They change only what is certain and leave everything else untouched. Review the diff before you publish.
Trimmed surrounding whitespace 28 changes
For example: 'stop_desc': '0 ' -> '0'
Recased shouting route names 1 change
For example: SFCC -> Sfcc
Run it yourself on your own copy of the feed: scorecard autofix <feed.zip> --out corrected.zip
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 72 days.
- agency_id matches your 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.
- shapes.txt covers your trips Ready
- All 8396 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Awarded
This feed earns the conformance mark: valid, current, and stating wheelchair access on nearly every stop and trip.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 72 days.
- Accessible Met
- States wheelchair access on 100% of stops and 100% of trips.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 1 of 8396 trips list fewer than two stops. A trip with one stop has no leg a rider can ride; trip planners can't route anyone on it, so the service effectively does not exist. Check your scheduling export: every trip should list each stop it calls at, in order, with times.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Clears the Google and Apple Maps four-week coverage bar. This feed has 72 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
How this agency maps to the standards
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.
Your state runs a transit-data program that can help: WSDOT Transportation Data. WSDOT builds and publishes GTFS for Washington transit agencies. Your state publishes no quality rubric of its own, so the closest published bars a program can hold this feed to are the federal and industry ones below; the score maps to those.
- Correctness 65 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 100 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 92 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a live badge on your agency site or feed README. It updates daily and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/spokane-transit-authority-sta/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.