Stanislaus Regional Transit Authority (StanRTA)

Service data ended 883 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.)

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

The trip updates realtime feed failed during sampling.

When this feed is down, riders see scheduled times presented as if they were live.

Fix: Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)

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

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

Some route lines list the same point twice in a row.

Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.

Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)

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

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

Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).

See the linked rule for what this affects.

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

Finding code: equal_shape_distance_diff_coordinates_distance_below_threshold · 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 · 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)

Some rider-facing names are in ALL CAPS or all lowercase.

ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.

Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)

Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules 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)

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

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

feed_info.txt lists no contact email and no contact URL.

Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.

Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)

Finding code: missing_feed_contact_email_and_url · Read the fix guide · 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 · 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 contains no fare information.

Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)

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

Feed valid beyond total service window (flagged by the MobilityData validator).

See the linked rule for what this affects.

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

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

feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.

Fix: Add feed_contact_email to feed_info.txt. (One field.)

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