Culver City Bus

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

• Warning416 instances

  416 of 417 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

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

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

• Warning2 instances

  Equal shape distance same coordinates (flagged by the MobilityData validator).

  See the linked rule for what this affects.

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

  Validator rule: equal_shape_distance_same_coordinates

• Warning1 instance

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

  If a new feed isn't published before it ends, trip planners will drop your agency and riders will see no service.

  Fix: Schedule a feed re-export now so the new calendar is live well before the current one ends. (Usually a re-export from your scheduling software.)

  Validator rule: feed_expiration_date30_days · Read the fix guide

• Warning1 instance

  Some files are missing recommended (not required) fields.

  Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.

  Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)

  Validator rule: missing_recommended_field

• Warning1 instance

  The feed contains route shapes no trip uses.

  Harmless to riders, but it bloats the feed and suggests stale export data.

  Fix: Enable 'remove unused shapes' (or similar) in your export tool. (One setting.)

  Validator rule: unused_shape · Read the fix guide

• Warning1 instance

  Service data runs out in 26 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.)

  Validator rule: scorecard_feed_expiring_soon

• Info10 instances

  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

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