Feed status · checked 2026-08-23
South Rim Shuttle
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
down 0.4 since 2026-08-22
Catalogued in Arizona.
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 89 minutes ago; last changed 62 days ago.
Measured 3 of 4 score categories from the feed URL on file (publisher not verified).
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 configured feed URL. Publisher ownership of that URL is not verified.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Re-export with a validity window that reaches at least 60 days out.Likely your export tool
Service data runs out in 19 day(s). When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
⏱ One export setting.worth about +61 points in its category
Remove past service periods the next time you export the feed.Likely your export tool
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.
⏱ One setting in most export tools.worth about +4 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
- Service data runs out in 19 day(s).
- Next action
- Re-export with a validity window that reaches at least 60 days out.
- 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 in the feed have already ended.
- Next action
- Remove past service periods the next time you export the 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
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.
Re-export with a validity window that reaches at least 60 days out. · 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. Self-check a feed before you publish.
Remove past service periods the next time you export the feed. · 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. Self-check a feed before you publish.
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 19 days.
- Published accessibility data
- Accessibility information is stated for 100% 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 v1.
- 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.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 1 kind of issue across 1 instance (0 error, 1 warning, 0 informational).
Service data runs out in 19 day(s). Publish an updated feed soon or riders will lose trip planning.
100% of stops state wheelchair accessibility (100% marked accessible, 0% 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 (100% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Kaibab Rim (Orange)).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
1 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("IMAX Theatre / R.P.'s Stage").
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 36 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.
- Hermits Rest (Red) (red)
- Hikers' Express (white)
- Kaibab Rim (Orange) (orange)
- Tusayan (Purple) (purple)
- Village (Blue) (blue)
| Route | Type | Line color |
|---|---|---|
| Hermits Rest (Red) | Bus | red |
| Hikers' Express | Bus | white |
| Kaibab Rim (Orange) | Bus | orange |
| Tusayan (Purple) | Bus | purple |
| Village (Blue) | Bus | blue |
List every stop
- Grand Canyon Visitor Center
- Village East
- Shrine of the Ages Eastbound
- Mather Campground
- Trailer Village
- Market Plaza Eastbound
- South Kaibab Trailhead
- Yaki Point
- Pipe Creek Vista
- Mather Point
- Yavapai Point Geology Museum
- Market Plaza Westbound
- Village Route Transfer
- Trailview Overlook
- Maricopa Point
- Powell Point Westbound
- Hopi Point
- Mohave Point Westbound
- The Abyss
- Monument Creek Vista
- Pima Point Westbound
- Hermits Rest
- Shrine of the Ages Westbound
- Pima Point Eastbound
- Mohave Point Eastbound
- Powell Point Eastbound
- IMAX Theatre / R.P.'s Stage
- Best Western Grand Canyon Squire Inn
- The Grand Hotel
- Big E Steakhouse and Saloon
- Train Depot
- Bright Angel Lodge
- Hermits Rest Transfer
- Maswik Lodge
- Backcountry Info Center
- Center Road
Over time
Overall score across the last 4 checks — down 0.4 since 2026-08-22.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 88.2 | first check |
| 2026-08-07 | 87.8 | down 0.4 |
| 2026-08-22 | 81.6 | down 6.2 |
| 2026-08-23 | 81.2 | down 0.4 |
What changed since your last check
- Correctness no change
- Freshness down 1.6
- Rider experience no change
What changed in this feed
Overall score fell 0.4 points since 2026-08-22.
Same feed file as 2026-08-22; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops and export changes in a reader, with no sign-up.
What changed over time
On 2026-08-06 this feed started at grade B. On 2026-08-22 feed entered the expiry window (20 days of service left). As of 2026-08-23 it holds grade B.
A plain-language history of this feed, newest first.
- 2026-08-22 Feed entered the expiry window (20 days of service left).
Everything we checked
2 findings, ordered by severity.
Show every finding
- 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.)
Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Service data runs out in 19 day(s).
When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.
Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)
Finding code: scorecard_feed_expiring_soon · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
NTD GTFS readiness Needs attention
This feed is close to NTD-ready. Service data runs out in 19 days; renew before you certify.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Needs attention
- Service data runs out in 19 days; renew before you certify.
- 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 245 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
One requirement remains for this feed to earn the conformance mark. Service data runs out in 19 days; renew to qualify.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data runs out in 19 days; renew to qualify.
- 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.
At risk for the Google and Apple Maps four-week coverage bar. This feed has 19 days of service left. Maps needs at least four weeks (28 days) of upcoming service, so your agency will fall out of trip planners soon. Re-export with a longer calendar.
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.
- Correctness 96 / 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 32 / 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 100 / 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/grand-canyon-national-park/2026-08-23.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-23. 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.