Feed status · checked 2026-06-16
eTrans
Based on the feed this agency publishes
First scorecard for this agency
A data-quality and completeness lens to help an agency improve its feed. Not the official Caltrans or Cal-ITP compliance determination. New to this? How to read your scorecard. Interactive view. Rubric v1.1, validator 8.0.1.
Top things to fix
Remove retired stops from the export, or add them back to the trips that should serve them.
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.
⏱ A review pass in your scheduling software.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
4 of 43 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.
⏱ A column in stops.txt; your scheduling software likely has it.
Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras.
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.
⏱ A quick look at the flagged files.
Score by category
The MobilityData validator flagged 4 kinds of issues: 0 error, 2 warning, and 43 informational instances in total.
Service data covers the next 168 days.
91% of stops state wheelchair accessibility (74% marked accessible). Fare data is published.
Not scored yet. Nothing here counts against the grade.
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
- Warning4 instances
4 of 43 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
- Warning2 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
- Info34 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
- Info8 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
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