Feed status · checked 2026-08-02
Embark
Based on the feed this agency publishes
Service mode Tram + Bus + Ferry
up 0.2 since 2026-08-01 · B → B
Catalogued in Oklahoma.
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 13 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
Review the rule documentation for 'missing_bike_allowance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Missing bike allowance (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +8 points in its category
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').Likely your export tool
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.
⏱ Often a bulk fix in your scheduling software.worth about +6 points in its category
Turn on 'remove unused shapes' (or the like) in your export tool.Likely your export tool
The feed contains route shapes no trip uses. Harmless to riders, but it bloats the feed and suggests stale export data.
⏱ One setting.worth about +6 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
- Missing bike allowance (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'missing_bike_allowance' 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
- Some rider-facing names are in ALL CAPS or all lowercase.
- Next action
- Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').
- 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 feed contains route shapes no trip uses.
- Next action
- Turn on 'remove unused shapes' (or the like) in your export tool.
- 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 'missing_bike_allowance' 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.
Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). · 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.
Turn on 'remove unused shapes' (or the like) in your export tool. · 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.
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 365 days.
- Published accessibility data
- Accessibility information is stated for 89.6% of stops and 96.8% 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.
Ungraded capability read
Ferry data profile
A ferry-specific view of what this GTFS feed publishes. Schedule measurements use ferry routes and trips only; fare and realtime facts are labelled as whole-feed. Unknown values are not treated as no.
- Ferry service
- 2 routes · 70 trips
- Terminal structure
- 5 ferry boarding locations; no parent-station hierarchy is published.
- Terminal access
- Not applicable: no ferry boarding location is linked to a parent station, so stop_access is not permitted here.
- Published accessibility
- Unknown: none of the 5 ferry boarding locations publish wheelchair_boarding. 100% of ferry trips publish a value; 100% of all ferry trips explicitly say allowed (70 of 70). Unstated values remain unknown. This reports published values, not verified physical usability.
- Bicycles
- Unknown: none of the 70 ferry trips publish bikes_allowed.
- Cars
- Unknown: none of the 70 ferry trips publish cars_allowed.
- Fares
- Whole feed: applied fare data is published using GTFS Fares v2.
- Realtime
- Whole feed: no GTFS-Realtime endpoints are configured in this scorecard.
Descriptive only. This profile does not change the grade or verify vessels, terminal facilities, vehicle carriage, fares, or accessibility in the real world. Field meanings follow the GTFS Schedule reference.
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 153 instances (0 error, 134 warning, 19 informational).
Service data covers the next 365 days.
90% of stops state wheelchair accessibility (90% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
90% of stops state accessibility (90% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
21 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (002, 008, 011, 012, 013, 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.
1527 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("S Walker Ave @ SW 44 St", "S May Ave @ I-240 Service Rd", "SW 29 St @ S May Ave", 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.
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 1644 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.
- 40 (teal)
- 42 (blue)
- 32 (purple)
- 52 (black)
- 2 (green)
- 1 (blue)
- 6 (gray)
- 3 (brown)
- 4 (yellow)
- 100X (pink)
- 5 (pink)
- 002 (green)
- 003 (teal)
- 007 (purple)
- 008 (pink)
- 009 (gray)
- 010 (green)
- 011 (teal)
- 012 (pink)
- 013 (orange)
- 014 (gray)
- 015 (pink)
- 016 (red)
- 018 (teal)
- 019 (purple)
- 022 (gray)
- 023 (red)
- 024 (gray)
- 038 (orange)
- 040 (green)
- 110 (pink)
- 111 (green)
- 112 (purple)
- 121 (teal)
- 122 (orange)
- 13N (orange)
- 144 (red)
- RAPID (yellow)
- 23N (red)
- BL (teal)
- DL (red)
- ERRC (teal)
- WRRC (teal)
| Route | Type | Line color |
|---|---|---|
| 40 LLOYD NOBLE SHUTTLE | Bus | teal |
| 42 RESEARCH ROUTE | Bus | blue |
| 32 APARTMENT LOOP | Bus | purple |
| 52 CAMPUS LOOP | Bus | black |
| 2 Route 2 | Bus | green |
| 1 Route 1 | Bus | blue |
| 6 Route 6 | Bus | gray |
| 3 Route 3 | Bus | brown |
| 4 Route 4 | Bus | yellow |
| 100X Route 100X Expresslink | Bus | pink |
| 5 Route 5 | Bus | pink |
| 002 N COLTRANE | Bus | green |
| 003 N KELLY | Bus | teal |
| 007 N MAY | Bus | purple |
| 008 N PENN/NW 63RD | Bus | pink |
| 009 W RENO CROSSTOWN | Bus | gray |
| 010 N PORTLAND | Bus | green |
| 011 S 29 ST CROSSTOWN | Bus | teal |
| 012 S MAY | Bus | pink |
| 013 S WESTERN/OCCC | Bus | orange |
| 014 SE 44 ST/SUNNYLANE | Bus | gray |
| 015 MIDWEST CITY | Bus | pink |
| 016 S PENN | Bus | red |
| 018 LINCOLN | Bus | teal |
| 019 SPENCER | Bus | purple |
| 022 ML KING/OCCHD | Bus | gray |
| 023 23RD ST CROSSTOWN | Bus | red |
| 024 NORMAN EXPRESS | Bus | gray |
| 038 N 10 ST CROSSTOWN | Bus | orange |
| 040 S WALKER | Bus | green |
| 110 MAIN S/24 NW | Bus | pink |
| 111 E LINDSEY/ALAMEDA | Bus | green |
| 112 W LINDSEY/NW 36 | Bus | purple |
| 121 WESTHEIMER AIRPORT | Bus | teal |
| 122 12 NE/ROCK CREEK RD | Bus | orange |
| 13N S WESTERN/SW 104 | Bus | orange |
| 144 SOCIAL SECURITY | Bus | red |
| RAPID NORTHWEST RAPID | Bus | yellow |
| 23N 23 CROSSTOWN NIGHT | Bus | red |
| 302 THUNDER SHUTTLE | Bus | teal (no shape in feed) |
| 303 WCWS EVENT EXPRESS | Bus | gray (no shape in feed) |
| 304 S 29 ST CROSSTOWN RR DETOUR | Bus | teal (no shape in feed) |
| BL BRICKTOWN LOOP | Tram / light rail | teal |
| DL DOWNTOWN LOOP | Tram / light rail | red |
| ERRC EAST ROUTE OKLAHOMA RIVER CRUISE | Ferry | teal |
| TSL THUNDER SHUTTLE LOOP | Tram / light rail | teal (no shape in feed) |
| WRRC WEST ROUTE OKLAHOMA RIVER CRUISE | Ferry | teal |
List every stop
- S Walker Ave @ SW 44 St
- S May Ave @ I-240 Service Rd
- SW 29 St @ S May Ave
- SW 74 St @ S Kentucky Ave
- SW 74 St @ S Blackwelder Ave
- SW 74 St @ S Walker Ave
- S Western @ SW 66 St
- S Central Ave @ SE 21 St
- S May Ave @ SW 44 St
- S High Ave @ SE 19 St
- S High Ave @ SE 29 St
- SE 44 St @ Cinderella Dr
- SE 44 St @ S Madera Blvd
- SE 59 St @ S Bryant Ave
- S Western Ave @ SW 74 St
- SE 44 St @ S Sunnylane Rd
- SE 44 St @ S Eastern Ave
- SE 44 St @ Foster Rd
- S Western Ave @ SW 44 St
- S High Ave @ SE 25 St
- SE 15 St @ S Byers Ave
- S Central Ave @ SE 15 St
- S Central Ave @ SE 20 St
- Transit Center-Bay D
- S Robinson Ave @ SW 13 St
- S Robinson Ave @ SW 7 St
- Exchange Ave @ W Reno Ave
- SW 89 St @ Walker
- S Western Ave @ SW 44 St
- SW 29 St @ S Barnes Ave
- SW 74 St @ S Western Ave
- S Pennsylvania Ave & SW 55 St
- S Sunnylane Rd @ SE 59 St
- S Pennsylvania Ave @ SW 62 St
- S Pennsylvania Ave @ SW 66 St
- S Pennsylvania @ SW 72 St
- SE 44 St @ S Bryant Ave
- S Pennsylvania Ave @ Flair Dr
- S Pennsylvania Ave @ SW 87 St
- S High Ave @ SE 44 St
- S Pennsylvania Ave @ SW 78 St
- N Pennsylvania Ave @ NW 63 St
- SE 15 St @ S High Ave
- S Pennsylvania Ave & SW 39 St
- S Pennsylvania Ave @ SW 31 St
- SW 29 St @ S Pennsylvania Ave
- S Kentucky Ave @ SW 27 St
- S Kentucky Ave @ SW 22 St
- Westwood Blvd @ SW 15 St
- N Lincoln Blvd @ Stanton L Young Blvd
- N Lincoln Blvd @ NE 16 St
- N Lincoln Blvd @ NE 19 St
- N Lincoln Blvd @ NE 30 St
- N Lincoln Blvd @ Stanton L Young Blvd
- N Lincoln Blvd @ NE 34 St
- N Lincoln Blvd @ NE 38 Terr
- N Lincoln Blvd @ NE 39 St
- S High Ave @ SE 15 St
- N Kelley Ave @ Clover Ln
- E Britton Rd @ N Kelley Ave
- S Santa Fe Ave @ SW 104 St
- SE 44 St @ S High Ave
- E Britton Rd @ N Oklahoma Ave
- Broadway Ext Service Rd @ NW 85 St
- Broadway Ext Service Rd @ W Wilshire Rd
- Broadway Ext Service Rd @ NW 71 St
- S Bryant Ave @ SE 44 St
- N Lincoln Blvd @ NE 46 St
- N Lincoln Blvd @ Woodland Dr
- N Lincoln Blvd @ NE 42 St
- N Douglas Blvd @ E Reno Ave
- N Lincoln Blvd @ NE 36 St
- N Lincoln Blvd @ E Hill St
- Chesapeake/Lawrence (westbound)
- Traditions East/Kraettli Apts. - North Stop (southbound)
- Traditions East/Kraettli Apts. - South Stop (southbound)
- N Lincoln Blvd @ NE 10 St
- E Reno Ave @ Midwest Blvd
- S Walker Ave @ SW 5 St
- S Walker Ave @ SW 7 St
- S Walker Ave @ SW 10 St
- S Walker Ave @ SW 23 St
- S Shields Blvd & SE 29 St
- S Shields Blvd & SE 33 St
- S Shields Blvd & SE 37 St
- S Shields Blvd @ SE 41 St
- Transit Center-Bay H
- Adair Blvd @ Peppertree Ln
- S Walker Ave @ SW 14 St
- NW 4 St @ N Broadway Ave
- SE 15 St @ S Air Depot Blvd
- NE 4 St @ N Bath Ave
- S Pennsylvania Ave @ SW 89 St
- N Martin Luther King Ave @ NE 19 St
- N Martin Luther King Ave @ NE 24 St
- N Martin Luther King Ave @ NE 26 St
- N Martin Luther King Ave @ NE 30 St
- S Santa Fe @ SW 89 St
- S Pennsylvania Ave @ SW 74 St
- S Pennsylvania Ave @ SW 43 St
- N Martin Luther King Ave & NE 50 St
- N Martin Luther King Ave @ NE 48 St
- N Martin Luther King Ave @ Springlake Dr
- N Martin Luther King Ave @ NE 37 St
- Exchange Ave @ Westwood Blvd
- NE 4 St @ N Wisconsin Ave
- NE 4 St @ N High Ave
- NE 4 St @ N Lindsey Ave
- Broadway Ext Service Rd @ W Britton Rd
- N Kelley Ave @ NE 20 St
- N Kelley Ave @ NE 21 St
- NW 23 St @ N Roff Ave
- NW 23 St @ M Lee Ave
- NW 23 St @ N Francis Ave
- NW 23 St @ N Gatewood Ave
- NW 23 St @ N Drexel Blvd
- NW 23 St @ NW Grand Blvd
- NW 23 St @ N Portland Ave
- NW 23 St @ N Ann Arbor Ave
- N Lincoln Blvd @ NE 50 St
- NW 23 St @ N Dittmer Rd
- NW 23 St @ N MacArthur Blvd
- NW 10 St @ Eighty Niner Dr
- NW 16 St & N Rockwell Ave
- NW 16 St @ N McKinley Ave OB
- N MacArthur Blvd @ NW 16 St
- N MacArthur Blvd @ NW 19 St
- NW 23 St @ N Moulton Dr
- NW 23 St @ N Sterling Ave
- Transit Center-Bay K
- NW 23 St @ N Minnie Ln
- NW 23 St @ N Walker Ave
- NW 23 St @ N Geraldine Ave
- NW 23 St @ N Tulsa Ave
- NW 23 St @ N Cross Ave
- NW 23 St @ N Youngs Blvd
- Classen & NW 23rd
- N Lincoln Blvd @ NE 50 St
- NE 23 St @ N Santa Fe Ave
- N Lincoln Blvd @ NE 13 St
- S Meridian Ave @ Enterprise Pl
- NW 10 St @ N Portland Ave
- NW 10 St @ N Tulsa Ave
- NE 23 St @ N Martin Luther King Ave
- NW 10 St @ Sterling Ave
- NW 10 St @ N Purdue St
- NE 23 St @ Workforce Oklahoma
- NW 10 St @ N Douglas Ave
- NE 36 St @ N Richardson Ave
- SE 25 St @ S Shields Blvd
- S Walker Ave & SW 32 St
- S Walker Ave @ SW 36 St
- NE 39TH @ N Hiwassee Rd
- S Walker Ave @ SW 64 St
- S Walker Ave @ SW 83 St
- S Walker Ave @ SW 87 St
- SW 104 St @ S Western Ave
- NE 23 St @ N Martin Luther King Ave
- S Walker Ave @ SW 53 St
- NE 36 St @ Adair St
- S Walker Ave @ SW 48 St
- S Walker Ave @ SW 40 St
- NW 10 St @ N Rockwell Ave
- NW 23 St @ N Ann Arbor Ave
- NW 64 St @ Lyrewood Ln
- Lyrewood Ln @ Galaxie Dr
- Lyrewood Ln @ Knight Lake Dr
- Lyrewood Ln @ Decon Ave
- NW 63 St @ N MacArthur Blvd
- NW 63 St @ N Ann Arbor Ave
- NW 63 St @ N Libby Ave
- S Shields Blvd @ SE 44 St
- N Pennsylvania Ave @ NW 59 St
- N Pennsylvania Ave @ NW 56 Terr
- N Pennsylvania Ave @ NW 47 St
- Transit Center-BAY C
- N Pennsylvania Ave @ NW 31 Terr
- N Pennsylvania Ave @ NW 36 St
- N Pennsylvania Ave @ NW 40 St
- NW 63 St @ N Portland Ave
- NW 63 St @ N MacArthur Blvd
- NW 63 St @ N College Ave
- N Prospect Ave @ NE 48 St
- N Prospect Ave @ Springlake Dr
- Festival Market Place
- Crest Foods
- 15th & Fretz Dr
- Fretz & 4th St
- Fretz & 9th St
- Fretz & Rob Ln
- Coffee Creek Apts / Fretz Ave
- Coffee Creek Apts
- 15th & Kelly Ave
- 15th & Kelly Park Rd
- Edmond Santa Fe High School
- 15th & Whispering Creek Dr
- 15th & Renaissance Blvd
- 15th & State St
- Coffee Creek Apts / Fretz Ave
- Fretz & Bryan Dr
- Fretz & 8th St
- Old Towne Lofts
- East Side Fretz & 2nd St
- Post Office
- Littler & Ayers St
- Boulevard & Danforth Rd
- Santa Fe & Danforth Rd
- Wal-Mart
- Fretz & Danforth Rd
- Danforth & Broadway
- Boulevard & Colcord Ave
- Boulevard & Thatcher St
- Bricktown Brewery
- Bryant Square North End
- Vista & Tuscan Ln
- UCO Central Plaza
- Freddies
- Kickingbird Plaza
- OU Hospital
- Walmart Neighborhood Market 2nd St
- S&B Burgers
- Oxford Oaks Apts
- Public Safety Center
- Fink Park
- Oxford Oaks Shopping Center
- 2nd St & Coltrane Rd
- Holiday Inn Express
- Shoppes at Fox Lake
- Sam's
- Wal-Mart I35
- Mercy North Complex
- Mercy South Complex
- Integris Main Complex
- Integris and Spring Creek Trail Head
- Bradbury Station
- Bryant & 9th St
- Pelican Bay
- Bryant & Devonshire Ct
- 15th & Spring Creek
- Spring Creek Apts
- Kilpatrick Bank
- Broadway & 10th St
- Broadway & 8th St
- University & Chowning Ave
- UCO Tennis Court
- Ayers St & Chartrand Ave
- Ayers St & Blackwelder Ave
- Bryant Place Apts
- Kickingbird Hills Apt
- Northside Kickingbird
- and 1394 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — up 0.2 since 2026-08-01.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 83.4 | first check |
| 2026-07-30 | 83.6 | up 0.2 |
| 2026-08-01 | 83.4 | down 0.2 |
| 2026-08-02 | 83.6 | up 0.2 |
What changed since your last check
- Correctness up 0.6
- Freshness no change
- Rider experience no change
What changed in this feed
Overall score rose 0.2 points since 2026-08-01.
The feed file was re-published since 2026-08-01.
No longer reported since 2026-08-01 (1 finding)
- Some service dates fall outside the date window set in feed_info.txt. (service_window_outside_feed_period)
This records the later feed state. It does not establish who made a change or why.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
10 findings, ordered by severity.
Show every finding
- Warning387 instances
387 of 12084 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the transit vehicle 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)
- Warning171 instances
171 of 1644 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)
- Warning70 instances
Missing bike allowance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_bike_allowance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: missing_bike_allowance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning36 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)
- Warning15 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Turn on 'remove unused shapes' (or the like) in your export tool. (One setting.)
Finding code: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning10 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no transit vehicle is scheduled to arrive.
Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)
Finding code: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Same route and agency url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_route_and_agency_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: same_route_and_agency_url · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some service calendars have no days of the week switched on.
Trips tied to these calendars never run; they are dead data that can mask real schedule problems.
Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)
Finding code: service_has_no_active_day_of_the_week · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info17 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)
- Info2 instances
The feed has a stretch of two weeks or more with no service running.
A long gap can mean dates were left out of the calendar. Apps then show no trips on those days.
Fix: Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar. (A review of your calendar dates.)
Finding code: big_gap_in_service · Read the fix guide · 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 365 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 12084 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. States wheelchair access on 90% of stops and 97% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 365 days.
- Accessible Not yet
- States wheelchair access on 90% of stops and 97% 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.
- 10 of 1644 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.
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 has 365 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.
- Correctness 65 / 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 97 / 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/embark-2062/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.