Mariposa Grove Shuttle (Yosemite National Park)

What this grade measures

The quality of the schedule data this agency publishes 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 where the feed stands today.

What needs attention next

Three improvements, in priority order, each sized so the board can see what it is approving:

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

   Estimated effort: A few minutes in your scheduling software.

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

   Estimated effort: Varies.

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

   Estimated effort: Two fields in feed_info.txt, or one export setting.