Feed status · checked 2026-08-02
OmniTrans
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-08-01
Catalogued in California.
Heads-up: The score rose 21 points in one step, from 67 on 2026-07-25 to 88 on 2026-07-30. A jump this size usually means the export changed rather than the service. Worth checking the run on this date. (checked 2026-07-30). This can be a brief vendor export glitch; watch the next update before acting.
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 2 hours ago; last changed 8 hours ago.
Measured 3 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: medium.
- Realtime quality was not measured this run. It does not count against the grade.
- 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 flagged stop times for transposed minutes.
Some scheduled trips move faster between stops than a bus can. Usually a typo'd stop time; riders get arrival times no bus can meet.
⏱ A few minutes per flagged trip.worth about +8 points in its category
Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced.Likely your export tool
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.
⏱ A few minutes per flagged stop.worth about +6 points in its category
Review the rule documentation for 'unexpected_enum_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Unexpected enum value (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +4 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
- Some scheduled trips move faster between stops than a bus can.
- Next action
- Check the flagged stop times for transposed minutes.
- 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
- Some stops sit far from the route line they belong to.
- Next action
- Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced.
- 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
- Unexpected enum value (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'unexpected_enum_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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 flagged stop times for transposed minutes. · 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. See this feed's finding-clearance log.
Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced. · 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. See this feed's finding-clearance log.
Review the rule documentation for 'unexpected_enum_value' 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.
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. See this feed's finding-clearance log.
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 154 days.
- Published accessibility data
- Accessibility information is stated for 100% of stops and 100% of trips. This measures published data, not whether stops or vehicles are physically usable.
- Fare information
- Fare information is published using GTFS Fares v2.
- Realtime information
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
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 8 kinds of issue across 106 instances (0 error, 102 warning, 4 informational).
Service data covers the next 154 days.
100% of stops state wheelchair accessibility (100% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
100% of stops state accessibility (100% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 19, 305, 6).
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.
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.
Fares are applied to trips.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 2283 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.
- 1 (teal)
- 10 (white)
- 14 (white)
- 15 (white)
- 19 (teal)
- 2 (white)
- sbX Green Line (teal)
- 215 (purple)
- 22 (white)
- 290 (purple)
- 3 (yellow)
- 305 (green)
- 312 (red)
- 319 (green)
- 367 (red)
- 380 (white)
- 4 (white)
- 6 (green)
- 61 (green)
- 66 (white)
- 8 (teal)
- 81 (white)
- 82 (brown)
- 83 (white)
- 84 (teal)
- 85 (gray)
- 87 (yellow)
- 88 (green)
| Route | Type | Line color |
|---|---|---|
| 1 ARMC - San Bdno - Del Rosa | Bus | teal |
| 10 Fontana - Baseline - San Bdno | Bus | white |
| 14 Fontana - Foothill - San Bdno | Bus | white |
| 15 Fontana - San Bdno - Redlands | Bus | white |
| 19 Fontana - Colton - Yucaipa | Bus | teal |
| 2 Cal State - Loma Linda | Bus | white |
| sbX Green Line | Bus | teal |
| 215 Riverside - San Bdno | Bus | purple |
| 22 North Rialto - Riverside Ave - ARMC | Bus | white |
| 290 San Bdno - Ontario Mills - Montclair | Bus | purple |
| 3 San Bdno - Baseline - Highland | Bus | yellow |
| 305 San Bdno - Waterman - Grand Terrace | Bus | green |
| 312 Fontana - Muscoy - Cal State | Bus | red |
| 319 Yucaipa | Bus | green |
| 367 Fontana - Baseline - Chaffey College | Bus | red |
| 380 ONT Connect | Bus | white |
| 4 San Bdno - Baseline - Highland | Bus | white |
| 6 Cal State - Sierra Way - San Bdno | Bus | green |
| 61 Fontana -Ontario Mills -ONT- Pomona | Bus | green |
| 66 Fontana - Foothill - Montclair | Bus | white |
| 8 San Bdno - Mentone - Crafton Hills | Bus | teal |
| 81 Ontario - Haven - Chaffey College | Bus | white |
| 82 Rancho Cucamonga - Fontana | Bus | brown |
| 83 Chino - Euclid - Upland | Bus | white |
| 84 Chino - Mountain - Montclair | Bus | teal |
| 85 Chino - Montclair - Chaffey College | Bus | gray |
| 87 Chaffey College - Ontario -Eastvale | Bus | yellow |
| 88 Chino Hills - Ramona - Montclair | Bus | green |
| OR Blm OmniRide Bloomington | Bus | green (no shape in feed) |
| OR CCH OmniRide Chino/Chino Hills | Bus | green (no shape in feed) |
| OR Upl OmniRide Upland | Bus | green (no shape in feed) |
List every stop
- Arrowhead Regional Medical Center
- Pacific High School
- Foothill @ Riverside Avenue
- Foothill @ Riverside Avenue
- 5th Street @ Medical Center Drive
- Merrill @ Riverside Avenue
- Merrill @ Riverside Avenue
- Marygold @ Sierra Avenue
- Mt Vernon @ Centerpointe
- Mt Vernon @ Centerpointe
- Marygold @ Sierra
- E Street @ Court Street
- Riverside Avenue @ Foothill
- Riverside Avenue @ Foothill
- Mt Vernon @ Johnston
- Arrowhead Regional Medical Center
- Cal State University San Bernardino
- Pomona Transit Center
- Holt @ Mills
- E Street @ Highland Avenue
- Holt @ Mills
- Central @ Holt
- VA Hospital
- VA Hospital
- Inland Center Mall
- E Street @ 4th Street
- E Street @ Highland Avenue
- Baseline @ Boulder
- Baseline @ Boulder
- Central Avenue @ Hibiscus
- Central Avenue @ Hibiscus
- Baseline @ Tippecanoe
- Baseline @ Garden
- Highland Avenue @ Waterman
- Vineyard @ Foothill
- E Street @ Court Street
- Vineyard @ Foothill
- Holt @ Vineyard
- Baseline @ Cherry
- Arrow Route @ Haven
- 4th Street @ F Street
- Jurupa @ Cherry
- Rancho Cucamonga Metrolink
- Boulder @ Baseline
- 40th Street @ Waterman
- 40th Street @ Waterman
- Mount Vernon Avenue @ Valley College
- Del Rosa Drive @ 3rd Street
- San Antonio Hospital
- Foothill @ Grove
- Baseline @ Haven
- Foothill @ Mountain Ave
- Foothill @ Haven
- Sierra Avenue @ Merrill
- Sierra Avenue @ Athol
- Sierra Avenue @ Randall
- Sierra Avenue @ Holly
- Palmetto @ Marygold
- San Bernardino Avenue @ Palmetto
- San Bernardino Avenue @ Tangelo
- San Bernardino Avenue @ Alder
- San Bernardino Avenue @ Laurel
- San Bernardino Avenue @ Locust
- San Bernardino Avenue @ Dumond
- San Bernardino Avenue @ Orchard Street
- San Bernardino Avenue @ Cedar
- San Bernardino Avenue @ Larch
- San Bernardino Avenue @ Bloomington Avenue
- 9th Street @ Medical Center
- Vineyard @ 4th Street
- San Bernardino Avenue @ Cactus
- San Bernardino Avenue @ Lilac
- San Bernardino Avenue @ Riverside Avenue
- San Bernardino Avenue @ Wildrose
- San Bernardino Avenue @ Indigo
- San Bernardino Avenue @ Pepper
- Olive @ Meridian
- Vineyard @ 5th Street
- Olive @ Cypress
- Rancho Avenue @ Olive
- C Street @ Rancho Avenue
- La Cadena @ L Street
- La Cadena @ N Street
- Vinyard @ 6th Street
- O Street @ 10th Street
- 11th Street @ N Street
- M Street @ Fogg
- M Street @ Mt Vernon
- Mt Vernon @ Cooley
- Mt Vernon @ Santo Antonio
- Washington @ Bluff
- Washington @ Meadow Lane
- Washington @ Center Drive
- Vineyard @ 7th Street
- Washinton @ Walin
- Washington @ Mohave
- Barton @ Hunts
- Barton @ Wier
- Barton @ Waterman
- University Avenue @ Barton
- University Avenue @ Yardley
- Vineyard @ 8th Street
- Campus Street @ University Avenue
- Barton @ Campus Street
- Barton @ Anderson
- Barton @ Loma Linda Drive
- Redlands Boulevard @ Mountain View
- Vineyard @ 9th Street
- Redlands Boulevard @ Bryn Mawr
- Redlands Boulevard @ Rhonda
- Redlands Boulevard @ Taft
- Redlands Boulevard @ New Jersey
- Redlands Boulevard @ Nevada
- Redlands Boulevard @ Iowa
- Vineyard @ Arrow
- Orange @ Stuart
- Redlands Boulevard @ Alabama
- Redlands Boulevard @ Iowa
- Redlands Boulevard @ Nevada
- Redlands Boulevard @ New Jersey
- Redlands Boulevard @ Taft
- Redlands Boulevard @ Rhonda
- Redlands Boulevard @ Bryn Mawr
- Redlands Boulevard @ Corporate Drive
- Carnelian @ Calle Del Prado
- Barton @ Mountain View
- Barton @ Loma Linda Drive
- Barton @ Anderson
- Campus Street @ University Avenue
- University Avenue @ Rosarita
- Carnelian @ Baseline
- Barton @ University Avenue
- Barton @ Waterman
- Barton @ Wier
- Barton @ Hunts
- Washington @ Mojave
- Washington @ Walin
- Washington @ Meadow
- Washington @ Bluff
- Mt Vernon @ Santo Antonio
- Mt Vernon @ Cooley
- Carnelian @ Avalon
- M Street @ Mt Vernon
- M Street @ Fogg
- 11th Street @ M Street
- O Street @ 9th Street
- La Cadena @ L Street
- La Cadena @ Valley
- 19th Street @ Carnelian
- Rancho Avenue @ C Street
- Olive @ Rancho Avenue
- Olive @ Cypress
- San Bernardino Avenue @ Pepper
- San Bernardino Avenue @ Eucalyptus
- San Bernardino Avenue @ Indigo
- San Bernardino Avenue @ Sycamore
- 19th Street @ Beryl
- San Bernardino Avenue @ Riverside Avenue
- San Bernardino Avenue @ Willow
- San Bernardino Avenue @ Lilac
- San Bernardino Avenue @ Cactus
- San Bernardino Avenue @ Bloomington Avenue
- San Bernardino Avenue @ Larch
- San Bernardino Avenue @ Cedar
- San Bernardino Avenue @ Linden
- San Bernardino Avenue @ Dumond
- San Bernardino Avenue @ Locust
- 19th Street @ Hellman
- San Bernardino Avenue @ Laurel
- San Bernardino Avenue @ Boxwood
- San Bernardino Avenue @ Tamarind
- Palmetto @ San Bernardino Avenue
- Marygold @ Palmetto
- Sierra Avenue @ San Bernardino Avenue
- Sierra Avenue @ Holly
- Sierra Avenue @ Randall
- Meridian @ Valley
- 19th Street @ Amethyst
- Valley @ Hermosa
- Valley @ Rancho Avenue
- Valley @ 4th Street
- Valley @ La Cadena
- Valley @ 10th Street
- Valley @ 12th Street
- Mt Vernon @ H Street
- Mt Vernon @ Fairway
- Mt Vernon @ Shasta
- Mt Vernon @ Olive
- 19th Street @ Archibald
- Mt Vernon @ Laurel
- Mt Vernon @ La Cadena
- Mt Vernon @ Mill
- 2nd Street @ J Street
- 5th Street @ D Street
- 19th Street @ Ramona
- 5th Street @ Sierra Way
- Waterman @ 5th Street
- Waterman @ 7th Street
- San Bernardino Avenue @ Pepper
- Waterman @ 9th Street
- Waterman @ Olive
- Waterman @ Baseline
- Waterman @ Wabash
- 19th Street @ Hermosa
- 21st Street @ Kenwood
- Highland Avenue @ Valencia
- Highland Avenue @ Cedar
- Highland Avenue @ Harrison
- Golden @ Highland Avenue
- Golden @ Date
- Golden @ Lynwood
- 19th Street @ Cartilla
- Lynwood @ Mountain
- C Street @ Pennsylvania
- Lynwood @ Merito
- Lynwood @ Sterling
- Highland Avenue @ Sterling
- Highland Avenue @ Osbun
- La Cadena @ D Street
- Highland Avenue @ Del Rosa Avenue
- Highland Avenue @ Mountain
- Haven @ 19th Street
- Highland Avenue @ Golden
- Highland Avenue @ Harrison
- Highland Avenue @ Cedar
- La Cadena @ F Street
- Valencia @ Highland Avenue
- 21st Street @ Kenwood
- Waterman @ Gilbert
- Waterman @ Baseline
- Haven @ Alta Loma
- Waterman @ 9th Street
- 5th Street @ Waterman
- 5th Street @ Sepulveda
- Sierra Way @ 5th Street
- 5th Street @ Arrowhead Avenue
- 2nd Street @ Kendall
- Mt Vernon @ Rialto Avenue
- Mt Vernon @ Mill
- Mt Vernon @ La Cadena
- Mt Vernon @ Laurel
- Mt Vernon @ Palm
- Mt Vernon @ D Street
- Mt Vernon @ H Street
- Valley @ Mt Vernon
- Valley @ 12th Street
- Valley @ 10th Street
- Valley @ La Cadena
- Valley @ 7th Street
- Valley @ 4th Street
- and 2033 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 | 67.0 | first check |
| 2026-07-30 | 88.0 | up 21.0 |
| 2026-08-01 | 88.0 | no change |
| 2026-08-02 | 88.0 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience 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.
What changed over time
On 2026-07-25 this feed started at grade D. On 2026-07-30 the grade moved from D to B. As of 2026-08-02 it holds grade B.
A plain-language history of this feed, newest first.
- 2026-07-30 Grade went D to B, freshness rose 75 points.
Everything we checked
9 findings, ordered by severity.
Show every finding
- Warning91 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning6 instances
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)
- Warning3 instances
Unexpected enum value (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unexpected_enum_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: unexpected_enum_value · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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.)
Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Many of the feed's trips don't run at all in the next 7 days.
It usually means old service periods are still in the export, making the feed bigger and harder to check.
Fix: Trim past service periods the next time you export. (One setting in most export tools.)
Finding code: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules 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
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.)
Finding code: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Future calendar (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'future_calendar' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: future_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Future feed (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'future_feed' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: future_feed · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
NTD GTFS readiness Ready
Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Ready
- Service data covers the next 154 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 3442 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 Awarded
This feed earns the conformance mark: valid, current, and stating wheelchair access on nearly every stop and trip.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 154 days.
- Accessible Met
- States wheelchair access on 100% of stops and 100% of trips.
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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 154 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.
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 (6 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.
- Meets Produce no critical errors in the MobilityData GTFS Validator
Passes validation with no errors.
- 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.
- Meets Designate a technical contact in feed_info.txt's feed_contact_email
feed_info.txt states a technical contact.
- Meets wheelchair_boarding stated on stops and trips
States wheelchair access on 100% of stops and 100% of trips.
- Meets shapes.txt with a shape for every trip
All 3442 trips have a shape in shapes.txt.
- Meets Fare data published, or the service marked fare-free
Fare data is published.
- Correctness 72 / 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 100 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Not yet published
- 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/omnitrans/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.