Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
Coralville Transit
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 84% of all tracked agencies and 84% of mid-size agencies. Operates in Iowa.
A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.1, validator 8.0.1.
Checked for changes 10 hours ago; last changed 8 days ago.
Top things to fix
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
117 of 117 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
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).Likely your export tool
159 of 159 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ Often one default setting in your export.worth about +15 points
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
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.
The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
⏱ A small file for most flat-fare systems.worth about +15 points
Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
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. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Send Trillium a fix request
This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 1 kind of issue across 1 instance (0 error, 1 warning, 0 informational).
Service data covers the next 174 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.
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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 20 (purple)
- 21 (pink)
- 23 (yellow)
- 22 (teal)
- 24 (green)
- 25 (teal)
| Route | Type | Line color |
|---|---|---|
| 20 Iowa River Landing | Bus | purple |
| 21 5th Street | Bus | pink |
| 23 10th Street | Bus | yellow |
| 22 North Liberty | Bus | teal |
| 24 Night | Bus | green |
| 25 Saturday | Bus | teal |
This feed has 117 stops.
List every stop
- 12th Avenue and 6th Street
- Downtown Interchange
- Softball Complex
- Macbride Hall
- IMU
- Iowa Ave - English Philosophy Building IMU
- Elliot St @ Carver Hawkeye Arena
- Newton & Lincoln
- Dental College
- Newton Rd - VA Hospital
- Newton Rd - MERF
- Newton Rd Ramp
- Newton Rd - UI Student Health
- 12th Ave & Liberty Ln
- Holiday Rd & Oak Lake Park Rd
- Holiday Rd & Oak Lake Park Rd
- Holiday Rd & Westview
- Holiday Rd & Eastview
- Holiday Rd & High Country Rd
- 1st Ave & 5th St
- 1st Ave & 5th St
- 6th St & 1st Ave - Scotch Pine
- 6th St & 1st Ave
- 6th St & 4th Ave
- 6th St & 4th Ave - Scotsdale
- 7th St & 4th Ave Place
- 7th St & 4th Ave Place
- 7th St & 6th Ave
- 7th St & 7th Ave
- 7th St & 7th Ave
- 7th St & 10th Ave
- 7th St & 10th Ave
- 7th St & 12th Ave
- 12th Ave & 7th St
- 14th Ave & 8th St
- 14th Ave & 9th St
- 14th Ave & 9th St
- 14th Ave & 10th St
- 10th St & 17th Ave
- 10th St & 20th Ave
- 10th St & 20th Ave
- 10th St & 22nd Ave
- 10th St & 22nd Ave
- 10th St & 23rd Ave
- 10th St & North Boston Way
- 10th St & 25th Ave
- Coral Ridge Mall
- 10th St & South Boston Way
- 9th St & 20th Ave
- 20th Ave & 9th St
- 20th Ave & 8th St
- 8th St & 20th Ave
- 20th Ave & 5th St
- 20th Ave & 5th St
- 5th St & 7th St - City Hall
- 5th St & 8th Ave
- 5th St & 4th Ave
- Commerce Dr & Commercial Park
- Heartland Place & Heartland Dr
- Holiday Rd & North Coral St - Hope House
- 12th Ave & Holiday Rd
- 12th Ave & Ozark Ridge
- 12th Ave & Ozark Ridge
- 12th Ave & 10th St
- Front St & Vandello Dr
- Front St & Vandello Dr
- Front St & Weston Dr
- Front St & Weston Dr
- Front St & Zeller St
- Front St & Zeller St
- Front St & Cherry St
- Front St & Cherry St
- North Liberty Rec Center
- Golfview Dr & Heidi Ln
- Golfview Dr & Rebecca St
- Golfview Dr at the Holiday MH Park
- Golfview Dr at the Holiday MH Park
- Fairview Ln & Augusta Circle
- Sugar Creek Ln & Augusta Cir
- Sugar Creek Ln & Praire Ridge Rd
- Sugar Creek Ln & Praire Ridge Rd
- Sugar Creek Ln & W Zeller St
- W Zeller St & Sugar Creek Ln
- Intermodal
- 5th St & 8th Ave
- 5th St & 3rd Ave
- Hardin Library
- Pappajohn Biomedical Discovery Building
- Hubbard Park
- 1st Ave & Highway 6
- 10th St & 23rd Ave
- Holiday Rd & 1st Ave
- 10th St & 12th Ave
- Sugar Creek Ln & Augusta Cir
- 22nd Ave & 10th St
- 10th St & 14th Ave
- Holiday Rd & 1st Ave
- Holiday Rd & Olde Hickory Rd
- Holiday Rd & 12th Ave
- Commercial Park & Heartland Dr
- Fairview Ln & Andrews Ct
- 8th St & 14th Ave
- 7th Street & 12th Avenue
- Ponseti Way
- 9th St & Ponseti Way
- 8th Street and 14th Ave.
- 14th Ave and 7th Street
- 7th Street and 14th Ave
- 7th Street and 5th Street
- 18th Ave/5th Street
- 5th Street/18th Ave
- 18th Ave/8th Street
- 9th St & 21th Ave Place
- Corridor Way
- 9th St & 21st Ave Pl
- 22nd Ave & 9th St (NB)
- 22nd & 9th Ave (SB)
Over time
Overall score across the last 9 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-30 | 81.1 | first check |
| 2026-07-01 | 81.1 | no change |
| 2026-07-02 | 81.1 | no change |
| 2026-07-04 | 81.1 | no change |
| 2026-07-05 | 81.1 | no change |
| 2026-07-06 | 81.1 | no change |
| 2026-07-07 | 81.1 | no change |
| 2026-07-08 | 81.1 | no change |
| 2026-07-09 | 81.1 | 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-07-08.
Same feed file as 2026-07-08; 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
- Warning159 instances
159 of 159 trips don't say whether the vehicle is wheelchair accessible.
Even with accessible stops, riders need to know the bus itself can take them.
Fix: Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning117 instances
117 of 117 stops don't say whether a wheelchair user can board there.
Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1 instance
Some service calendars in the feed have already expired.
Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
102 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Newton Rd - UI Student Health", "Newton Rd Ramp", "Newton Rd - VA Hospital", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
NTD certification readiness Ready
Published at a public URL, valid, and current: the three things the NTD GTFS requirement asks of a feed all hold here. Only your own D-10 certification makes 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 174 days.
- agency_id matches your NTD ID Not checked yet
- Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed is close to the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 174 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.
Clears the Google and Apple Maps four-week coverage bar. This feed has 174 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
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.
- Correctness 96 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 100 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 45 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: 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 live badge on your agency site or feed README. It updates daily and links back to this scorecard.
Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.
Cite this record
This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/coralville-transit-196/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.