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
Feed status · checked 2026-07-09
Link Transit
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 71% of all tracked agencies and 69% of mid-size agencies. Operates in North Carolina.
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.
Checked for changes 4 hours ago; last changed 4 hours 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_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.Likely your team
200 of 200 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
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).Likely your export tool
163 of 163 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ Often one default setting in your export.worth about +15 points
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
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
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.
Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default). · 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.
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 4 kinds of issue across 173 instances (0 error, 170 warning, 3 informational).
Service data covers the next 387 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.
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.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 1 Red (red)
- 2 Orange (orange)
- 3 Blue (blue)
- 4 Green (green)
- 5 Purple (blue)
| Route | Type | Line color |
|---|---|---|
| 1 Red | Bus | red |
| 2 Orange | Bus | orange |
| 3 Blue | Bus | blue |
| 4 Green | Bus | green |
| 5 Purple | Bus | blue |
This feed has 200 stops.
List every stop
- Mebane Cone Health Park and Ride Lot
- N. Ireland St @ Fisher Ave (outbound)
- Graham Hopedale Rd @ Martin St (outbound)
- Graham Hopedale Rd @ N. Church St (outbound)
- Sellers Mills Road @ N. Church St (nearside)
- N. Church St @ Fairview St (outbound)
- N. Church Street @ Main Street (outbound)
- W. Main Street @ Across Church Circle (outbound)
- W. Main Street @ Haw River Flooring (outbound)
- E. Main Street @ Stone Street (Haw River Town Hall) (outbound)
- W. Main Street @ Across Roma Road (outbound)
- Roxboro Road @ Across Bakersfield Road (US Post Office) (outbound)
- Roxboro Road @ Pine Street (outbound)
- Roxboro Road @ Across Sunset Drive (outbound)
- Roxboro Road @ Food Lion (outbound)
- Yanceyville Road @ Green Level Church Road (outbound)
- Yanceyville Road @ Dollar General
- W. Lebanon Avenue @ N. Holt Avenue
- W. Lebanon Avenue @ Church Street
- Ball Park Drive @ Short Street
- Ball Park Drive @ N. Williamson Ave
- Church Street @ O'Neal Street (inbound)
- Church Street @ O'Neal Street (outbound)
- Ball Park Drive @ Williamson Ave
- Ball Park Drive @ Lynn St
- Ball Park Drive @ Trollinger Apartments
- Ball Park Drive @ Elon Town Hall
- Burlington Avenue @ Huffine Street (outbound)
- Yanceyville Road @ Green Level Church Road (inbound)
- Roxboro Road @ Empire Tobacco and Vape (inbound)
- Roxboro Road @ Sunset Drive (inbound)
- Roxboro Road @ Circle Drive (inbound)
- Roxboro Road @ US Highway 70 (inbound)
- W. Main Street @ Roma Road (inbound)
- E. Main Street @ Across from Stone Street (inbound)
- W. Main Street @ The Lofts on Haw River (inbound)
- W. Main Street @ Church Circle (inbound)
- N. Church Street @ Main Street (inbound)
- N. Church St @ McKinney Street (inbound)
- Sellers Mills Road @ N. Church Street (farside)
- N. Graham Hopedale Road @ N. Church Street (inbound)
- N. Graham Hopedale Road @ Martin Street (inbound)
- Chandler Avenue @ Apple Street (inbound)
- Apple Street @ Across Baldwin Drive (inbound)
- Apple Street @ Ross Street (inbound)
- Apple Street @ Richmond Avenue (inbound)
- W. Main Street near Whitsett Avenue (Outbound)
- W. Main Street near Whitsett Avenue (Inbound)
- Worth Street Transfer Hub/Burlington Downtown
- E. Webb Street @ Tucker Street (outbound)
- Everett Street / Burlington Homes (outbound)
- Everett Street @ Fix Street (outbound)
- Fix @ Tucker St. (outbound)
- Tucker Street @ Center Court / Tucker St Apts (outbound)
- Chapel Hill Road / Glenwood Apts. (outbound)
- S. Mebane Street @ Trail 2 (outbound)
- S. Mebane Street @ Saintsbury Dr. / Food Lion (outbound)
- S. Mebane Street @ Delaney Drive (outbound)
- International Drive @ Holly Hill Mall (Blue Inbound/Red Inbound Transfer)
- Huffman Mill Road @ Forestdale Drive (outbound)
- Garden Road / Walmart
- Boone Station Drive/Waltham Dr / Alamance Crossing (outbound)
- Boone Station Drive / Tiki Lane (outbound)
- University Commons
- Alamance Regional Medical Center / Park & Ride Lot
- Boone Station Drive / Tiki Lane (inbound)
- Boone Station Drive / Alamance Crossing (inbound)
- Huffman Mill Road @ Forestdale Drive / Brittany Apts. (inbound)
- S. Mebane Street @ Delaney Drive (inbound)
- S. Mebane Street @ Saintsbury Dr. / Food Lion (inbound)
- S. Mebane Street @ Trail 2 (inbound)
- S. Mebane Street @ Colony Apts. (inbound)
- Chapel Hill Road / Glenwood Apts. (inbound)
- Tucker Street @ Center Court / Tucker St Apts (inbound)
- Tucker St @ Fix St. (inbound)
- Everett Street @ Fix Street (inbound)
- Everett Street / Burlington Homes (inbound)
- E. Webb Avenue @ Gilmer Street (inbound)
- Maple @ S. Broad Post Office (Outbound)
- Maple Avenue @ S. Flanner Street (outbound)
- Maple Avenue @ Stokes Street (inbound)
- Maple Avenue @ Floyd Street (outbound)
- ACC Dillingham Center @ Plaza Drive
- Hanford Road @ Anthony Road (On Request - call 336.222.5465, 1 hour before pick up)
- Hanford Road @ Maple Ave (On Request - call 336.222.5465, 1 hour before pick up)
- Harden Street @ Atwood Drive (outbound)
- Graham Park & Ride
- Alamance Community College / Jimmie Kerr Road
- Harden Street @ Atwood Drive (inbound)
- Maple Avenue @ Floyd Street / Family Dollar (inbound)
- Maple Avenue @ S. Flanner Street (inbound)
- Maple @ S. Broad Post Office (Inbound)
- S. Worth Street @ Maple Avenue / City Annex (outbound)
- S. Worth Street @ Maple Avenue / City Annex (inbound)
- S. Main Street @ East 6th Street (outbound)
- S. Main Street @ Summit Drive (outbound)
- Burlington City Park / YMCA / Kitchin St. (outbound)
- S. Church Street @ Tarleton Avenue (outbound)
- Church Street @ Huffman Mill/Harris Teeter
- International Drive @ across near Anne Elizabeth Drive (Blue Outbound/Red Outbound Transfer)
- Forestdale Drive @ Academy Sports (outbound)
- Forestdale Drive @ Commerce Place (outbound)
- Correct Time Plaza @ Church Street (outbound)
- Burlington Ave @ Apple St. (outbound)
- Burke Street @ Red Caboose / Downtown Gibsonville (outbound)
- NC 100 @ Minneola Street (outbound)
- Bethel Street @ Dollar General (outbound)
- Harper Senior Center / Azela Circle / Gibsonville
- Bethel Street @ Dollar General (inbound)
- NC 100 @ Minneola Street (inbound)
- Burke Street @ Red Caboose / Downtown Gibsonville (inbound)
- Burlington Ave @ Apple St. (Inbound)
- Huffine St (Inbound)
- Alamance Street @ Huffine Street (inbound)
- Correct Time Plaza @ Church Street (inbound)
- Forestdale Drive @ Commerce Place (inbound)
- Forestdale Drive @ Residence at Forestdale (Inbound)
- International Drive @ near Anne Elizabeth Drive
- Church Street @ Huffman Mill Road
- S. Church Street @ Tarleton Avenue (inbound)
- Burlington City Park / YMCA (inbound)
- S. Main Street @ Summit Drive (inbound)
- S. Main Street @ East 6th Street (inbound)
- N. Fisher Street @ Trade Street
- Front Street @ Tarpley Street (outbound)
- Front Street @ Tarpley Street (inbound)
- W. Front Street @ Trollinger St. (outbound)
- W. Davis St @ Garfield Road (outbound)
- W. Davis Street @ Food Lion (outbound)
- W.Webb Ave @ Lakeview Ave (outbound)
- Cadiz Street @ Glen Raven Mills (outbound)
- Durham Street @ James Drive (Outbound)
- Durham Street @ Cadiz Street (outbound)
- Elm Street @ Spence Street (outbound)
- Tillman Street @ Lakeside Apts. (outbound)
- Hatch Street @ Logan Street (outbound)
- Hatch Street @ Ray Street (outbound)
- Key Street @ Rahut Street (outbound)
- Sharpe Road @ Morgantown Rd (outbound)
- Sharpe Road @ Lundsford Drive (outbound)
- Rauhut Street @ Westmoreland
- Rauhut Street @ Sharpe Family Dollar (outbound)
- North Park Library
- Rauhut Street @ Sharpe Family Dollar (Inbound)
- Rauhut St @ Key St (Robinson Park) (inbound)
- Hatch Street @ Ray Street (inbound)
- Hatch Street @ Logan Street (inbound)
- Tillman Street @ Lakeside Apts. (inbound)
- Elm Street @ Chestnut Street (inbound)
- Durham Street @ Cadiz Street (inbound)
- Durham Street @ James Drive (Inbound)
- Cadiz Street @ Glen Raven Mills (inbound)
- W.Webb Ave @ Lakeview Ave (inbound)
- W. Davis Street @ Food Lion (inbound)
- W. Davis St @ Garfield Road (inbound)
- W. Front Street @ Trollinger St. (inbound)
- N. Main St. @ Amtrak Station (outbound)
- N. Ireland St. @ Sellars St./ BHA (outbound)
- N. Ireland St @ Fairfax Avenue (outbound)
- N. Mebane St @ Walmart (outbound)
- Sellers Mills Road @ N. Church St. Plaza/Food Lion (outbound)
- Graham Hopedale Rd @ McKinney St (DSS) (inbound)
- Morningside Drive Apartments (inbound)
- Homewood Avenue @ Vaughn Road (inbound)
- Beaumont Avenue @ Beaumont Court (inbound)
- Sharpe Road @ Melrose Drive
- Apple Street @ Ross Street (outbound)
- Apple Street @ Baldwin Road (outbound)
- Chandler Avenue @ Chandler Court (Crump Village) (outbound)
- Sharpe Road @ Melrose Drive
- Beaumont Avenue @ Beaumont Court (outbound)
- Homewood Avenue @ Vaughn Road (outbound)
- Morningside Drive Apartments (outbound)
- Graham Hopedale Rd @ McKinney St (DSS) (outbound)
- Sellers Mills @ Church St. Plaza/Food Lion (inbound)
- N. Mebane St @ Across from Walmart (inbound)
- N. Ireland St. @ Sellars St./ BHA (inbound)
- N. Main St. @ Amtrak Station (inbound)
- Apple Street @ midblock Excel Christian Academy (outbound)
- Maple Avenue @ Stokes Street (outbound)
- South Williamson Ave @ Eastgate Drive
- W. Haggard Ave @ N. Holt Ave
- W. Haggard Ave @ Manning Ave
- Manning Ave @ Blakely Hall Ln
- Manning Ave @ Blakely Hall Ln (inbound)
- W. Haggard Ave @ Manning Ave (inbound)
- W. Haggard Ave @ N. Holt Ave (inbound)
- South Williamson Ave @ Westgate (inbound)
- W. Elm Street @ S. Maple St / Alamance County Sheriff (inbound)
- W. Elm Street @ S. Maple St / Alamance County Sheriff (outbound)
- Cook Rd @ Elon Park Drive
- Manning Ave @ Popular (inbound)
- Manning Ave @ Popular (Outbound)
- W. Front Street @ Peele Street (inbound)
- W. Front Street @ Peele Street (outbound)
- Huffine Street @ Burlington Avenue (Inbound)
- S. Williamson Ave @ Church St. Food Lion (inbound)
- Church Street @ S. Williamson Avenue next to Walgreens
- Jimmie Kerr Road @ Bakatsias Ln
- S. Mebane St @ Trail 4 (Outbound)
Over time
Overall score across the last 20 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-19 | 75.6 | first check |
| 2026-06-20 | 75.6 | no change |
| 2026-06-21 | 75.6 | no change |
| 2026-06-22 | 75.6 | no change |
| 2026-06-23 | 75.6 | no change |
| 2026-06-24 | 75.6 | no change |
| 2026-06-25 | 75.6 | no change |
| 2026-06-26 | 75.6 | no change |
| 2026-06-27 | 75.6 | no change |
| 2026-06-28 | 75.6 | no change |
| 2026-06-29 | 75.6 | no change |
| 2026-06-30 | 75.6 | no change |
| 2026-07-01 | 75.6 | no change |
| 2026-07-02 | 75.6 | no change |
| 2026-07-04 | 75.6 | no change |
| 2026-07-05 | 75.6 | no change |
| 2026-07-06 | 75.6 | no change |
| 2026-07-07 | 75.6 | no change |
| 2026-07-08 | 75.6 | no change |
| 2026-07-09 | 75.6 | 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-08.
Same feed file as 2026-07-08; 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
- Warning200 instances
200 of 200 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)
- Warning164 instances
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.)
Validator rule: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning163 instances
163 of 163 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 (most small-agency fleets are 100% accessible, so this is often a single default). (Often one default setting in your export.)
Agencies here usually clear this within about 1 week (based on 5 observed fixes).
Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning5 instances
Route long name contains short name (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_long_name_contains_short_name' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
Same name and description for route (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'same_name_and_description_for_route' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: same_name_and_description_for_route · 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)
- Info3 instances
Unknown file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'unknown_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Agencies here usually clear this within about 1 week (based on 6 observed fixes).
Validator rule: unknown_file · 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.
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1 Red).
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.
193 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("N. Ireland St @ Fisher Ave (outbound)", "Graham Hopedale Rd @ Martin St (outbound)", "Graham Hopedale Rd @ N. Church St (outbound)", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
NTD certification 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 387 days.
- agency_id matches your NTD ID Not aligned
- Your feed's agency_id is 227; your National Transit Database ID is 40252. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id, so a difference here is a heads-up, not an error. Optionally set the agency_id for your service to 40252 in agency.txt (and the matching agency_id in routes.txt) so the feed lines up with your NTD record. It is a convenience, not a required feed change: FTA also links agency_id to your NTD ID on your P-50 form.
- shapes.txt covers your trips Ready
- All 163 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 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 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 387 days.
- Accessible Not yet
- States wheelchair access on 0% 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 387 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 100 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 45 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: 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 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/link-transit-1971/2026-07-09.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-09. 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.