Call-prep brief · checked 2026-10-07
Athens Public Transit
Grade F · 43.3 / 100
Unchanged since 2026-10-06.
For this call: lead with the grade and the three fixes below, then confirm the feed is current and the NTD details line up. Each fix is framed as a next step, not a failure.
What changed since the last check
- Correctness no change
- Freshness no change
- Rider experience no change
Top three things to fix
Correct feed_end_date in feed_info.txt. Set it to 2024-12-31, the last day in your calendar, or to the last day your schedule is reliable.
feed_info.txt says this feed ends on 2023-12-31. Your service calendar runs to 2024-12-31. The GTFS standard tells apps to trust a feed only up to its end date. So apps may stop showing your service on the earlier date, even though the calendar goes on.
This one is about the feed as a whole, so there is no share of it to count.
Effort: One field in feed_info.txt, often an export setting.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
148 of 148 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.
Fixing this covers all 148 stops in the feed.
Effort: A column in stops.txt; your scheduling software likely has it.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
488 of 488 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
Fixing this covers all 488 trips in the feed.
Effort: A default or per-trip field in your export.
Riders and need behind these fixes
- This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
- Ohio as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-10-05.
These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.
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
- feed_info.txt says this feed ends on 2023-12-31. Your service calendar runs to 2024-12-31.
- Next action
- Correct feed_end_date in feed_info.txt. Set it to 2024-12-31, the last day in your calendar, or to the last day your schedule is reliable.
- 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
- 148 of 148 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
- 488 of 488 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
Ready to send to the agency
Hi Athens Public Transit team, feed_info.txt says this feed ends on 2023-12-31. Your service calendar runs to 2024-12-31. The GTFS standard tells apps to trust a feed only up to its end date. So apps may stop showing your service on the earlier date, even though the calendar goes on. The fix is usually one export setting: Correct feed_end_date in feed_info.txt. Set it to 2024-12-31, the last day in your calendar, or to the last day your schedule is reliable. This came from your GTFS data quality scorecard, which checks the feed you publish and lists the fixes in plain language: https://gtfsscorecard.org/agency/athens-public-transit-1973/
NTD GTFS readiness: Not ready
Resolve this before you certify on the D-10. Service data expired 1011 days ago, so FTA would find the link out of date. agency.txt has no nonblank agency_id. Every RY2026 NTD GTFS submission needs a stable value unique among the reporters represented in the feed, crosswalked to each reporter's NTD ID on the P-50 form.
- Published Ready
- Published at a public URL.
- Valid Ready
- Passes validation with no errors.
- Current Not ready
- Service data expired 1011 days ago, so FTA would find the link out of date.
- agency_id provided Not ready
- agency.txt has no nonblank agency_id. Every RY2026 NTD GTFS submission needs a stable value unique among the reporters represented in the feed, crosswalked to each reporter's NTD ID on the P-50 form.
Key facts
- Feed URL
- https://hosted-gtfs-feeds.s3.amazonaws.com/HAPCAP/gtfs.zip
- Last checked
- 2026-10-07
- Service window
- Feed has expired. Last service date 2024-12-31.
- Feed version
- 1.0 - Jan 9, 2023
- Location
- Ohio
Part of the Ohio portfolio: see where this agency sits among the other feeds in that group before the call.
A data-quality and completeness read to support an agency conversation. Not an official compliance determination. Rubric v1.4, validator 8.0.1.