GTFS Scorecard
← All agencies

Feed status · checked 2026-08-01

Access Allegany

Based on the feed this agency publishes

Service mode Bus

42.0 / 100

unchanged since 2026-07-31

Catalogued in New York.

Feed expiredAccessibility gapsRealtime not yet published

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 84 minutes 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

Fix 01

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 213 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 in its category

Fix 02

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.

⏱ Varies.worth about +12 points in its category

Fix 03

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

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.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category

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
Service data ended 213 day(s) ago.
Next action
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
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.

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

    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.

  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.

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    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.

  3. 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. Make this change in whatever tool produces your feed, then re-export.

    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 was 213 days ago.
Published accessibility data
Accessibility information is stated for 0% of stops and 94% 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 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

Correctness59.5 / 100

The MobilityData validator flagged 11 kinds of issue across 763 instances (5 error, 750 warning, 8 informational).

Freshness0.0 / 100

Service data ended 213 day(s) ago. Trip planners have likely already dropped this feed.

Rider experience51.1 / 100

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

Accessibility35.3 / 100

0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

2 accessibility depth signals

  • 3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (SA1, SA6, SA4).

    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.

  • 19 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Tops/YMCA", "W. University/Main St. (Alfred)", "CR-15 & Old State Rd (Angelica)", 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.

Realtime qualityNot yet measured

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

Skip to route and stop data

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.

  • SA3 (red)
  • SA4 (gray)
  • SA5 (teal)
  • SA6 (teal)
  • SA1 (orange)
  • SA2 (purple)
Routes in Access Allegany's feed
RouteTypeLine color
SA3 Angelica - Belmont - Friendship - CubaBusred
SA4 Angelica-Belmont-Belfast-Houghton-Fillmore-Short TractBusgray
SA5 Alfred - Andover - Whitesville - WellsvilleBusteal
SA6 Cuba - Hinsdale - OleanBusteal
SA1 Angelica - Belmont - Scio - WellsvilleBusorange
SA2 Bolivar-Richburg-Ceres-Olean-WellsvilleBuspurple
List every stop
  • Houghton Mini-Mart
  • River Dog Fly Shop (Houghton)
  • ACCESS Center (Belmont)
  • VA Healthcare Clinic (Wlsv)
  • Belmont Hotel (Belmont)
  • Corner Friendship St & Main (Bolivar)
  • Houghton College (Houghton)
  • Fire Department (Short Tract)
  • Literacy West (Belmont)
  • Dresser Rand (Olean)
  • Erin Isle Apartments (Cuba)
  • W. University/Main St. (Alfred)
  • Best Inn (Wlsv)
  • Northwest Corner (Rent-A-Center) (Wlsv)
  • Scio Library (Scio)
  • Walmart (Olean)
  • Dollar General/Shop 'n Save (Fillmore)
  • Giant Foodmart (Cuba)
  • Fire Department (Oramel)
  • ACT Terminal (Cuba)
  • ACT Terminal (Cuba)
  • BOCES (Belmont)
  • Tops/YMCA
  • Olean General Hospital (Olean)
  • Carpenter Commons/Wellsville Woods
  • Maple Apartments (Alfred)
  • Trapping Brook House (Wlsv)
  • Gallman Hardware (Cuba)
  • E State/Main St (Wlsv)
  • ASC Admin Building (Alfred)
  • Budget Inn (Wlsv)
  • Brookhaven Apts – Gazebo/Park (Wlsv)
  • UR medical (Andover)
  • American Legion (Belmont)
  • The Store (Scio)
  • Shop n' Save (Bolivar)
  • Olean Center Mall (Olean)
  • Houghton Academy (Houghton)
  • Grange (Angelica)
  • Office for the Aging (Belmont)
  • Alfred Tech/Hillside Homes (Wlsv)
  • Trout Run
  • Cuba Memorial Hospital (Cuba)
  • Olean BOCES (Olean)
  • Main/Sunnyside (Friendship)
  • Main/Baxter (Friendship)
  • Cornell Cooperative Ext. (Belmont)
  • Clarity Wellness
  • Episcopal Church (Wlsv)
  • YMCA (Olean)
  • Town Hall / School (Richburg)
  • Miller & Brandes (Friendship)
  • Friendship Car Wash
  • Crosby's (Belmont)
  • Dollar General / Tinkertown Hardware (Alfred Station)
  • Alstom 417 (Wlsv)
  • Allegany County Sheriff's Office
  • Post Office (Black Creek)
  • Belfast Manor
  • Library (L. Genesee)
  • East End Market (Angelica)
  • Archbishop Walsh High School (Olean)
  • N Brooklyn Ave & W Madison Street
  • Portville Plaza
  • Colony Park Apartments
  • Town Hall (Little Genesee)
  • CR-15 & Dorvit Rd. (Short Tract)
  • Dollar General / Dunkin (Wlsv)
  • Crosby's (Hinsdale)
  • Tinkertown Hardware
  • Short's Deli (Wlsv)
  • Town Hall (Caneadea)
  • CR-15 & Old State Rd (Angelica)
  • CR-15 & CR-16 (Angelica)
  • Post Office (Allentown)
  • Cuba Cultural Center (Cuba)
  • Fire Department (Portville)
  • County Court House (Belmont)
  • Otis Eastern (Wlsv)
  • Houghton College Facilities
  • Cuba Library
  • Marathon (Wlsvle)
  • Whitesville Grocery (Whitesville)
  • Caneadea Mini Mart
  • American Legion (Belfast Main Street)
  • Town Park (Belfast Main Street - NB)
  • Highland Pointe (Wlsv)
  • Stillwater Pizza
  • ACASA
  • Dave's Diner (Ceres)
  • N Brooklyn Avenue & Stevens

Over time

Overall score across the last 4 checks — unchanged since 2026-07-31.

2026-07-25: 42.02026-07-30: 42.02026-07-31: 42.02026-08-01: 42.0
Show the numbers
CheckScoreChange
2026-07-2542.0 first check
2026-07-3042.0 no change
2026-07-3142.0 no change
2026-08-0142.0 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

17 findings, ordered by severity.

Show every finding
  • Error5 instances

    Trip distance exceeds shape distance (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: 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. (Varies.)

    Finding code: trip_distance_exceeds_shape_distance · See MobilityData GTFS Validator rules

  • Error1 instance

    Service data ended 213 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.)

    Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices

  • Warning735 instances

    Missing timepoint value (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'missing_timepoint_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: missing_timepoint_value · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning91 instances

    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.

    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

  • Warning12 instances

    On some trips the stop distances run a little past the end of the route line.

    The stop and shape distance values don't quite line up, so any math that uses them can drift.

    Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)

    Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning5 instances

    5 of 84 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

  • Warning2 instances

    2 of 84 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

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

    Finding code: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    feed_info.txt lists no contact email and no contact URL.

    Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.

    Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)

    Finding code: missing_feed_contact_email_and_url · Read the fix guide · See MobilityData GTFS Validator rules

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

    Finding code: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules

  • 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

  • Info3 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

  • Info2 instances

    Trip with shape dist traveled but no shape distances (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'trip_with_shape_dist_traveled_but_no_shape_distances' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: trip_with_shape_dist_traveled_but_no_shape_distances · See MobilityData GTFS Validator rules

  • Info1 instance

    Feed valid beyond total service window (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'feed_valid_beyond_total_service_window' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: feed_valid_beyond_total_service_window · See MobilityData GTFS Validator rules

  • Info1 instance

    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

  • Info1 instance

    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

  • Info1 instance

    feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

    Trip-planning apps and regional data coordinators 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.)

    Finding code: scorecard_no_feed_contact · Read the fix guide · See MobilityData GTFS Validator rules

NTD GTFS readiness Not ready

Resolve this before you certify on the D-10. 1 validator error to resolve. Service data expired 213 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 213 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 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 84 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. 1 validator error to resolve. Service data expired 213 days ago. States wheelchair access on 0% of stops and 94% of trips; the mark needs 90% of each.

Valid Not yet
1 validator error to resolve.
Current Not yet
Service data expired 213 days ago.
Accessible Not yet
States wheelchair access on 0% of stops and 94% 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 153 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 5 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.

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 60 / 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 0 / 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 51 / 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.

Access Allegany GTFS data quality grade: F

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/access-allegany/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.