Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires · Correct or claim this listing
Feed status · checked 2026-07-10
Foothill Transit
Based on the feed this agency publishes
First scorecard for this agency
Ahead of 36% of all tracked agencies and 46% of large agencies.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.1, validator 8.0.1.
Top things to fix
Review the rule documentation for 'invalid_phone_number' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid phone number (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points
Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The trip updates realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
⏱ Usually a vendor support ticket.worth about +8 points
Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The vehicle positions realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
⏱ Usually a vendor support ticket.worth about +8 points
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
Review the rule documentation for 'invalid_phone_number' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Score by category
The MobilityData validator flagged 9 kinds of issue across 606 instances (2 error, 574 warning, 30 informational).
Service data covers the next 113 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
Sampled 9 times: 0 of 3 feeds healthy; 0.0% of scheduled trips had live predictions.
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
- Error2 instances
Invalid phone number (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_phone_number' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: invalid_phone_number · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
The trip updates realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)
Validator rule: scorecard_rt_trip_updates_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Error1 instance
The vehicle positions realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)
Validator rule: scorecard_rt_vehicle_positions_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Error1 instance
The service alerts realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)
Validator rule: scorecard_rt_service_alerts_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Warning13302 instances
13302 of 13302 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 · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1995 instances
1995 of 1995 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 · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning534 instances
Stop too far from shape using user distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning95 instances
95 of 95 trips scheduled during the sampling window had no live predictions.
Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.
Fix: Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. (A vendor data-mapping question.)
Validator rule: scorecard_rt_trip_coverage · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Warning34 instances
Same name and description for route (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_name_and_description_for_route' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: same_name_and_description_for_route · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 instances
Some route colors don't contrast with their text color.
Route badges become unreadable, especially for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Validator rule: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some stops sit far from the route line they belong to.
Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. (A few minutes per flagged stop.)
Validator rule: stop_too_far_from_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)
Validator rule: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info14 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 · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info14 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
Unused station (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unused_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: unused_station · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
25 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (195, 282, 289, 291, 292, and more).
Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.
1936 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Temple Ave and Diamond Bar Blvd E", "Orange Grove Ave and Glen Ave N", "Golden Springs Rd and Calbourne Dr E", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
NTD GTFS readiness Needs attention
This feed is close to NTD-ready. 1 validator error to resolve.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 1 validator error to resolve.
- Current Ready
- Service data covers the next 113 days.
- agency_id matches your NTD ID Not checked yet
- Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed is close to the conformance mark. 1 validator error to resolve. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Met
- Service data covers the next 113 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every stop and trip is wheelchair accessible.
A pass credential for a feed that is valid, current, and states wheelchair access on nearly every stop and trip. Accessibility here measures what the feed publishes, not whether a stop is physically usable. How the conformance mark works.
Realtime reliability
The realtime feed responded on 0.0% of 1 checks, with lag not reported by the feed.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Clears the Google and Apple Maps four-week coverage bar. This feed has 340 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 2 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
How this agency maps to the standards
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.
- Correctness 60 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 100 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 38 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: stop names and headsigns.
- Realtime quality 0 / 100
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a live badge on your agency site or feed README. It updates daily and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/foothill-transit-101/2026-07-10.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-10. Use it in a board packet, an NTD narrative, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.