Santa Clarita Transit

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

• Error5 instances

  Missing required file (flagged by the MobilityData validator).

  See the linked rule for what this affects.

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

  Validator rule: missing_required_file

• Error1 instance

  Invalid input files in subfolder (flagged by the MobilityData validator).

  See the linked rule for what this affects.

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

  Validator rule: invalid_input_files_in_subfolder

• Error1 instance

  Missing calendar and calendar date files (flagged by the MobilityData validator).

  See the linked rule for what this affects.

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

  Validator rule: missing_calendar_and_calendar_date_files

• Error1 instance

  Neither feed_info.txt nor the calendars state when service ends.

  Nobody can tell when this feed will go stale.

  Fix: Add feed_start_date and feed_end_date to feed_info.txt and include calendar end dates in your export. (Likely a one-time export setting.)

  Validator rule: scorecard_no_expiry_date

• Warning1 instance

  A recommended GTFS file (usually feed_info.txt) is missing.

  feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.

  Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)

  Validator rule: missing_recommended_file · Read the fix guide

• Warning1 instance

  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. (A small file for most flat-fare systems.)

  Validator rule: scorecard_no_fare_data · Read the fix guide

• Warning1 instance

  agency.txt has no working website URL.

  Trip planners link riders to this URL for schedules and fares.

  Fix: Set agency_url to your agency's website, starting with https://. (One field.)

  Validator rule: scorecard_bad_agency_url

• Warning0 instances

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

• Warning0 instances

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

• Warning0 instances

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

• Info1 instance

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

  App makers and state data programs 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.)

  Validator rule: scorecard_no_feed_contact · Read the fix guide

• Info0 instances

  About 0 stop names are written in ALL CAPS.

  Mixed-case names are easier to read in apps and are read more naturally by screen readers.

  Fix: Rename stops to mixed case (e.g. 'Main St & 2nd Ave'). (Often a bulk fix in your scheduling software.)

  Validator rule: scorecard_stop_names_all_caps