Tulare County Area Transit (TCAT)

680 of 680 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. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)

Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

375 of 375 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)

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

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

19 of 19 trips scheduled during the sampling window had no live predictions.

Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.

Fix: Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. (A vendor data-mapping question.)

Finding code: scorecard_rt_trip_coverage · Read the fix guide for scorecard_rt_trip_coverage · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)

8 of 680 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 for scorecard_missing_headsigns · See GTFS Best Practices (opens GTFS Best Practices 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 for fast_travel_between_consecutive_stops · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

Between two distant stops, the times imply a speed no bus reaches.

A rider gets a trip plan that cannot happen. Live systems then report delays that are not real.

Fix: Check the two stop times for a wrong digit first. Then check whether a stop sits at the wrong coordinates, or a stop between them is missing. (Minutes per flagged trip once you open it.)

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

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

Route badges get hard to read, most of all for riders with low vision.

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

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

Some service calendars in the feed have already ended.

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

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

Service data runs out in 18 day(s).

When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice.

Fix: Re-export with a validity window that reaches at least 60 days out. (One export setting.)

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

This feed describes flexible (demand-responsive) service but has no booking_rules.txt.

Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.

Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)

Finding code: scorecard_flex_no_booking_rules · Read the fix guide for scorecard_flex_no_booking_rules · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

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

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

Stop without zone id (flagged by the MobilityData validator).

See the linked rule for what this affects.

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

Finding code: stop_without_zone_id · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

The feed includes a file that is not part of the GTFS spec.

Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.

Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)

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

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.

Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)

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