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
Metropolitan Transit Authority of Black Hawk County
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 51% of all tracked agencies and 50% of small 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 17 minutes ago; last fetch returned HTTP 404.
Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: provisional.
- Realtime quality was not measured this run. It does not count against the grade.
- The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 2382 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
Populate trip_headsign to match what the bus displays.Likely your export tool
510 of 510 trips have no headsign. Riders at the stop can't tell which direction a bus is going.
⏱ Usually a bulk edit in your scheduling software.worth about +15 points
Remove past service periods the next time you export the feed.Likely your export tool
Some service calendars in the feed have already ended. Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.
⏱ One setting in most export tools.worth about +4 points
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
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.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
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.
Populate trip_headsign to match what the bus displays. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
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.
Remove past service periods the next time you export the feed. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
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 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.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 7 kinds of issue across 16 instances (0 error, 8 warning, 8 informational).
Service data ended 2382 day(s) ago. Trip planners have likely already dropped this feed.
100% of stops state wheelchair accessibility (56% marked accessible, 44% 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 (56% marked accessible). Reflects what the feed states, 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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 1 (teal)
- 10 (blue)
- 11 (pink)
- 12 (blue)
- 2 (red)
- 3 (yellow)
- 4 (yellow)
- 5L (white)
- 5W11 (white)
- 6 (yellow)
- 7 (yellow)
- 8 (gray)
- 9 (purple)
| Route | Type | Line color |
|---|---|---|
| 1 West - BLUE | Bus | teal |
| 10 Hawkeye Community College | Bus | blue |
| 11 UNI Panther Shuttle | Bus | pink |
| 12 UNI Weekend Safe Ride | Bus | blue |
| 2 West - RED | Bus | red |
| 3 East - GREEN | Bus | yellow |
| 4 East - ORANGE | Bus | yellow |
| 5L Crossroads/La Porte Road - TAN | Bus | white |
| 5W11 Crossroads/West 11th Street - TAN | Bus | white |
| 6 Cedar Falls-UNI - YELLOW | Bus | yellow |
| 7 Cedar Falls-Rainbow - YELLOW | Bus | yellow |
| 8 West Loop - GREY | Bus | gray |
| 9 Cedar Falls Loop - PURPLE | Bus | purple |
This feed has 89 stops.
List every stop
- Central Transfer
- W 3rd St and Locust St
- W Park Ave and South St
- Hammond Ave and Easton Ave
- Covenant Hospital
- Kimball Ave and Rachael St
- Pheasant Ln and Olympic Dr
- United Medical Park
- Johnathan St and San Marnan Dr
- St Francis Dr and Wildwood Rd
- Baltimore St and E Ridgeway Ave
- W 4th St and Locust St
- W 5th St and Allen St
- W 6th St and Commercial St
- Oak Ave and Mulberry St
- Burton Ave and Conger St
- Longfellow Ave and Walker St
- Cedar Bend St and W Donald St
- Columbia St and W Donald St
- Crossroads Blvd at SE Loop
- Allen Hospital - Dr Offices
- HyVee at Logan Ave
- Burton Ave and W Parker St
- Fletcher Ave and Campbell Ave
- Broadway St and Center St
- Walnut Court
- Human Services Campus
- Lafayette St and Osage Ave
- Pinecrest - Idaho St and Independence Ave
- Prairie Pkwy and Wild Rye Way
- Mobile St and Newell St
- North Crossing UnityPoint Clinic
- E 4th St and Lime St
- Vinton St and Independence Ave
- Lafayette Park
- Goodwill on Falls Ave
- E 7th St and Franklin St (EB)
- W 11th St and South St
- Crossroads Mall
- Schukei Rd and San Marnan Access Rd
- Hammond Ave and Southtown Dr
- Walmart at Crossroads Mall
- HyVee at Crossroads Mall
- La Porte Rd at E Mitchell Ave
- W 18th St and Commercial St
- Ohio St and E Ridgeway Ave
- Central Intermediate
- Wisconsin St and E Ridgeway Ave
- Fletcher Ave and University Ave (WB)
- Progress Ave and University Ave (WB)
- HyVee at College Square Mall
- Melrose Dr and University Ave (WB)
- UNI Multimodal Transportation Center
- Waterloo Rd and E 18th St
- Greenhill Rd and Rainbow Dr
- Ansborough Ave and Maynard Ave
- Galloway Ave and Rainbow Dr
- Social Security Office
- Main St and 6th St
- Black Hawk Village and University Ave (EB)
- North Star Svcs and Iowa Workforce Dev
- Greenhill Rd and S Hackett Rd
- Veterans Affairs Clinic
- Kimball Ave and Park Ln
- W 9th St and South St
- Main St and W Seerley Blvd
- Arrowhead Medical Center
- Walmart - Walmart Dr and Brandilynn Blvd
- Russell Rd and W Ridgeway Ave
- Purdue University Global
- Hudson Rd and University Ave (NB)
- S Division St and W 8th St
- Thunder Ridge Mall
- Washington St and W 4th St
- Main St and W 18th St
- College St and W Seerley Blvd
- Ohio St and W 31st St
- Dysart Rd and Mills Ln
- Kimball Ridge Center
- Hawkeye Community College - Front
- Hawkeye Community College - Back
- W 3rd St and Fletcher Ave
- UNI-ROTH NE Lot
- Ohio St and Redeker Dr
- The Quarters at CF Apartments
- Hillcrest Apartments
- Campus Courts Apartments
- W 27th St and Hudson Rd
- Washington St and W 2nd St
Over time
Overall score across the last 20 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 60.3 | first check |
| 2026-06-20 | 60.3 | no change |
| 2026-06-21 | 60.3 | no change |
| 2026-06-22 | 60.3 | no change |
| 2026-06-23 | 60.3 | no change |
| 2026-06-24 | 60.3 | no change |
| 2026-06-25 | 60.3 | no change |
| 2026-06-26 | 60.3 | no change |
| 2026-06-27 | 60.3 | no change |
| 2026-06-28 | 60.3 | no change |
| 2026-06-29 | 60.3 | no change |
| 2026-06-30 | 60.3 | no change |
| 2026-07-01 | 60.3 | no change |
| 2026-07-02 | 60.3 | no change |
| 2026-07-04 | 60.3 | no change |
| 2026-07-05 | 60.3 | no change |
| 2026-07-06 | 60.3 | no change |
| 2026-07-07 | 60.3 | no change |
| 2026-07-08 | 60.3 | no change |
| 2026-07-09 | 60.3 | 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
- Error1 instance
Service data ended 2382 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
Validator rule: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning510 instances
510 of 510 trips have no headsign.
Riders at the stop can't tell which direction a bus is going.
Fix: Populate trip_headsign to match what the bus displays. (Usually a bulk edit in your scheduling software.)
Validator rule: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning5 instances
Some service calendars in the feed have already ended.
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
This feed's service calendar runs out within the next 7 days.
When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.
Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)
Agencies here usually clear this within about 1 week (based on 16 observed fixes).
Validator rule: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Missing feed contact email and url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Some 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.)
Agencies here usually clear this within about 2 weeks (based on 8 observed fixes).
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info5 instances
Service window outside feed period (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'service_window_outside_feed_period' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 17 observed fixes).
Validator rule: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 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.)
Validator rule: service_extends_far_in_the_future · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Big gap in service (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'big_gap_in_service' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 13 observed fixes).
Validator rule: big_gap_in_service · 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).
App makers and state data programs 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.)
Agencies here usually clear this within about 1 week (based on 10 observed fixes).
Validator rule: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (2).
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.
64 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("W 4th St and Locust St", "Fletcher Ave and Campbell Ave", "Goodwill on Falls Ave", 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 Not ready
Resolve this before you certify on the D-10. Service data expired 2382 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- Service data expired 2382 days ago, so FTA would find the link out of date.
- 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.
- shapes.txt covers your trips Ready
- All 510 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 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. Service data expired 2382 days ago.
- Valid Met
- Passes validation with no errors.
- Current Not yet
- Service data expired 2382 days ago.
- 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 8941 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 82 / 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 0 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 78 / 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/metropolitan-transit-authority-of-black-hawk-county/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.