Mountain View Community Shuttle

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

• Warning3 instances

  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

• Warning2 instances

  Some scheduled trips travel implausibly fast between stops.

  Usually a typo'd stop time; riders get impossible arrival estimates.

  Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)

  Validator rule: fast_travel_between_consecutive_stops · Read the fix guide

• Warning2 instances

  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

• Warning2 instances

  Route long name contains short name (flagged by the MobilityData validator).

  See the linked rule for what this affects.

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

  Validator rule: route_long_name_contains_short_name

• Warning1 instance

  Missing feed contact email and url (flagged by the MobilityData validator).

  See the linked rule for what this affects.

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

  Validator rule: missing_feed_contact_email_and_url · Read the fix guide

• Warning1 instance

  feed_info.txt is missing its start/end dates

  Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.

  Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)

  Validator rule: scorecard_missing_feed_info_dates · Read the fix guide

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

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

• 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