Feed status · checked 2026-08-01
Metropolitan Transit Authority of Black Hawk County
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued 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.3, validator 8.0.1.
Checked for changes 1 days ago; last changed 38 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
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
280 of 280 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
396 of 396 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
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.
136 of 396 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.
⏱ Usually one value per route pattern in your scheduling source.worth about +5 points in its category
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.
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
- 280 of 280 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
- 396 of 396 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
- Feed evidence
- 136 of 396 trips lack rider-facing destination or direction text.
- Next action
- 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.
- 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.
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.
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. 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.
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.
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. · 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.
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's last published service date is in 153 days.
- 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
- Fare information is published using GTFS Fares v1.
- 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 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 5 kinds of issue across 49 instances (0 error, 5 warning, 44 informational).
Service data covers the next 153 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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
6 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1B, 10, 4, 5, 6, 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.
223 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Cedar Bend St and Virginia St", "W 4th St and Ansborough Ave (WB)", "Avon Ave and Parker St", 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 280 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.
- 1B (teal)
- 4 (orange)
- 6 (yellow)
- 2 (red)
- 8 (gray)
- 9 (purple)
- 5 (white)
- 3 (brown)
- 1A (teal)
- 10 (orange)
- 7 (yellow)
| Route | Type | Line color |
|---|---|---|
| 1B | Bus | teal |
| 4 | Bus | orange |
| 6 | Bus | yellow |
| 2 | Bus | red |
| 8 | Bus | gray |
| 9 | Bus | purple |
| 5 | Bus | white |
| 3 | Bus | brown |
| 1A | Bus | teal |
| 10 | Bus | orange |
| 7 | Bus | yellow |
List every stop
- Cedar Bend St and Virginia St
- W 4th St and Ansborough Ave (WB)
- Avon Ave and Parker St
- Wildwood Rd and Hammond Ave
- Fletcher Ave and University Ave(WB)
- Ridgeway Ave and Marnie Ave
- W 5th and Bayard St
- Allen Hospital, Entrance 2
- Broadway Ave and Conger St
- HyVee at Crossroads Mall
- Central Transfer
- Falls Ave and University Ave(WB)
- Six Corners
- Six Corners (WB)
- College St and W Seerley Blvd
- Ansborough Ave and University Ave(EB)
- Lincoln Elementary
- W 9th St and E Mitchell Ave
- Oak Ave and Mulberry St
- Parler St and E 4th St
- North Star and Iowa Workforce
- Walnut St and 12th St
- Galloway Ave and Rainbow Dr
- Prairie Pkwy and Prairie View Rd
- Greenhill Rd and Maynard Ave
- Ansborough Ave and Olympic Dr
- W Ridgeway Ave & Kimball Ave
- E 4th St and Adams St
- Rainbow Dr and Waterloo Rd
- Arrowhead Medical Center
- Franklin St and Park Ave
- La Porte Rd and E Ridgeway Ave
- Independence Ave and Vinton St
- Rownd St and University Ave(EB)
- Unity Square Townhomes
- Target - Crossroads
- Williston Ave and W 9th St (WB)
- Ridgeway Ave and Russell Rd
- St Francis Dr & Wildwood Rd
- Mobile St and Sumner St
- Central Transfer
- W 4th St & Fletcher Ave
- Hawkeye Community College - Front
- Cedarloo Shopping Area(EB)
- Jefferson St and 10th St
- Central Intermediate
- Eastgate Estates
- 18th St and Black Hawk St
- Main St and University Ave(EB)
- La Porte Rd and Howard Ave(SB)
- Aldi
- W 3rd St & Locust St
- Lantern Square
- W Park Ave & South St
- UNI Multimodal Transportation Center
- UnityPoint Clinics - North Crossing
- Hudson Rd and Technology Pkwy
- Rainbow Dr and Cedar Heights Dr
- Fletcher Ave and Black Hawk Rd (WB)
- Main St and W Seerley Blvd
- Ridgeway Ave and Bethel St
- Crossroads Mall Front
- Hy-Vee Gas and McDonalds
- Ridgeway Ave and Marnie Ave
- Rownd St and Rainbow Dr
- Maynard Ave and Auburn St
- S Main St and Orchard Dr
- W 4th St and W Ridgeway Ave(WB)
- Athens Dr and Tital Tr
- Williston Ave and W 9th St
- Prairie Pkwy and Brandilynn Blvd
- Crossroads Front Mall Entrance
- MercyOne Medical Center
- Main St and 6th St
- Broadway St and Dawson St
- Hammond Ave and Flammang Dr
- W 9th St and Park Ln
- Bishop Ave and Independence Ave
- E 4th St and Esther St
- W 5th St and Grant Ave
- E 4th St and E Dale St
- Bankers Blvd - Fisher Dr
- Progress Ave and Midway Dr
- E 6th St and Sycamore St
- Williston St and Baltimore St (WB)
- Pheasant Ln and Olympic Dr
- Dysart Rd and Orange Rd
- Thunder Ridge Mall
- W 1st St and Jefferson St
- Ansborough Hy Vee
- Highland School
- College St and W 12th St
- Greenhill Rd and Maynard Ave
- Hawkeye Community College - Back
- Chancellor Dr and W Ridgeway Ave
- Greenhill Rd and Rainbow Dr
- Hudson Rd and W 18th St
- Fletcher Ave and US 218 Ramp(NB)
- Fletcher Ave and W 4th St
- McClain Dr and University Ave(EB)
- Texas St and Cedar Terrace Dr
- Kimball Ave & W 3rd St
- Falls Ave and University Ave(EB)
- Seerley Blvd and Iowa St
- Wisconsin St and E Ridgeway Ave
- South St and W 3rd St
- W 11th St and South St
- W 3rd St and Fletcher Ave
- Hudson Rd and Viking Rd
- Walmart at Crossroads Mall
- Division St and Mercy One
- 9th St and Mitchell Ave
- Lafayette St and Vinton St (NB)
- Mobile St and Oneida St
- Mobile St and Sumner St
- Cedar Bend St and W Donald St
- US 63 and Esther St
- Longfellow Ave and Walker St
- 11th St and Easton Ave
- Hudson Rd and W 12th St
- Parker St and Avon Ave
- Ridgeway Ave and Plaza Cir
- W 9th St and Easton Ave
- UNI Multimodal Transportation Center
- Kimball Ridge Center
- US 63 and Parker St
- Adrian St and Lafayette St
- College St and University Ave
- Pinecrest
- Burton Ave and Conger St
- N Barclay St and Lester St
- Highland Dr and Crescent Dr
- Cedar Valley Arboretum
- Cedar Valley SportsPlex
- Prairie Pkwy and Wild Rye Way
- Wal-Mart
- Washington St and W 4th St
- W 5th St and Locust St
- Lost Island Theme Park
- Rainbow Dr and Rownd St
- Idaho St and Willow St
- W 6th St and Commercial St
- La Porte Rd and E Ridgeway Ave
- Donald St and Burton Ave
- Broadway St and Park Road
- Nordic Dr and Performance Dr
- Cedar Bend St and W Donald St
- Parker St and Avon Ave
- E 5th St and Walnut St
- 11th St and Easton Ave
- Bayard St and W 4th St (EB)
- Kimball Ave and Williston Ave
- Ansborough Ave and University Ave(WB)
- Main St and University Ave
- Hammond Ave & Wildwood Rd
- Bethel St and Ridgeway Ave
- Allen Hospital, Outpatient Entrance
- S Main St and Jennings Dr
- Ansborough Ave and Olympic Dr
- Kimball Ave and Mitchell Ave
- Water Park and Casino
- Southbrooke Dr and Frontage Rd of San Marnan Dr
- Hudson Rd and University Ave(NB)
- McDonalds and Hy-Vee Gas
- Walnut St and W 18th St
- Franklin St and Vinton St
- Hudson Rd and Greenhill Rd
- Fletcher Ave and US 218 Ramp
- Midway Dr and University Ave(EB)
- Broadway Ave and Conger St
- W 3rd St and Locust St
- Ansborough Ave and Meadow Ln
- College St and W 18th St
- W 11th St and Jefferson St
- Hackett Rd and Rainbow Dr
- Ridgeway Ave and Hammond Ave
- Cedarloo Shopping Area(WB)
- HyVee at College Square Mall
- UNI Multimodal Transporation Center
- Main St and W 18th St
- Rainbow Dr and Hacket Rd
- Walnut St and W 1st St
- Peoples Community Health Clinic
- Main St and Seerley Blvd
- Central Transfer
- Idaho St and Newell St
- Social Security Office
- Mullan Ave and Locust St
- W 4th St and Jefferson St
- US 63 and Almond St
- Mt Village Apartments
- Hudson Rd and W 4th St
- Idaho St and Newell St
- College St and W 25th St(NB)
- Colby Rd & Rachael St
- Sheerer Ave and University Ave(WB)
- Vinton St and Independence Ave
- Beverly Hills St and Maynard Ave
- Ansborough Ave and Falls Ave
- W 11th St and E Mitchell Ave
- E 11th St and Lafayette St
- Dysart Rd and Mills Ln
- Central Transfer
- Ridgeway Ave and Wisconsin St
- Jefferson St and Park Ave
- Newell St and E. 4th St
- Hudson Rd and Erik Rd
- Lafayette St and Vinton St
- Kimball Ave and Park Ln
- Ansborough Ave and Maynard Ave
- W 4th St & Bayard St
- Goodwill Industries
- Main St and Waterloo Rd
- Bishop Ave and Osage Ave
- W. 11th St and Willison Ave
- Fletcher Ave and Falls Ave
- Bayard St and W 4th St (WB)
- W 18th St and Commercial St
- Walnut St and W 6th St
- 18th St and Main St
- 6th St and Franklin St
- Ridgeway Ave and W 11th St
- Walnut Court
- University Ave and Holiday Rd
- 6th St and Walnut St
- W 3rd St and Fletcher Ave
- W 6th St and Jefferson St
- Mobile St and Newell St
- Lafayette St and Vinton St (SB)
- Walnut St and W 4th St
- Fletcher Ave and University Ave(EB)
- Crossroads Mall Front
- Kimball Ave and Mitchell Ave
- College St and 21st St
- Greenhill Medical Group
- Main St and 18th St
- W 2nd St and Jefferson St
- University Ave and Melrose Dr
- W 4th St and Kimball Ave (EB)
- Peoples Health Clinic
- Nordic Dr and Viking Rd
- Main St and 13th St
- S Division St and W 8th St
- Central Transfer
- Barnett Dr and W 4th St
- Allen Hospital - Dr Offices
- Wal Mart Dr and Brandilynn Blvd
- Home Depot
- Ansborough Ave and Downing Ave
- W 4th St and W 5th St
- and 30 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 | 81.5 | first check |
| 2026-07-30 | 81.5 | no change |
| 2026-07-31 | 81.5 | no change |
| 2026-08-01 | 81.5 | 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-31.
Same feed file as 2026-07-31; 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
9 findings, ordered by severity.
Show every finding
- Warning396 instances
396 of 396 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)
- Warning280 instances
280 of 280 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)
- Warning136 instances
136 of 396 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)
- Warning3 instances
Some route colors don't contrast with their text color.
Route badges get hard to read, most of all for riders with low vision.
Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)
Finding code: route_color_contrast · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning2 instances
Some stops exist in the feed but no trip ever stops at them.
Riders may walk to a stop where no bus 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)
- Warning1 instance
This feed describes flexible (demand-responsive) service but has no booking_rules.txt.
Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.
Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)
Finding code: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info34 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)
- Info8 instances
The feed includes a file that is not part of the GTFS spec.
Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.
Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)
Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info2 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · 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.
Flex zones are published but no booking_rules.txt is present.
Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).
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 153 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 396 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 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 153 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.
Can riders use it?
Checks beyond structural validation: places where the feed is valid but a rider still could not travel.
- 2 of 280 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 153 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 90 / 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 55 / 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/metropolitan-transit-authority-of-black-hawk-county-2414/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.