Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires · Correct or claim this listing
Feed status · checked 2026-07-10
Intercity Transit
Based on the feed this agency publishes
First scorecard for this agency
Ahead of 79% of all tracked agencies and 92% of large agencies.
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.1, validator 8.0.1.
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
1116 of 1116 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
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
Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Stop too far from shape using user distance (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +6 points
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. 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. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
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.
Score by category
The MobilityData validator flagged 3 kinds of issue across 17 instances (0 error, 17 warning, 0 informational).
Service data covers the next 50 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 not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
Sampled 9 times: 3 of 3 feeds healthy; 100.0% of scheduled trips had live predictions; 89.7% of vehicles on their route; predictions ran a median of 0s behind schedule.
Over time
This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.
Everything we checked
- Warning1116 instances
1116 of 1116 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.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning12 instances
12 of 117 sampled vehicle positions were far from their assigned route (worst: 3436 m).
A bus shown off its route usually means a wrong trip assignment; riders watch their bus drive the wrong streets.
Fix: Ask your AVL vendor to check vehicle-to-trip assignments for the flagged trips. (A vendor support ticket with the trip ids attached.)
Validator rule: scorecard_rt_vehicles_off_route
- Warning8 instances
Stop too far from shape using user distance (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: stop_too_far_from_shape_using_user_distance · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning8 instances
The feed contains route shapes no trip uses.
Harmless to riders, but it bloats the feed and suggests stale export data.
Fix: Enable 'remove unused shapes' (or similar) in your export tool. (One setting.)
Validator rule: unused_shape · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Missing feed contact email and url (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: missing_feed_contact_email_and_url · 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.)
Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info1 instance
feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).
App makers and state data programs 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.)
Validator rule: scorecard_no_feed_contact · 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.
5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (9X, 34, 35, 77, 78).
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.
962 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Capitol Way at 4th Ave [sb]", "Capitol Blvd at Carlyon Ave [sb]", "Crosby Blvd at Somerset Hill Dr [sb]", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
NTD GTFS readiness Ready
Published at a public URL, valid, and current: the three things the NTD GTFS requirement asks of a feed all hold here. Only your own D-10 certification makes 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 50 days.
- agency_id matches your NTD ID Not checked yet
- Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
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). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and 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 100% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 50 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 100% 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.
Realtime reliability
The realtime feed responded on 100.0% of 1 checks, with 0s median lag.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Live predictions vs schedule
Arrival predictions ran right on the schedule, and stayed within 91s nine times in ten. They were on time (about a minute early to five late) 96.7% of the time. 89.7% of reported vehicle positions sat on or near the published route shape.
From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.
Clears the Google and Apple Maps four-week coverage bar. This feed has 50 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
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.
- Correctness 84 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 83 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 52 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: stop names and headsigns.
- Realtime quality 98 / 100
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
Show your grade
Put a live badge on your agency site or feed README. It updates daily 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/intercity-transit-266/2026-07-10.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-10. Use it in a board packet, an NTD narrative, 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.