Feed status · checked 2026-08-01
EZ Rider
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Texas.
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 11 hours ago; last changed 41 days 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
Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Block trips with overlapping stop times (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +24 points in its category
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
652 of 652 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.worth about +25 points in its category
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool
288 of 288 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 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
- Block trips with overlapping stop times (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'block_trips_with_overlapping_stop_times' 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
- Feed evidence
- 652 of 652 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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
- 288 of 288 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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.
Review the rule documentation for 'block_trips_with_overlapping_stop_times' 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. Self-check a feed before you publish.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · 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.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · 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 states that service is published through 2050-12-30. This may be intentional or a placeholder; confirm current service with the transit operator.
- 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
- 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 9 kinds of issue across 157 instances (84 error, 41 warning, 32 informational).
Service is published through 2050-12-30. It may be intentional, but confirm the end date before treating the feed as maintained.
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.
2 accessibility depth signals
8 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (Odessa Special Event 1, Midland Special Event 1, Odessa Special Event 2, Midland Special Event 2, Odessa 1, 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.
596 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("1- Grant & 11th", "2- Grant & 14th", "3- Grant & 17th", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
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.
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 652 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.
- Odessa 2 (yellow)
- Odessa 3 (green)
- Odessa 4 (teal)
- Odessa 6 (pink)
- Odessa 1 (black)
- Odessa 5 (red)
- Odessa Connect (blue)
- Midland Connect (blue)
- Midland 1 (blue)
- Midland 2 (yellow)
- Midland 3 (green)
- Midland 4 (teal)
- Midland 6 (pink)
- Midland 5 (red)
| Route | Type | Line color |
|---|---|---|
| Odessa 2 | Bus | yellow |
| Odessa 3 | Bus | green |
| Odessa 4 | Bus | teal |
| Odessa 6 | Bus | pink |
| Odessa Special Event 1 | Bus | blue (no shape in feed) |
| Midland Special Event 1 | Bus | blue (no shape in feed) |
| Odessa Special Event 2 | Bus | blue (no shape in feed) |
| Midland Special Event 2 | Bus | blue (no shape in feed) |
| Odessa 1 | Bus | black |
| Odessa 5 | Bus | red |
| Odessa Connect | Bus | blue |
| Midland Connect | Bus | blue |
| Midland 1 | Bus | blue |
| Midland 2 | Bus | yellow |
| Midland 3 | Bus | green |
| Midland 4 | Bus | teal |
| Midland 6 | Bus | pink |
| Midland 5 | Bus | red |
List every stop
- 1- Grant & 2nd
- 10- Wilson & Bankhead
- 6- University & Jackson
- 7- University & Tom Green
- 8- University & Center
- 9- University & Kay
- 10- University & Maple
- 11- University & Windsor
- 12- University & Dawn
- 13- University & Bonham
- 14- University & Grandview
- 11- Bankhead & Drury
- 16- University & Halifax
- 18- University & Haywood
- 19- University & JBS Parkway
- 20- University (J. Patterson Designs)
- 24- UTPB Main & UTPB Circle
- 26- Preston & 42nd
- 27- 42nd & JBS Parkway
- 12- Bankhead & Clements
- 30- JBS Parkway (Wells Fargo)
- 25- UTPB Circle (Library)
- 21- JBS Parkway & Oakwood
- 22- Oakwood & Sunnygrove
- 13- Clements & Lauderdale
- 33- University & JBS Parkway
- 34- University & Fair Oaks
- 35- University & Englewood
- 36- University & Verde
- 37- University & Redbud
- 38- University & Dawn
- 39- University & Eastover
- 40- University & Maple
- 41- University & Brentwood
- 14- Clements & Hickory
- 42- University & Roger
- 43- University & Adams
- 44- University & Hancock
- 45- Andrews HWY & 23rd
- 47- Grant & 13th
- 1- 7th & Grant
- 2- 7th & Jackson
- 3- 7th & Muskingum
- 4- 8th & Adams
- 15- Clements & Fall
- 5- 8th & Jefferson
- 6- 8th & Lettie Lee
- 7- 8th & Dixie
- 8- 8th & Hillcrest
- 9- 8th & Royalty
- 10- 8th & McKinley
- 12- 8th & Express Way
- 16- Clements (Ector Junior High)
- 13- Meadows (Apartments)
- 14- 11th & Tower
- 15- 11th & Grandview
- 16- Grandview & Beechwood
- 17- Grandview & 16th
- 18- Grandview & 21st
- 19- Grandview & 26th
- 20- Grandview & Brentwood
- 21- Grandview & Kenwood
- 22- Grandview & Candy
- 17- Clements & Crane
- 23- Grandview & 37th
- 24- Grandview & 42nd
- 25- Grandview & Richmond
- 26- Grandview & Mayer
- 27- 52nd & Grandview
- 28- 52nd & Arbor
- 29- 52nd & Esmond
- 30- 52nd (Cimarron Place)
- 31- 52nd (Twin Towers)
- 18- Clements & Washington
- 32- JBS Parkway & Plaza
- 33- Tanglewood & Esmond
- 34- Tanglewood & 50th
- 35- Tanglewood & 52nd
- 36- 52nd & Tanglewood
- 37- 52nd (Sherwood Place)
- 38- 52nd & Arbor
- 39- Grandview & 46th
- 40- Grandview & Lyndale
- 41- Grandview & 42nd
- 19- Clements & Lincoln
- 42- Grandview & 37th
- 43- Grandview & Everglade
- 2- Grant & Murphy
- 20- Grant & Midland
- 21- Monahan's & Texas
- 32- Fitch & Ave De Mexico
- 1- 5th & Washington
- 2- Golder & 4th
- 3- 2nd & Whitaker
- 4- Whitaker & 3rd
- 5- Whitaker & 6th
- 6- 8th & Belmont
- 33- Blackshear & Wabash
- 7- 8th & Lasseter
- 8- W County rd. & 6th
- 9- 3rd & W County rd.
- 10- 3rd & Vine
- 11- 3rd & MacArthur
- 12- Harless & 4th
- 13- Harless & 10th
- 14- Harless & 12th
- 15- Harless & 13th
- 16- Harless & 14th
- 34- Washington & Lubbock
- 17- Harless & 16th
- 18- 16th & Alameda
- 19- 16th & Linda
- 22- University & Conover
- 23- University & Madera
- 24- University (7-11)
- 25- W County rd. (First Basin Bank)
- 26- W County rd. & Kermit
- 35- Washington & Murphy
- 27- W County rd. & 38th
- 28- 42nd & W County rd.
- 29- Golder & 42nd
- 30- Golder & 38th
- 32- Golder & 30th
- 33- University & Kermit
- 34- Kermit & Pleasant
- 35- Kermit & W County rd.
- 36- W County rd & University
- 3- Grant & May
- 37- W County rd. & San Andres
- 38- W County rd. & 24th
- 39- W County rd. & 20th
- 40- W County rd. & Santa Rita
- 41- W County rd. & 13th
- 42- W County rd. & 10th
- 43- 8th & Kelly
- 44- 8th & Whitaker
- 45- 8th & Bernice
- 37- Murphy & Grandview
- 1- Wall & Carrizo Street
- 2- Wall & "C" Street
- 3- Wall & "F" Street
- 4- Wall & "I" Street
- 5- Wall & "L" Street
- 6- Wall & Andrews
- 7- Wall & Truman
- 8- Wall & Powell
- 9- Wall & Crestview
- 10- Wall & Midkiff
- 11- 80 svc rd. & Fasken
- 12- 80 svc rd (Rogers Ford)
- 13- 80 svc rd. (Grand Texan)
- 14- Midland & Seminole
- 15- Midland & Comanche
- 42- Pearl (Coca Coloa Bldg)
- 16- Midland & Pleasant
- 17- Midland & Erie
- 18- Thomason & Monty
- 19- Thomason & Bentwood
- 20- Thomason & Shadylane
- 21- 250 svc rd. N & Storey
- 22- 250 svc rd. N & 2nd Driveway
- 24- 250 svc rd. N (La Quinta)
- 25- 250 svc rd. N & Princeton
- 43- JSB Parkway (Candlewood)
- 28- 250 svc rd. N (Target)
- 29- 250 svc rd. S & Midland
- 30- 250 svc rd. S (Clusters)
- 31- 250 svc rd. S & Amistad
- 32- 250 svc rd. S & Livington
- 33- 250 svc rd. S (Newport)
- 34- 250 svc rd. S & Wadley
- 35- 250 svc rd. S & Grassland
- 36- 250 svc rd. S & 191 svc rd. W
- 44- JBS Parkway & Interstate 20
- 37- Andrews & Westcliff
- 46- Midland & Illinois
- 39- Midland & Princeton
- 40- Midland & Crockett
- 42- Midland & Leddy
- 43- Midland & Tanner
- 44- Thomason & Devonion
- 45- Thomason & Raymond
- 46- Thomason & Howard
- 47- Thomason & Anetta
- 48- Wall (Executive Inn)
- 49- Wall & Williams
- 50- Wall & Bankhead
- 52- Wall & Missouri
- 53- Wall & Andrews
- 54- Wall & "L" Street
- 1- Illinois & Main
- 2- Illinois & Colorado
- 3- Illinois & Carrizo
- 4- Illinois & "D" Street
- 5- Illinois & "F" Street
- 6- Illinois & Broadway
- 7- Illinois & "N" Street
- 8- Illinois & Secor
- 9- Illinois & Kessler
- 10- Illinois & Powell
- 11- Illinois & Crestview
- 12- Illinois & Upland
- 46- Dobbs & Electric
- 13- Illinois & Godfrey
- 14- Illinois & Delmar
- 15- Illinois (WWVSC)
- 16- Midland & Illinois
- 17- Midland & Storey
- 18- Cuthbert (AJHS)
- 19- Cuthbert & Bonham
- 20- Cuthbert & Godfrey
- 21- Cuthbert & Upland
- 22- Midkiff & Cuthbert
- 47- Electric & Patterson
- 23- Midkiff & Golf Course
- 24- Midkiff & Ma Mar
- 25- Midkiff & Fannin
- 26- Midkiff & Dengar
- 27- Midkiff & Wadley
- 28- Midkiff & Maxwell
- 29- Midkiff (C.C.F.C.U.)
- 30- Midkiff & Haynes
- 32- Midkiff & Haynes
- 33- Midkiff & Providence
- 4- May & Lincoln
- 48- Murphy & Lindy
- 34- Midkiff & Maxwell
- 35- Midkiff & Wadley
- 36- Midkiff & Dengar
- 37- Midkiff & Ma Mar
- 38- Midkiff & Sinclair
- 39- Midkiff & Sentinel
- 40- Midkiff & Bedford
- 41- Cuthbert & Upland
- 42- Cuthbert & Godfrey
- 43- Cuthbert & Bonham
- 49- Standard & Murphy
- 44- Cuthbert & Delmar
- 45- Midland & Crockett
- 47- Illinois & Delmar
- 48- Illinois & McDonald
- 49- Illinois & Godfrey
- 50- Illinois & Thomas
- 51- Illinois & Crestview
- 52- Illinois & Powell
- 53- Illinois & Kessler
- 54- Illinois & Andrews
- 55- Illinois & "O" Street
- 56- Texas & "H" Street
- 57- Texas & "F" Street
- and 402 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 46.3 | first check |
| 2026-07-30 | 46.3 | no change |
| 2026-07-31 | 46.3 | no change |
| 2026-08-01 | 46.3 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
15 findings, ordered by severity.
Show every finding
- Error84 instances
Block trips with overlapping stop times (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: block_trips_with_overlapping_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning652 instances
652 of 652 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)
- Warning288 instances
288 of 288 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)
- Warning288 instances
288 of 288 trips lack rider-facing destination or direction text.
When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.
Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)
Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning18 instances
Some files leave out fields that GTFS asks for but does not require.
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.)
Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning8 instances
Some trips serve fewer than two stops.
A trip with one stop can't be ridden; planners ignore it and it may signal an export problem.
Fix: Check the flagged trips in your scheduling software; remove them or restore their missing stops. (Worth a vendor question if it appears often.)
Finding code: unusable_trip · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning8 instances
Unused trip (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unused_trip' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: unused_trip · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning4 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.)
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
Fast travel between far stops (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'fast_travel_between_far_stops' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: fast_travel_between_far_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Finding code: missing_recommended_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
On some trips the stops fall along the route line in a different order than the schedule lists.
Trip planners can draw the bus doubling back or skipping ahead, which confuses riders reading the map.
Fix: Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards. (A few minutes per flagged trip.)
Finding code: stops_match_shape_out_of_order · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
feed_info.txt is missing its start/end dates (the file itself is absent)
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.)
Finding code: scorecard_missing_feed_info_dates · 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)
- Info32 instances
Service extends far in the future (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: service_extends_far_in_the_future · 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
- The published window is current, but its service end date is unusually distant; confirm that date is intentional.
- 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 Needs attention
- 280 of 288 trips have a shape; 8 do not. Fill in shapes.txt and trips.shape_id for the remaining trips so every trip has a path. Reduced, Rural, and Tribal NTD reporters need full coverage by Report Year 2026.
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
- The published window is current, but its service end date is unusually distant; confirm that date is intentional.
- 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 8 of 288 trips list fewer than two stops. A trip with one stop has no leg a rider can ride; trip planners can't route anyone on it, so the service effectively does not exist. Check your scheduling export: every trip should list each stop it calls at, in order, with times.
These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.
Clears the Google and Apple Maps four-week coverage bar. This feed clears the four-week coverage window, but its service end date is unusually distant. Confirm that date is intentional before treating it as evidence of ongoing maintenance. The feed also carries 84 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.
- Correctness 41 / 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 85 / 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 22 / 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/ez-rider/2026-08-01.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-01. 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.