Feed status · checked 2026-08-01
Spokane Transit Authority (STA)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Washington.
Heads-up: Days until the service window ends dropped by 124 between 2026-07-25 and 2026-07-30, but only 5 day(s) passed. The feed's calendar appears to have moved backward, which can happen when an older export is republished. Worth confirming the latest export is the one being served. (checked 2026-07-30). This can be a brief vendor export glitch; watch the next update before acting.
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.3, validator 8.0.1.
Checked for changes 9 hours ago; last changed 9 hours 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
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
1689 of 1689 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.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
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 +8 points in its category
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 in its category
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
- 1689 of 1689 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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
- Feed evidence
- Some rider-facing names are in ALL CAPS or all lowercase.
- Next action
- Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
- 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
- Feed evidence
- Some service calendars have no days of the week switched on.
- Next action
- Delete the empty calendars or set their service days.
- 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
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
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.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
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.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. See this feed's finding-clearance log.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 168 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v2.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
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 156 instances (0 error, 137 warning, 19 informational).
Service data covers the next 168 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
1620 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Appleway @ Vista", "Ash @ Indiana", "37th @ Grand", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, 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.
This feed has 1689 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: 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) |
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 @ Stone
- 5th @ Thor
- 5th @ Thor
- 6th @ Cheney High School
- 6th @ Ash
- 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
- 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 @ Dearborn
- 8th @ Dearborn
- 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
- and 1439 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 73.8 | first check |
| 2026-07-30 | 78.7 | up 4.9 |
| 2026-07-31 | 73.8 | down 4.9 |
| 2026-08-01 | 73.8 | 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-31.
Same feed file as 2026-07-31; the published zip did not change.
What changed inside the export
- 24 new stops appeared.
- The export now has 15,677 trips, 7,281 more than before.
- Service now runs through 2027-01-16 (was 2026-09-19).
Read from the feed file itself, compared with the previous export. A service change is normal; this is a heads-up so nothing disappears silently.
Changed counts
- down Some service calendars in the feed have already ended. (5 → 3) (expired_calendar)
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
What changed over time
On 2026-07-25 this feed started at grade C. On 2026-08-01 the grade held steady. As of 2026-08-01 it holds grade C.
A plain-language history of this feed, newest first.
- 2026-07-31 Score fell 5 points, rider experience fell 25 points.
- 2026-07-30 Score rose 5 points, rider experience rose 25 points.
Everything we checked
10 findings, ordered by severity.
Show every finding
- Warning1689 instances
1689 of 1689 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.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning75 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.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning36 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.)
Finding code: 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)
- Warning18 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: 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)
- Warning3 instances
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.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning3 instances
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.)
Finding code: unusable_trip · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: 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.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info19 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide · 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).
Trip-planning apps and regional data coordinators 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.)
Finding code: 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.
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 168 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 your 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.
- shapes.txt covers your trips Ready
- All 15677 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, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
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). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also 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 Not yet
This feed is close to the conformance mark. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 168 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.
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.
- 3 of 15677 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 168 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
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
A local transit-data support resource is WSDOT Transportation Data. WSDOT builds and publishes GTFS for Washington transit agencies. This resource supports agencies; it is not a scoring authority.
- Correctness 63 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
- Freshness 100 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
- Rider experience 68 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers 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 badge on your agency site or feed README. It updates after each completed scoring check 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-08-01.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-08-01. Use it in a board packet, a regulatory filing, 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.