Feed status · checked 2026-08-01
Allen County Regional Transit Authority
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Ohio.
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 9 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
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
206 of 206 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 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 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
179 of 338 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 +13 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
- 206 of 206 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
- The feed contains no fare information.
- Next action
- 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.
- 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
- 179 of 338 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
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_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 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.
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. 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 122 days.
- Published accessibility data
- Accessibility information is stated for 47% 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 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 3 kinds of issue across 23 instances (0 error, 23 warning, 0 informational).
Service data covers the next 122 days.
47% of stops state wheelchair accessibility (47% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.
47% of stops state accessibility (47% marked accessible). Reflects what the feed states, not verified physical usability.
2 accessibility depth signals
2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (2, 5).
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.
77 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Elida Rd. and Robb Ave.", "Elida Rd & Diller Rd.", "Elida Rd and Pioneer", 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 338 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.
- 10 (pink)
- 9 (blue)
- 8 (yellow)
- 7 (teal)
- 6 (brown)
- 5 (orange)
- 4 (purple)
- 3 (white)
- 2 (red)
- 1 (green)
| Route | Type | Line color |
|---|---|---|
| 10 Delphos | Bus | pink |
| 9 Bluffton | Bus | blue |
| 8 South Metcalf/Shawnee | Bus | yellow |
| 7 North East | Bus | teal |
| 6 West North | Bus | brown |
| 5 South Main | Bus | orange |
| 4 North Main | Bus | purple |
| 3 Lima Mall | Bus | white |
| 2 Eastgate | Bus | red |
| 1 West Market | Bus | green |
List every stop
- Lima Mall route Elida Elementary School
- Lima Mall route Elida Middle School
- Zurmehly & Shawnee Rd.
- Central Point Parkway
- Alpa
- Ace Hardware
- Apollo
- Husky Refinery
- Orthopedic Institute
- Precision Thermoplastic
- Hanthorn & St. John's Rd.
- Beer Barrel Pizza (Dixie Highway)
- Liberty School
- Kibby & Main St.
- WOCAP
- Marimor Industries
- Lima Pallet
- Nickles Bakery
- Schoonover Park
- Federal Building
- St. Rita's
- Jameson & Allentown
- Rosedale & Allentown Rd.
- West Middle School
- Beer Barrel Pizza (Market Street)
- WalMart, Allentown
- Lochhaven Apartments
- Lima Sporting Goods Store
- Metcalf & North St.
- Our Daily Bread
- South Middle School
- 2nd & Johns Ave.
- Lima Apartments
- 8th & Reese Ave.
- 7th & Main St.
- 3rd & Main St.
- Lima Towers
- YMCA @ S. Main St.
- Main & Grand Ave.
- St. Gerard School
- Citi Trend (Northland Plaza)
- Circle K
- Temple Christian Elementary
- Willow Lake Apartments.
- Lima West Apartments
- Eagles
- Metcalf and Robb
- Greenway Apartments
- McKibben & West St.
- Fairfield Inn
- Biolife
- Meijer
- Lima Mall - East Side
- Edgewood Skating Rink
- Richelieu Apartments
- Mr. Appliance
- Furl Williams Shelter
- Metcalf & Robb Ave.
- McKibben and Elizabeth
- Wayne and Main
- Meat City
- Nelsons Packaging
- Leonard & 309 Hwy.
- Immanuel Baptist Church
- OSU Campus
- Colony Mobile Home
- Walmart East
- Eastgate Plaza
- Sam's Club
- Bob Evans Restaurant
- Kewpee East
- Lima Memorial Hospital
- Happy Days
- CVS Pharmacy
- Lima Senior High School
- YMCA
- McDonel and Elm
- Metcalf and Elm
- Elm and Collett
- Elm and Jameson
- Elm & Cole St.
- Lakewood and Woodlawn
- Glennwood and Spencerville
- Fat Jacks
- Chiefs Grocery Store
- LCC
- Cable & Market St.
- Woodlawn & Market St.
- Cole & Market St.
- St. Rita's
- Lima Terminal (Union Street)
- Lima Terminal (High Street)
- Maplewood Apartments
- Court House
- Lima Memorial Health Park
- JSMC
- Bob Evans
- Elida Rd & Diller Rd.
- Deer Creek Apartments
- S. Main & 2nd St.
- Main & 5th St.
- Lakeview Farms
- East Towne Plaza
- Western Sizzlin
- Auto Kiniton
- McDonald's - Bluffton
- Diamond Manufacturing
- Lima Mall route Elida High School
- Sherwood & Cable Rd.
- Mark Pi's
- McDonald's
- Goodwill
- Buffalo Wild Wings
- Jarvis & Eastown Rd.
- Lowe's
- Koop & Eastown Rd.
- Taco Bell
- Superior Bank
- Cole & Allentown Rd.
- Metcalf & North St.
- Main & North St.
- Elizabeth & North St.
- North & Allentown
- Verizon Wireless
- West Elm Plaza
- 4th & Reese Ave.
- Milburn & 2nd St.
- Eureka & Pine St.
- Daley's Grocery
- Black Lace Shelter
- Murphy and Main
- Wally's
- Brower Commons Shelter
- Lane and North Main
- McKibben & Main St.
- Dominion Building
- Child Support Shelter
- Market and McDonel
- Glenwood & Market St.
- Riley & Market St.
- Cable & Elm St.
- Woodlawn and Elm
- Main & Spring St.
- Metcalf and Market
- IHEART media
- Market and Jameson
- Lakewood and Cable
- Betty Lou Apartments
- Robb and Main
- North Middle School
- McDonald's
- West and Northern
- Northern and Union
- O'Conner and Main
- Haller and Main
- Main and Murphy
- Rainbow Muffler
- Shawnee St. and Bellefontaine
- Jimmy Johns
- Workers Comp.
- Rumpke
- 4th and St. Johns
- Dollar General
- Family Dollar
- St. John and Hanthorn
- Winfield United
- Hanthorn and Greely Chapel
- Greely Chapel and 4th Street
- Red Lobster
- Walgreen's
- Allen County Fairgrounds
- Eastwood Estates
- Lost Creek Care Center
- Luther Pines
- Hampton Greene Apartments
- La Charreada
- Beer Barrel
- Mt. Holyoke and 309
- Collins Ave and Bellefontaine
- Dewey and Bellefontaine
- Shawnee St. and Bellefontaine
- East Wind
- Lima City Schools
- P&G Reservoir Rd. Gate 1
- Reservoir and Ridge Crest Circle
- Reservoir and Roush
- Leonard and Elm
- Leonard and Federal
- Leonard and Bellefontaine
- Save A lot
- Kibby and Dana
- Kibby and Calumet
- Harrison and Eureka
- Harrison and Elm
- Elm and Pine
- Willard and 309
- Mckibben and West
- McKibben and Metcalf
- Metcalf and Grand
- Tremont and Metcalf
- Metcalf and O'Connor
- Kimberly and Edgewood
- Juneau Dr & Edgewood
- Great Clips
- Golden Corral
- Kohl's
- Five Below
- Spectrum
- Menards
- Across from Tracy Appliances
- Elida and East
- T-mobile
- Tractor Supply
- Milano's
- R & R liquidation
- Robb Ave Trailer Park
- Save a Lot
- Northwold and Robb Ave
- Smart Start
- Metcalf and O'Connor
- Independence Schools
- Grand and Metcalf
- Metcalf and Hazel
- McKibben and Metcalf
- McKibben and Elizabeth
- Dollar General
- Unity School
- Jefferson Apartments
- 400 block of Pine St.
- Main & North St.
- St. Rita's
- Jackson and Wayne
- Jackson and Mckibben St
- Jackson and Jefferson
- Sugar and 81 Rd
- 81 and Prosperity
- Waffle House
- PPG
- Resource
- Ford Engine Plant Gate 4
- Robb and Sugar
- Fuel Stop
- Richards Building Supply
- Lauer Historical Park
- Roush and Reservoir
- Kingswood Dr and Reservoir
- Fetter and Reservoir
- P&G Cool Rd.
- P&G Reservoir Road Gate 4
- Eureka and Central
- and 88 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 | 79.4 | first check |
| 2026-07-30 | 79.4 | no change |
| 2026-07-31 | 79.4 | no change |
| 2026-08-01 | 79.4 | 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
6 findings, ordered by severity.
Show every finding
- Warning206 instances
206 of 206 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)
- Warning179 instances
179 of 338 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)
- Warning11 instances
Some scheduled trips move faster between stops than a bus can.
Usually a typo'd stop time; riders get arrival times no bus can meet.
Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)
Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning11 instances
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
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
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)
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 122 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 206 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 47% 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 122 days.
- Accessible Not yet
- States wheelchair access on 47% 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 122 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 84 / 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 57 / 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/allen-county-regional-transit-authority/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.