Feed status · checked 2026-08-02
Foothill Transit
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-08-01
Catalogued in California.
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.3, validator 8.0.1.
Checked for changes 46 minutes ago; last changed 16 days ago.
Measured 4 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- The feed was downloaded from the agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
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 +33 points in its category
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 +33 points in its category
Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The service alerts 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 +33 points in its category
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- The trip updates realtime feed failed during sampling.
- Next action
- Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- The vehicle positions realtime feed failed during sampling.
- Next action
- Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- The service alerts realtime feed failed during sampling.
- Next action
- Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
How to make and check these changes
Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.
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.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. 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.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Check the service alerts 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.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date is in 90 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- No fare information is published in the feed.
- Realtime information
- No realtime feed was reachable during sampling.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
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 7 kinds of issue across 578 instances (2 error, 574 warning, 2 informational).
Service data covers the next 90 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.
3 accessibility depth signals
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.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Sampled 9 times: 0 of 3 configured feeds healthy; vehicle position plausibility was not measurable.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 1995 stops.
The route and stop data is ready below. Load the map only when you want the geographic view. It uses additional data.
Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 195 (teal)
- 197 (purple)
- 282 (pink)
- 285 (red)
- 286 (yellow)
- 289 (yellow)
- 291 (teal)
- 292 (pink)
- 482 (purple)
- 486 (teal)
- 488 (white)
- 490 (pink)
- 492 (orange)
- 495 (teal)
- 499 (pink)
- 699 (red)
- 853 (yellow)
- 178 (yellow)
- 185 (gray)
- 187 (green)
- 188 (purple)
- 190 (red)
- 194 (green)
- 269 (pink)
- 270 (teal)
- 272 (pink)
- 274 (teal)
- 280 (pink)
- 281 (white)
- 284 (green)
- 295 (teal)
- 480 (green)
- 493 (teal)
- 498 (teal)
- 707 (gray)
- 861 (red)
| Route | Type | Line color |
|---|---|---|
| 195 Pomona Transit Center via Reservoir St | Bus | teal |
| 197 Pomona - Claremont - Montclair | Bus | purple |
| 282 Puente Hills-Hacienda Hts-El Monte Sta | Bus | pink |
| 285 Puente Hills-Whittier Hospital-La Habra | Bus | red |
| 286 Pomona - Diamond Bar - Brea Mall | Bus | yellow |
| 289 Pomona - Walnut - Puente Hills Mall | Bus | yellow |
| 291 La Verne - Pomona via Garey Ave | Bus | teal |
| 292 Claremont Transit Ctr-Pomona Transit Ctr | Bus | pink |
| 482 Pomona-Rowland Heights-Puente Hills Mall | Bus | purple |
| 486 Pomona-La Puente-El Monte Via Amar Rd | Bus | teal |
| 488 Glendora-West Covina-El Monte Station | Bus | white |
| 490 Express-Grand Av Park N Ride-Covina-DTLA | Bus | pink |
| 492 El Monte-Arcadia-Montclair Transit Ctr | Bus | orange |
| 495 Express - Industry Park N Ride - DTLA | Bus | teal |
| 499 Express - Via Verde Park N Ride - DTLA | Bus | pink |
| 699 Express - Montclair - Fairplex - DTLA | Bus | red |
| 853 Diamond Bar | Bus | yellow |
| 178 Puente Hills Mall - El Monte Station | Bus | yellow |
| 185 Azusa - West Covina - Puente Hills Mall | Bus | gray |
| 187 Azusa - Arcadia - Pasadena | Bus | green |
| 188 Azusa-Claremont-Montclair Transit Ctr | Bus | purple |
| 190 Pomona - West Covina - El Monte Station | Bus | red |
| 194 Pomona - Industry - La Puente - El Monte | Bus | green |
| 269 El Monte Station - Shops at Montebello | Bus | pink |
| 270 Arcadia Sta. - Monrovia - El Monte Sta. | Bus | teal |
| 272 Duarte - Baldwin Park - West Covina | Bus | pink |
| 274 West Covina - Industry - Whittier | Bus | teal |
| 280 Azusa - Puente Hills Mall via Azusa Ave | Bus | pink |
| 281 Glendora-Azusa-West Covina-Puente Hills | Bus | white |
| 284 Glendora-San Dimas-Covina-West Covina | Bus | green |
| 295 San Dimas Station-Cal Poly Pomona-Mt SAC | Bus | teal |
| 480 West Covina-Pomona-Montclair Transit Ctr | Bus | green |
| 493 Express-Rowland Hts-Puente Hills-DTLA | Bus | teal |
| 498 Express Service - West Covina - DTLA | Bus | teal |
| 707 Montclair - Pomona - El Monte - L.A. | Bus | gray |
| 861 Duarte Mtn Vista-Huntington-Royal Oaks | Bus | red |
List every stop
- Temple Ave and Diamond Bar Blvd E
- Orange Grove Ave and Glen Ave N
- Golden Springs Rd and Calbourne Dr E
- Colima Rd and Camino del Sur N
- Colima Rd and Camino del Sur S
- Colima Rd and Carretera Dr N
- Colima Rd and Brea Canyon Cut-off Rd E
- Colima Rd and Brea Canyon Cut-off Rd E
- Colima Rd and Fullerton Rd W
- Colima Rd and Fullerton Rd W
- Colima Rd and Greencastle Ave W
- Colima Rd and Greencastle Ave W
- Colima Rd and Hacienda Blvd S
- Colima Rd and Halliburton Rd N
- Colima Rd and Halliburton Rd W
- Colima Rd and Jellick Ave W
- Colima Rd and Jellick Ave W
- Colima Rd and Larkvane Rd E
- Colima Rd and Larkvane Rd E
- Colima Rd and Manor Gate Rd N
- Colima Rd and Manor Gate Rd N
- Colima Rd and Manor Gate Rd S
- Colima Rd and Manor Gate Rd S
- Colima Rd and Mar Vista Dr N
- Colima Rd and Mar Vista Dr S
- Colima Rd and Nausika Ave E
- Colima Rd and Nausika Ave W
- Colima Rd and Nogales St E
- Colima Rd and Nogales St E
- Colima Rd and Otterbien Ave E
- Colima Rd and Otterbien Ave W
- Colima Rd and Paso Real Ave E
- Colima Rd and Paso Real Ave E
- Colima Rd and Punta Del Este Dr N
- Colima Rd and Punta Del Este Dr S
- Colima Rd and Sierra Ridge Wy S
- Colima Rd and Stimson Ave N
- Colima Rd and Walnut Hall Rd E
- Colima Rd and Walnut Hall Rd E
- Whittier Blvd and Colima Rd N
- Colorado Blvd and Allen Ave E
- Colorado Blvd and Allen Ave W
- Colorado Blvd and Arroyo Pkwy E
- Colorado Blvd and Catalina Ave E
- Colorado Blvd and Catalina Ave W
- Colorado Blvd and Garfield Ave E
- Colorado Blvd and Garfield Ave W
- Colorado Blvd and Hill Ave E
- Colorado Blvd and Hill Ave W
- Colorado Blvd and Lake Ave E
- Colorado Blvd and Lake Ave W
- Colorado Blvd and Los Robles Ave E
- Colorado Blvd and Los Robles Ave W
- Colorado Blvd and Madison Ave E
- Colorado Blvd and Marengo Ave W
- Rosemead Blvd and Colorado Blvd E
- Colorado Blvd and San Gabriel Blvd W
- Colorado Blvd and Sierra Bonita Ave E
- Colorado Blvd and Altadena Dr E
- Colorado Blvd and Sierra Madre Blvd W
- Copley Dr and AQMD W
- Copley Dr and Diamond Bar City Hall E
- Copley Dr and Golden Springs Dr
- Gateway Center Dr and Valley Vista Dr E
- County Rd and Garey Ave S
- Covina Blvd and Hospital Entrance N
- Covina Blvd and Bonnie Cove Ave N
- Covina Blvd and Bonnie Cove Ave S
- Covina Blvd and Lyman Ave S
- Covina Blvd and Lone Hill Ave
- Covina Blvd and Mangrove Ave N
- Covina Blvd and Mangrove Ave S
- Covina Blvd and Sunflower Ave N
- Covina Blvd and Sunflower Ave S
- Covina Blvd and Valley Center Ave N
- Covina Blvd and Valley Center Ave S
- Workman Mill Rd. and FedEx S
- Diamond Bar Blvd and Golden Springs Dr E
- Diamond Bar Blvd and Golden Springs Dr
- Diamond Bar Blvd and Highland Valley Rd
- Diamond Bar Blvd and Highland Valley Rd
- Diamond Bar Blvd and Town Center S
- Diamond Bar Park & Ride E
- Diamond Bar Park & Ride W
- Diamond Bar Blvd and Sunset Crossing Rd
- Diamond Bar Blvd and Sunset Crossing Rd
- Diamond Bar Blvd and Town Center N
- Diamond Ranch High School
- Duarte Rd and Buena Vista St E
- Duarte Rd and Hope Dr E
- Durward Wy and D St
- East End Ave and Holt W
- East End Ave and Mission W
- El Monte Station Upper Level
- El Monte Station Upper Level
- El Monte Station Lower Level
- El Monte Station Lower Level
- Fairplex Dr and Elwood Ave E
- Fairplex Dr and Elwood Ave W
- Francisquito Ave and California Ave W
- Figueroa St and 5th St E
- Figueroa St and 5th St E
- Figueroa St and 7th St E
- Figueroa St and 7th St E
- Figueroa St and 8th St E
- Figueroa St and 8th St E
- Figueroa St and 9th St E
- Figueroa St and 9th St E
- 6th St and Hope St W
- 6th St and Hope St W
- Foothill Blvd and Alameda W
- Foothill Blvd and Amelia Ave E
- Foothill Blvd and Amelia Ave W
- Diamond Bar Blvd and Temple Ave N
- Foothill Blvd and Baseline Rd W
- Foothill Blvd and Chelsea Dr E
- Foothill Blvd and Chelsea Dr W
- Foothill Blvd and Citrus Ave W
- Foothill Blvd and Claremont Blvd S
- Foothill Blvd and Dartmouth Ave E
- Foothill Blvd and Dartmouth Ave W
- Foothill Blvd and D St E
- Foothill Blvd and D St E
- Foothill Blvd and D St W
- Foothill Blvd and Dalton Ave E
- Foothill Blvd and Dalton Ave W
- Foothill Blvd and Damien Ave W
- Foothill Blvd and Elwood Ave S
- Foothill Blvd and Elwood Ave N
- Foothill Blvd and Emerald Ave E
- Foothill Blvd and Emerald Ave W
- Foothill Blvd and Falcon St E
- Foothill Blvd and Falcon St E
- Foothill Blvd and Bradford St. W
- Foothill Blvd and Bradford St. W
- Foothill Blvd and Fruit St W
- Citrus College (Foothill Blvd and Galant
- Citrus College (Foothill Blvd and Galant
- Foothill Blvd and Barranca Ave E
- Foothill Blvd and Garey Ave E
- Foothill Blvd and Garey Ave W
- Foothill Blvd and Garey Ave W
- Grand Ave and Foothill Blvd
- Foothill Blvd and Indian Hill Blvd E
- Foothill Blvd and Indian Hill Blvd W
- Foothill Blvd and Irwindale Ave E
- Irwindale Ave and Foothill Blvd S
- Foothill Blvd and Irwindale Ave W
- Foothill Blvd and Live Oak Ave S
- Foothill Blvd and Live Oak Ave N
- Foothill Blvd and Lone Hill Ave S
- Foothill Blvd and Loraine Ave S
- Foothill Blvd and Loraine Ave N
- Foothill Blvd and Mills Ave E
- Foothill Blvd and Mills Ave W
- Foothill Blvd and Minnesota Ave S
- Foothill Blvd and Minnesota Ave N
- Foothill Blvd and Mountain Ave E
- Foothill Blvd and Mountain Ave W
- Foothill Blvd and Orange Ave E
- Foothill Blvd and Orange Ave W
- Nogales St and Daisetta St W
- Nogales St and Daisetta St W
- Foothill Blvd and Pasadena Ave E
- Foothill Blvd and Pasadena Ave W
- Foothill Blvd and Ramona Ave E
- Foothill Blvd and Rosemead Blvd W
- Foothill Blvd and Rockvale Ave E
- Foothill Blvd and San Dimas Ave E
- Foothill Blvd and San Dimas Ave W
- Foothill Blvd and San Dimas Canyon Rd E
- Foothill Blvd and San Dimas Canyon Rd W
- Foothill Blvd and San Gabriel Blvd E
- Foothill Blvd and San Gabriel Blvd N
- Foothill Blvd and San Gabriel Blvd W
- Foothill Blvd and Sierra Madre Villa Ave
- Foothill Blvd and Sumner Ave E
- Foothill Blvd and Sumner Ave W
- Foothill Blvd and Sunnyslope Ave W
- Foothill Blvd and Todd Ave E
- Foothill Blvd and Todd Ave W
- Foothill Blvd and Towne Ave E
- Foothill Blvd and Towne Ave W
- Foothill Blvd and Towne Center Dr E
- Foothill Blvd and Towne Center Dr E
- Foothill Blvd and Towne Center Dr W
- Foothill Blvd and Towne Center Dr W
- Foothill Blvd and Valencia St E
- Foothill Blvd and Valencia St W
- Foothill Blvd and Valley Center Ave E
- Foothill Blvd and Valley Center Ave N
- Foothill Blvd and Vernon Ave E
- Foothill Blvd and Vernon Ave W
- Foothill Blvd and Walnut Ave E
- Foothill Blvd and Longhorn Rd W
- Foothill Blvd and Wheeler Ave W
- Foothill Blvd and Gordon Ave S
- Foothill Blvd and Whispering Oaks Dr N
- Foothill Blvd and White Ave E
- Foothill Blvd and White Ave E
- Foothill Blvd and Woodglen Dr E
- Foothill Blvd and Woodglen Dr W
- Francisquito Ave and Baldwin Park Blvd E
- Francisquito Ave and Baldwin Park Blvd W
- Francisquito Ave and California Ave E
- Francisquito Ave and Dalewood St W
- Francisquito Ave and Frazier St E
- Francisquito Ave and Frazier St W
- Francisquito Ave and Hacienda Blvd W
- Francisquito Ave and Orange Ave E
- Francisquito Ave and Orange Ave W
- Francisquito Ave and Puente Ave E
- Francisquito Ave and Puente Ave W
- Francisquito Ave and Sunset Ave E
- Francisquito Ave and Sunset Ave W
- Francisquito Ave and Vineland Ave E
- Francisquito Ave and Willow Ave E
- Francisquito Ave and Willow Ave W
- Covina Metrolink (Front and Citrus Ave N
- Covina Metrolink (Front and Citrus Ave S
- Gale Ave and Seventh Ave S
- Gale Ave and Seventh Ave S
- Gale Ave and Azusa Ave N
- Gale Ave and Azusa Ave N
- Gale Ave and Azusa Ave S
- Gale Ave and Azusa Ave S
- Gale Ave and Bixby Dr N
- Gale Ave and Bixby Dr N
- Gale Ave and Bixby Dr S
- Gale Ave and Bixby Dr S
- Gale Ave and Fieldgate Ave N
- Gale Ave and Fieldgate Ave N
- Gale Ave and Fieldgate Ave S
- Gale Ave and Fieldgate Ave S
- Gale Ave and Green Dr N
- Gale Ave and Green Dr N
- Gale Ave and Green Dr S
- Gale Ave and Green Dr S
- Gale Ave and Hinnen Ave N
- Gale Ave and Hinnen Ave N
- Gale Ave and John Reed Ct N
- Gale Ave and John Reed Ct N
- Gale Ave and John Reed Ct S
- Gale Ave and John Reed Ct S
- Gale Ave and Post Office N
- Gale Ave and Post Office N
- Gale Ave and Kwis Ave S
- Gale Ave and Kwis Ave S
- Diamond Bar Blvd and Mountain Laurel Way
- Gale Ave and Latchford Ave. N
- and 1745 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-08-01.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 50.9 | first check |
| 2026-07-30 | 50.9 | no change |
| 2026-08-01 | 50.9 | no change |
| 2026-08-02 | 50.9 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality no change
What changed in this feed
Overall grade and score held steady since 2026-08-01.
Same feed file as 2026-08-01; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
15 findings, ordered by severity.
Show every finding
- 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.)
Finding code: 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.)
Finding code: 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.)
Finding code: 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.)
Finding code: 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. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)
Finding code: 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.)
Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning534 instances
Some stops sit far from the route line, going by the feed's own distance values.
Trip planners may draw the route down the wrong streets or point riders to the wrong corner.
Fix: Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)
Finding code: 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)
- 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.)
Finding code: 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 get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt lists no contact email and no contact URL.
Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.
Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)
Finding code: 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.)
Finding code: 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.)
Finding code: 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.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference 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.)
Finding code: 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).
Trip-planning apps and regional data coordinators 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.)
Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
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 90 days.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
- agency_id equals your NTD ID (optional) Not checked yet
- This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
- shapes.txt covers your trips Ready
- All 13302 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
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). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also 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 90 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 200 checks over the last 34 days, 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 90 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
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
In California, the published guideline is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.
California Minimum GTFS Guidelines checklist (2 of 6 measured items met)
The state's own Data Process Checklist, matched item by item to what this scorecard already measures. An item marked "not measured here" is real ground the checklist covers that this tool does not check; see the official checklist for the full picture.
- Meets Publish GTFS Schedule at a stable, automatically-fetchable URL
The published feed URL downloaded at the last check.
- Not measured here Implement required fields: Fares v2, text-to-speech stop names, shapes.txt, wheelchair_boarding, and Pathways where applicable
This scorecard measures wheelchair_boarding, shapes.txt coverage, fare data, and station pathways separately, below; it does not check the Fares v2 format specifically or text-to-speech stop names.
- Not measured here Achieve a passing score in every category of the MobilityData GTFS Grading Scheme v1
This scorecard automates a proxy for the Grading Scheme's rider-facing fields (see the standards crosswalk) rather than running the scheme itself, which grades by comparison to the real world by hand.
- Not measured here Publish changes to the base schedule at least one week ahead of every service change
This scorecard does not track a feed's publish history, so advance notice cannot be checked.
- Gap Produce no critical errors in the MobilityData GTFS Validator
1 validator error to resolve.
- Not measured here Publish Trip Updates, Vehicle Positions, and Alerts feeds
This scorecard checks realtime reachability and freshness overall; it does not check for all three feed types individually.
- Not measured here Update Trip Updates and Vehicle Positions at least every 20 seconds
This scorecard samples realtime freshness; it does not check this specific 20-second cadence.
- Not measured here Publish information for at least 99% of vehicles in service
This scorecard measures the share of scheduled trips represented in TripUpdates, a related but different figure than vehicle coverage.
- Not measured here Keep 100% of trip_ids consistent between Schedule and Realtime
This scorecard does not currently check trip_id consistency between the Schedule and Realtime feeds.
- Not measured here Produce no critical errors in the Center for Urban Transportation Research realtime validator
This scorecard does not run the CUTR realtime validator.
- Not measured here Publish accessible feed links on the agency or regional partner website
This scorecard does not check the agency's own website.
- Not measured here Register GTFS and GTFS-Realtime feeds with transit.land and the Mobility Database
This scorecard does not currently check aggregator registration for this section.
- Gap Designate a technical contact in feed_info.txt's feed_contact_email
feed_info.txt has no feed_contact_email or feed_contact_url.
- Gap wheelchair_boarding stated on stops and trips
States wheelchair access on 0% of stops and 0% of trips.
- Meets shapes.txt with a shape for every trip
All 13302 trips have a shape in shapes.txt.
- Gap Fare data published, or the service marked fare-free
No fare data is published.
- Correctness 62 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
- Freshness 100 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
- Rider experience 38 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers 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 badge on your agency site or feed README. It updates after each completed scoring check 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/2026-08-02.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-08-02. Use it in a board packet, a regulatory filing, 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.