Board packet · transit data quality · checked 2026-11-09
RIDE Sitka
Grade C · 70.6 / 100 · partial: freshness not measured
The scoring methodology changed since the prior check; the trend restarts here without an improvement or regression claim.
Scored from a Mobility Database mirror copy downloaded on 2026-10-19, because the feed URL on file could not be downloaded. Service dates in that copy end 2021-12-31. It may not match the feed the agency publishes today.
What this grade measures
The quality of the schedule data in the feed scored here for trip-planning apps: whether riders using Google Maps, Apple Maps, or Transit see current, correct, and complete information. It measures the data feed, not service quality or operations.
Progress this period
No newly cleared items this period. The score and trend above reflect the mirror copy described above, which may not match the feed the agency publishes today.
What needs attention next
Three improvements, in priority order, each sized so the board can see what it is approving:
Check that https://transitfeeds.com/p/ride-sitka/713/latest/download still serves your current feed. If the feed moved, publish the new address.
The feed URL on file, https://transitfeeds.com/p/ride-sitka/713/latest/download, could not be downloaded: the server answered with an error instead of the file. Trip planners download the feed from that address too. The grade here was measured on an older Mobility Database copy whose service ended 2021-12-31, so freshness is not graded until the current feed can be downloaded.
This one is about the feed as a whole, so there is no share of it to count.
Estimated effort: Usually a server or hosting setting, not a change to the feed itself.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
52 of 52 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.
Fixing this covers all 52 stops in the feed.
Estimated effort: A column in stops.txt; your scheduling software likely has it.
Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
This one is about the feed as a whole, so there is no share of it to count.
Estimated effort: A small file for most flat-fare systems.
Riders and need behind these fixes
- This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
- Alaska as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-11-02.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
This feed URL points at the TransitFeeds archive, which is no longer maintained. Before any single fix, publish the feed from a live URL you control and update the listings that still point here.
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
- The feed URL on file, https://transitfeeds.com/p/ride-sitka/713/latest/download, could not be downloaded: the server answered with an error instead of the file.
- Next action
- Check that https://transitfeeds.com/p/ride-sitka/713/latest/download still serves your current feed. If the feed moved, publish the new address.
- 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
- 52 of 52 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
- The feed contains no fare information.
- Next action
- Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.
- 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
Produced by the GTFS Scorecard, an open-source data quality tool. A data-quality read to support the board conversation, not an official compliance determination. Live scorecard: https://gtfsscorecard.org/agency/ride-sitka/. Rubric v1.4, validator 8.0.1.