San Joaquin Regional Transit District (RTD)

898 of 898 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 · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

Some stops sit far from the route line, going by the feed's own distance values.

Trip planners may draw the route down the wrong streets or point riders to the wrong corner.

Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)

Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

Some scheduled trips move faster between stops than a bus can.

Usually a typo'd stop time; riders get arrival times no bus can meet.

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

Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

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

Finding code: fast_travel_between_far_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

28 of 2339 trips lack rider-facing destination or direction text.

When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)

Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)

Some stops sit far from the route line they belong to.

Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.

Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)

Finding code: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

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.

Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)

Finding code: service_has_no_active_day_of_the_week · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

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

Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

The feed has a stretch of two weeks or more with no service running.

A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.

Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)

Finding code: big_gap_in_service · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)