Feed status · checked 2026-09-13
Going-to-the-Sun Road Shuttle (Glacier National Park)
Based on the official feed source on file
Service mode Bus
unchanged since 2026-09-12
Catalogued in Montana.
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 30 hours ago; last changed 24 days ago.
Measured 3 of 4 score categories from the official feed URL on file.
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 official feed URL on file.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Publish the calendar for the current or next service period and set feed_info feed_end_date past it.Likely your export tool
This seasonal service has no published calendar. The last one ended 6 day(s) ago. Between service periods this is normal. But if buses are running with no published calendar, trip planners show nothing.
⏱ One export when the next period's schedule is set.worth about +50 points in its category
Schedule a feed re-export now so the new calendar is live well before the current one ends.Likely your export tool
This feed's service calendar runs out within the next 30 days. If a new feed isn't published before it ends, trip planners will drop your agency and riders will see no service.
⏱ Usually a re-export from your scheduling software.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
- This seasonal service has no published calendar. The last one ended 6 day(s) ago.
- Next action
- Publish the calendar for the current or next service period and set feed_info feed_end_date past it.
- 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
- This feed's service calendar runs out within the next 30 days.
- Next action
- Schedule a feed re-export now so the new calendar is live well before the current one ends.
- 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.
Publish the calendar for the current or next service period and set feed_info feed_end_date past it.
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.
Schedule a feed re-export now so the new calendar is live well before the current one ends. · Read the fix guide for feed_expiration_date30_days
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 was 6 days ago.
- 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.
Score by category
The MobilityData validator flagged 1 kind of issue across 1 instance (0 error, 1 warning, 0 informational).
This seasonal service's published calendar ended 6 day(s) ago. If the next service period is running, publish its calendar so riders can plan it.
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
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Apgar VC Boarding, West Side Logan Pass Shuttle Service, The Loop to Logan, West Side Logan Pass Shuttle Service, Lake McDonald Lodge Boarding, West Side Logan Pass Shuttle Service, Return West Side Logan Pass Shuttle Service).
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 ("St. Mary Visitor Center").
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 7 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.
- Return East Side Logan Pass Shuttle Service (yellow)
- Rising Sun Boarding, East Side Logan Pass Shuttle Service (yellow)
- St Mary VC Boarding, East Side Logan Pass Shuttle Service (yellow)
- Return West Side Logan Pass Shuttle Service (green)
- Apgar VC Boarding, West Side Logan Pass Shuttle Service (green)
- Lake McDonald Lodge Boarding, West Side Logan Pass Shuttle Service (green)
- The Loop to Logan, West Side Logan Pass Shuttle Service (green)
| Route | Type | Line color |
|---|---|---|
| Return East Side Logan Pass Shuttle Service | Bus | yellow |
| Rising Sun Boarding, East Side Logan Pass Shuttle Service | Bus | yellow |
| St Mary VC Boarding, East Side Logan Pass Shuttle Service | Bus | yellow |
| Return West Side Logan Pass Shuttle Service | Bus | green |
| Apgar VC Boarding, West Side Logan Pass Shuttle Service | Bus | green |
| Lake McDonald Lodge Boarding, West Side Logan Pass Shuttle Service | Bus | green |
| The Loop to Logan, West Side Logan Pass Shuttle Service | Bus | green |
List every stop
- Apgar Visitor Center
- Rising Sun Picnic Area
- St. Mary Visitor Center
- Lake McDonald Lodge
- The Loop (EB)
- The Loop (WB)
- Logan Pass
Over time
Overall score across the last 6 checks — unchanged since 2026-09-12.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-08-06 | 88.3 | first check |
| 2026-08-07 | 87.9 | down 0.4 |
| 2026-08-10 | 86.7 | down 1.2 |
| 2026-09-01 | 75.8 | down 10.9 |
| 2026-09-12 | 85.8 | up 10.0 |
| 2026-09-13 | 85.8 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed over time
On 2026-08-06 this feed started at grade B. On 2026-09-01 the grade moved from B to C. On 2026-09-12 the grade moved from C to B. On 2026-08-10 feed entered the expiry window (28 days of service left). As of 2026-09-13 it holds grade B.
A plain-language history of this feed, newest first.
- 2026-09-12 Grade went C to B, freshness rose 40 points.
- 2026-09-01 Grade went B to C, freshness fell 37 points.
- 2026-08-10 Feed entered the expiry window (28 days of service left).
Everything we checked
2 findings, ordered by severity.
Show every finding
- Warning1 instance
This feed's service calendar runs out within the next 30 days.
If a new feed isn't published before it ends, trip planners will drop your agency and riders will see no service.
Fix: Schedule a feed re-export now so the new calendar is live well before the current one ends. (Usually a re-export from your scheduling software.)
Finding code: feed_expiration_date30_days · Read the fix guide for feed_expiration_date30_days · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This seasonal service has no published calendar. The last one ended 6 day(s) ago.
Between service periods this is normal. But if buses are running with no published calendar, trip planners show nothing.
Fix: Publish the calendar for the current or next service period and set feed_info feed_end_date past it. (One export when the next period's schedule is set.)
Finding code: scorecard_intermittent_calendar_ended
NTD GTFS readiness Not ready
Resolve this before you certify on the D-10. Service data expired 6 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- Service data expired 6 days ago, so FTA would find the link out of date.
- 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 53 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 expired 6 days ago.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 6 days ago.
- 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.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks.
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 50 / 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/glacier-going-to-the-sun-road-shuttle/2026-09-13.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-09-13. 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.