Reds Meadow Shuttle

Top things to fix

Score by category

Over time

This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.

Everything we checked

• Error1 instance

  Service data ended 167 day(s) ago.

  When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.

  Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)

  Validator rule: scorecard_feed_expired

• Warning543 instances

  543 of 543 trips don't say whether the vehicle is wheelchair accessible.

  Even with accessible stops, riders need to know the bus itself can take them.

  Fix: Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)

  Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide

• Warning57 instances

  Some stops exist in the feed but no trip ever stops at them.

  Riders may walk to a stop where no bus is scheduled to arrive.

  Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)

  Validator rule: stop_without_stop_time · Read the fix guide

• Warning20 instances

  Some service calendars in the feed have already expired.

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

  Validator rule: expired_calendar · Read the fix guide

• Warning13 instances

  13 of 190 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.)

  Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide

• Warning3 instances

  Same stop and route url (flagged by the MobilityData validator).

  See the linked rule for what this affects.

  Fix: Review the rule documentation for 'same_stop_and_route_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

  Validator rule: same_stop_and_route_url

• Warning2 instances

  2 of 543 trips have no headsign.

  Riders at the stop can't tell which direction a bus is going.

  Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)

  Validator rule: scorecard_missing_headsigns · Read the fix guide

• Warning1 instance

  Some scheduled trips travel implausibly fast between stops.

  Usually a typo'd stop time; riders get impossible arrival estimates.

  Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)

  Validator rule: fast_travel_between_consecutive_stops · Read the fix guide

• Warning1 instance

  Fast travel between far stops (flagged by the MobilityData validator).

  See the linked rule for what this affects.

  Fix: Review the rule documentation for 'fast_travel_between_far_stops' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

  Validator rule: fast_travel_between_far_stops

• Warning1 instance

  This feed's service calendar runs out within the next 7 days.

  When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.

  Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)

  Validator rule: feed_expiration_date7_days · Read the fix guide

• Warning1 instance

  Some route colors don't contrast with their text color.

  Route badges become unreadable, especially for riders with low vision.

  Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)

  Validator rule: route_color_contrast · Read the fix guide

• Warning1 instance

  Same stop and agency url (flagged by the MobilityData validator).

  See the linked rule for what this affects.

  Fix: Review the rule documentation for 'same_stop_and_agency_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

  Validator rule: same_stop_and_agency_url

• Warning1 instance

  Many of the feed's trips don't run at all in the next 7 days.

  It usually means old service periods are still in the export, making the feed bigger and harder to check.

  Fix: Trim past service periods the next time you export. (One setting in most export tools.)

  Validator rule: trip_coverage_not_active_for_next7_days · Read the fix guide

• Info32 instances

  Some files contain columns that are not part of the GTFS spec.

  Harmless to riders, but apps ignore these columns and they can hide typos in real column names.

  Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)

  Validator rule: unknown_column · Read the fix guide

• Info14 instances

  Service window outside feed period (flagged by the MobilityData validator).

  See the linked rule for what this affects.

  Fix: Review the rule documentation for 'service_window_outside_feed_period' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

  Validator rule: service_window_outside_feed_period · Read the fix guide