Feed status · checked 2026-10-17
Giant Forest Shuttle (Sequoia National Park)
Based on the official feed source on file
Service mode Bus
unchanged since 2026-10-16
Cataloged in California.
Source feed: https://www.nps.gov/external-resources/gtfs/seki/giant-forest-shuttle.zip
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.4, validator 8.0.1.
Checked for changes 35 minutes ago; last changed 57 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.
About this feed
Giant Forest Shuttle (Sequoia National Park)’s published feed lists 5 bus routes, 278 scheduled trips and 15 stops. Its service dates run from 2026-05-22 through 2026-09-07. The published file last changed on 2026-08-21.
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 40 day(s) ago. Between service periods this is normal. But if buses are running with no published calendar, trip planners show nothing.
This one is about the feed as a whole, so there is no share of it to count.
⏱ One export when the next period's schedule is set.worth about +50 points in its category
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
4 of 15 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 4 of 15 stops, about 27% of them.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +7 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.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
⏱ Usually a re-export from your scheduling software.worth about +4 points in its category
Riders and need behind these fixes
- This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
- California 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-10-12.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
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.
- Finding
- Fix 01 in Top things to fix: its feed evidence and the requested change.
- 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
- Finding
- Fix 02 in Top things to fix: its feed evidence and the requested change.
- 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
- Finding
- Fix 03 in Top things to fix: its feed evidence and the requested change.
- 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.
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.
Fix 02 · Read the fix guide for scorecard_wheelchair_boarding_unknown
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.
Fix 03 · 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 40 days ago.
- Published accessibility data
- Accessibility information is stated for 73.3% 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 40 day(s) ago. If the next service period is running, publish its calendar so riders can plan it.
73% of stops state wheelchair accessibility (73% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
73% of stops state accessibility (73% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Route 2 (Grey)).
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.
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 15 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.
- Route 1 (Green) (green)
- Route 2 (Grey) (gray)
- Route 3 (Purple) (purple)
- Route 4 (Orange) (yellow)
- Sequoia Shuttle (teal)
| Route | Type | Line color |
|---|---|---|
| Route 1 (Green) | Bus | green |
| Route 2 (Grey) | Bus | gray |
| Route 3 (Purple) | Bus | purple |
| Route 4 (Orange) | Bus | yellow |
| Sequoia Shuttle | Bus | teal |
List every stop
- Crescent Meadow
- Three Rivers Historical Museum
- Lemon Cove Village RV Park
- Visalia Transit Center
- Visalia Convention Center-Comfort Suites
- Moro Rock
- La Quinta Inn and Suites
- Wyndham Hotel
- Giant Forest Museum
- Sherman Tree Trailhead
- Sherman Tree Parking Lot
- Wolverton
- Lodgepole Market and Visitor Center
- Lodgepole Campground
- Wuksachi Lodge and Restaurant
Over time
Overall score across the last 16 checks — unchanged since 2026-10-16.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-10-02 | 83.7 | first check |
| 2026-10-03 | 83.7 | no change |
| 2026-10-04 | 83.7 | no change |
| 2026-10-05 | 83.7 | no change |
| 2026-10-06 | 83.7 | no change |
| 2026-10-07 | 83.7 | no change |
| 2026-10-08 | 83.7 | no change |
| 2026-10-09 | 83.7 | no change |
| 2026-10-10 | 83.7 | no change |
| 2026-10-11 | 83.7 | no change |
| 2026-10-12 | 83.7 | no change |
| 2026-10-13 | 83.7 | no change |
| 2026-10-14 | 83.7 | no change |
| 2026-10-15 | 83.7 | no change |
| 2026-10-16 | 83.7 | no change |
| 2026-10-17 | 83.7 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Feed history
Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-10-02 to 2026-10-17 (16 checks) | e22947303ad4 | 2026-09-07 | Current rubric: see the trend above |
| 2026-08-21 to 2026-10-01 (38 checks) | e22947303ad4 | 2026-09-07 | B, 83.7 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-25 to 2026-08-20 (27 checks) | 91508d260fb8 | 2026-09-07 | C, 76 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-19 to 2026-07-24 (4 checks) | 91508d260fb8 | 2026-09-07 | B, 87.3 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
What changed in this feed
Overall grade and score held steady since 2026-10-16.
Same feed file as 2026-10-16; 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.
Everything we checked
3 findings, ordered by severity.
Show every finding
- Warning4 instances
4 of 15 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- 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 40 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 40 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 40 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 278 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
Two requirements remain for this feed to earn the conformance mark. Service data expired 40 days ago. States wheelchair access on 73% of stops and 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 40 days ago.
- Accessible Not yet
- States wheelchair access on 73% 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.
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.
In California, the published guideline is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.
California Minimum GTFS Guidelines checklist (5 of 6 measured items met)
The state's own Data Process Checklist, matched item by item to what this scorecard already measures. An item marked "not measured here" is real ground the checklist covers that this tool does not check; see the official checklist for the full picture.
- Meets Publish GTFS Schedule at a stable, automatically-fetchable URL
The published feed URL downloaded at the last check.
- Not measured here Implement required fields: Fares v2, text-to-speech stop names, shapes.txt, wheelchair_boarding, and Pathways where applicable
This scorecard measures wheelchair_boarding, shapes.txt coverage, fare data, and station pathways separately, below; it does not check the Fares v2 format specifically or text-to-speech stop names.
- Not measured here Achieve a passing score in every category of the MobilityData GTFS Grading Scheme v1
This scorecard automates a proxy for the Grading Scheme's rider-facing fields (see the standards crosswalk) rather than running the scheme itself, which grades by comparison to the real world by hand.
- Not measured here Publish changes to the base schedule at least one week ahead of every service change
This scorecard does not track a feed's publish history, so advance notice cannot be checked.
- Meets Produce no critical errors in the MobilityData GTFS Validator
Passes validation with no errors.
- Not measured here Publish Trip Updates, Vehicle Positions, and Alerts feeds
This scorecard checks realtime reachability and freshness overall; it does not check for all three feed types individually.
- Not measured here Update Trip Updates and Vehicle Positions at least every 20 seconds
This scorecard samples realtime freshness; it does not check this specific 20-second cadence.
- Not measured here Publish information for at least 99% of vehicles in service
This scorecard measures the share of scheduled trips represented in TripUpdates, a related but different figure than vehicle coverage.
- Not measured here Keep 100% of trip_ids consistent between Schedule and Realtime
This scorecard does not currently check trip_id consistency between the Schedule and Realtime feeds.
- Not measured here Produce no critical errors in the Center for Urban Transportation Research realtime validator
This scorecard does not run the CUTR realtime validator.
- Not measured here Publish accessible feed links on the agency or regional partner website
This scorecard does not check the agency's own website.
- Not measured here Register GTFS and GTFS-Realtime feeds with transit.land and the Mobility Database
This scorecard does not currently check aggregator registration for this section.
- Meets Designate a technical contact in feed_info.txt's feed_contact_email
feed_info.txt states a technical contact.
- Gap wheelchair_boarding stated on stops and trips
States wheelchair access on 73% of stops and 100% of trips.
- Meets shapes.txt with a shape for every trip
All 278 trips have a shape in shapes.txt.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- 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 93 / 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.
Part of the California portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in California
Other scorecards in California, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
Show your grade
Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.
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/giant-forest-shuttle/2026-10-17.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-10-17. 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.