City of Tracy (TRACER)

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

• Error18 instances

  Fare transfer rule without transfer count (flagged by the MobilityData validator).

  See the linked rule for what this affects.

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

  Validator rule: fare_transfer_rule_without_transfer_count

• Error9 instances

  Invalid currency amount (flagged by the MobilityData validator).

  See the linked rule for what this affects.

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

  Validator rule: invalid_currency_amount · Read the fix guide

• Error6 instances

  Missing required field (flagged by the MobilityData validator).

  See the linked rule for what this affects.

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

  Validator rule: missing_required_field

• Error5 instances

  Duplicate key (flagged by the MobilityData validator).

  See the linked rule for what this affects.

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

  Validator rule: duplicate_key

• Error1 instance

  Missing required column (flagged by the MobilityData validator).

  See the linked rule for what this affects.

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

  Validator rule: missing_required_column · Read the fix guide

• Error1 instance

  Service data ended 1416 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

• Warning193 instances

  193 of 193 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

• Warning105 instances

  105 of 105 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

• Warning105 instances

  105 of 105 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

• Warning10 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

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

  Validator rule: mixed_case_recommended_field · Read the fix guide

• 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

• Info80 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

• Info9 instances

  Unknown file (flagged by the MobilityData validator).

  See the linked rule for what this affects.

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

  Validator rule: unknown_file · Read the fix guide

• Info4 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

• Info1 instance

  Big gap in service (flagged by the MobilityData validator).

  See the linked rule for what this affects.

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

  Validator rule: big_gap_in_service