Access Allegany

What changed since the last check

• Correctness no change
• Freshness no change
• Rider experience no change

Top three things to fix

1. Correct feed_end_date in feed_info.txt. Set it to 2027-01-01, the last day in your calendar, or to the last day your schedule is reliable.

   feed_info.txt says this feed ends on 2025-12-31. Your service calendar runs to 2027-01-01. 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.

2. Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

   Trip distance exceeds shape distance (flagged by the MobilityData validator). See the linked rule for what this affects.

   This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

   Effort: Varies.

3. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.

   91 of 91 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 91 stops in the feed.

   Effort: A column in stops.txt; your scheduling software likely has it.

Ready to send to the agency

Hi Access Allegany team, feed_info.txt says this feed ends on 2025-12-31. Your service calendar runs to 2027-01-01. 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 2027-01-01, 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/access-allegany/

Copy this note from the full scorecard.

NTD GTFS readiness: Not ready

Resolve this before you certify on the D-10. 1 validator error to resolve. Service data expired 280 days ago, so FTA would find the link out of date.

Published Ready

Published at a public URL.

Valid Needs attention

1 validator error to resolve.

Current Not ready

Service data expired 280 days ago, so FTA would find the link out of date.

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 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.

Key facts

Feed URL

https://s3.amazonaws.com/datatools-511ny/public/Access_Allegany.zip

Last checked

2026-10-07

Service window

Feed has expired. Last service date 2027-01-01.

Location

New York