Call-prep brief · checked 2026-08-01

Mariposa Grove Shuttle (Yosemite National Park)

Grade A · 97.8 / 100

Unchanged since 2026-07-31.

For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. Each fix is framed as a next step, not a failure.

What changed since the last check

Correctness no change
Freshness no change
Rider experience no change

Top three things to fix

Delete the empty calendars or set their service days.
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.
Effort: A few minutes in your scheduling software.
Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Service extends far in the future (flagged by the MobilityData validator). See the linked rule for what this affects.
Effort: Varies.
Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside.
Some service dates fall outside the date window set in feed_info.txt. feed_info.txt should span every day your service runs, so apps know when the data applies.
Effort: Two fields in feed_info.txt, or one export setting.

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: 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

Agency: Mariposa Grove Shuttle (Yosemite National Park)
Finding: service_has_no_active_day_of_the_week
Feed evidence: Some service calendars have no days of the week switched on.
Why it matters: Trips tied to these calendars never run; they are dead data that can mask real schedule problems.
Requested change: 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.
Evidence: https://gtfsscorecard.org/agency/mariposa-grove-shuttle/?finding=service_has_no_active_day_of_the_week#finding-handoff

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 257 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 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.

The bar this score answers to

The published guideline in is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.

Key facts

Feed URL: https://www.nps.gov/external-resources/gtfs/yose/mariposa-grove-shuttle-service.zip
Last checked: 2026-08-01
Service window: 257 days of service data remain. Last service date 2065-11-30.
Feed version: 20260504
Location: California

A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.3, validator 8.0.1.