← All agencies

Feed status · checked 2026-08-02

GoTriangle

Based on the feed this agency publishes

Service mode Bus

69.7 / 100

up 0.5 since 2026-08-01 · D → D

Covers 195 daysAccessibility 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 43 minutes ago; last changed 18 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

Fix 01

Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool

1959 of 1959 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Fix 02

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

220 of 496 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 +11 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
1959 of 1959 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
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. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · 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. See this feed's finding-clearance log.

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

    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. See this feed's finding-clearance log.

  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. See this feed's finding-clearance log.

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 is in 195 days.
Published accessibility data
Accessibility information is stated for 55.6% of stops and 0% 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.

Score by category

Correctness60.0 / 100

The MobilityData validator flagged 7 kinds of issue across 704 instances (0 error, 704 warning, 0 informational).

Freshness100.0 / 100

Service data covers the next 195 days.

Rider experience58.9 / 100

56% of stops state wheelchair accessibility (56% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is not published.

Accessibility34.8 / 100

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

2 accessibility depth signals

  • 4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (305, 705, ZWX, 400).

    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.

  • 462 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Blount St at GoRaleigh Station", "Martin St at Dawson St", "Harrington St at Martin St", 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 496 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.

  • 100 (red)
  • 300 (white)
  • 305 (teal)
  • 310 (yellow)
  • 400 (purple)
  • 405 (pink)
  • 700 (pink)
  • 705 (purple)
  • 800 (green)
  • 805 (green)
  • CRX (gray)
  • DRX (black)
  • ODX (orange)
  • RDU (teal)
  • WRX (yellow)
  • ZWX (brown)
  • 420 (yellow)
  • 311 (orange)
Routes in GoTriangle's feed
RouteTypeLine color
100 Route 100Busred
300 Route 300Buswhite
305 Route 305Busteal
310 Route 310Busyellow
400 Route 400Buspurple
405 Route 405Buspink
700 Route 700Buspink
705 Route 705Buspurple
800 Route 800Busgreen
805 Route 805Busgreen
CRX Route CRXBusgray
DRX Route DRXBusblack
ODX Route ODXBusorange
RDU RDU ShuttleBusteal
WRX Route WRXBusyellow
ZWX Route ZWXBusbrown
420 Route 420Busyellow
311 Route 311Busorange
List every stop
  • Avent Ferry Rd at Varsity Dr (Carolyn Apts)
  • Avent Ferry Rd at Brigadoon Dr (SB)
  • Trailwood Dr at Centennial Knoll Cir
  • Avent Ferry Rd at Brigadoon Dr
  • Avent Ferry Rd at Centennial View Ln
  • New Bern Ave at S Tarboro Rd
  • E Edenton St at N Tarboro Rd
  • E Edenton St at N Wilmington St
  • Westgate Dr at South Square (SB)
  • Woodcroft Pkwy at Autumn Woods Dr
  • Woodcroft Pkwy at Sandstone Ridge Dr (WB)
  • Woodcroft Pkwy at Winterberry Ridge Dr (EB)
  • Woodcroft Shopping Center (EB)
  • Woodcroft Shopping Center (WB)
  • Western Blvd at Jones Franklin Rd
  • Trailwood Dr at Lineberry Dr
  • Western Blvd at Hunt Dr (WB)
  • McFarland Dr at Witherspoon Blvd (EB)
  • Fayetteville Rd at Renaissance Pkwy (SB)
  • East Dr at Jackson Cir (NB)
  • Alston Ave at Linwood Ave (NB)
  • Revere Rd at Nash St
  • Trailwood Dr at Tryon Rd
  • New Bern Ave at WakeMed (across)
  • Dillard Dr at Meeting St (EB)
  • Avent Ferry Rd at Avery Close Apt
  • Erwin Rd at Emergency Dr (EB)
  • Fulton St at Elder St (SB)
  • Hillsborough St at Jones Franklin Rd (WB)
  • Efland-Cheeks Community Center
  • E Washington St at S 5th St (Mebane City Hall)
  • Mebane Cone Health Park-and-Ride
  • Salisbury St at Davie St (SB)
  • Salisbury St at South St (SB)
  • Woodcroft Pkwy at Parson's Chase (EB)
  • Woodcroft Pkwy at Homeplace II (WB)
  • N Salisbury St at W Edenton St
  • Durham Tech OCC Park-and-Ride (SB)
  • E Morgan St at S Wilmington St
  • Wilmington St at Jones St
  • Waterstone Dr at UNC Health Care - Hillsborough Ca
  • Jones Ferry Rd at Davie Rd (EB)
  • E Main St at Jade Palace (WB)
  • Jones Ferry Rd at Alabama Ave (WB)
  • E Main St at Weaver St Realty (EB)
  • Slater Rd at Carrington Mill Blvd (EB)
  • Slater Rd at Carrington Mill Blvd (WB)
  • Watkins Rd at Wake Tech RTP Campus (WB)
  • Watkins Rd at Perimeter Park Dr (WB)
  • Kit Creek Rd at Cisco Building 10 (EB)
  • Kit Creek Rd at Cisco (Building 6)
  • Davis Dr at Wally Gilbert Dr (Biogen)
  • Davis Dr at Hopson Rd (Verisk Health & Manpower)
  • Kit Creek Rd at Davis Dr (Cisco Bldg 5)
  • McCrimmon Pkwy at Airport Blvd (EB)
  • Evans Rd at Aviation Pkwy (WB)
  • Weston Pkwy at Evans Rd (SB)
  • Weston Pkwy at Shelton Dr (SB)
  • Chapel Hill Rd at Summit Ridge Loop (EB)
  • Chapel Hill Rd at Morrisville Pkwy (EB)
  • Chapel Hill Rd at Market Center Dr (EB)
  • Chapel Hill Rd at Maynard Rd (EB)
  • Chapel Hill Rd at Boundary St (EB)
  • Chapel Hill Rd at Boundary St (WB)
  • Chapel Hill Rd at Middleton Rd (WB)
  • Chapel Hill Rd at NW Cary Pkwy (WB)
  • Chapel Hill Rd at Ridgemere Dr (WB)
  • Chapel Hill Rd at Weston Pkwy (WB)
  • Weston Pkwy at Shelton Dr (NB)
  • Evans Rd at Weston Pkwy (NB)
  • McCrimmon Pkwy at Aviation Pkwy (WB)
  • McCrimmon Pkwy at Airport Blvd (WB)
  • Main St at Center St (NB)
  • North Main Athletic Complex Park-and-Ride (WB)
  • Apex Peakway at Hughes St (WB)
  • Tryon Rd at New Waverly Pl (WB)
  • Apex Peakway at Hughes St (EB)
  • North Main Athletic Complex Park-and-Ride (EB)
  • Main St at Center St (SB)
  • Watkins Rd at Wake Tech RTP Campus (EB)
  • Watkins Rd at Perimeter Park Dr (EB)
  • Renaissance Pkwy at Southpoint Mall (WB)
  • Fayetteville Rd at Laurel Springs Dr (NB)
  • NC 54 at Residence Inn Blvd (WB)
  • NC 54 at The Hamptons Apts (WB)
  • NC 54 at Seasons of Southpoint (EB)
  • Erwin Rd at Downing St (EB)
  • Erwin Rd at Lambeth Cir (WB)
  • NC 54 at Fayetteville Rd (EB)
  • NC 54 at Barbee Rd (EB)
  • Fayetteville Rd at Geneva Dr (NB)
  • NC 54 at Waterford Valley Dr (WB)
  • NC 54 at Revere Rd (WB)
  • Chapel Hill St at Gregson St (WB)
  • Fayetteville Rd at Laurel Springs Dr (SB)
  • Fayetteville Rd at Geneva Dr (SB)
  • NC 54 at NC 55 (EB)
  • Wilmington St at North St
  • Fayetteville Rd at Crooked Creek Pkwy (NB)
  • Duke St at Jackson St (NB)
  • University Dr at Martin Luther King Jr Pkwy (WB)
  • NC 54 at Pine Glen Trail (WB)
  • Erwin Rd at Fulton St (EB)
  • Erwin Rd at Downing St (WB)
  • Fayetteville Rd at Dunhill Dr (NB)
  • Witherspoon Blvd at McFarland Dr (SB)
  • Hope Valley Rd at Garrett Rd (NB)
  • NC 54 at S Alston Ave (EB)
  • Salisbury St at Morgan St (SB)
  • Edenton St at Harrington St (WB)
  • Blue Ridge Rd at Westchase Blvd (NB)
  • Blue Ridge Rd at Trinity Rd (NB)
  • Hillsborough St at Forest Rd (WB)
  • Hillsborough St at Friendly Dr (EB)
  • Hillsborough St at Forest Rd (EB)
  • Western Blvd at Ashe Ave (WB)
  • Hillsborough St at Shepherd St (WB)
  • Hillsborough St at Meredith College (WB)
  • Western Blvd at Deboy St (EB)
  • S Columbia St at Health Sciences Library (NB)
  • Trent Dr at Duke Hospital South (WB)
  • Erwin Rd at Morreene Rd (SB)
  • Westgate Dr at South Square (NB)
  • Erwin Rd at LaSalle St (EB)
  • Erwin Rd at LaSalle St (WB)
  • Fayetteville Rd at Sutton Station (SB)
  • Trent Dr at Duke Hospital South (EB)
  • Fayetteville Rd at Dunhill Dr (SB)
  • Chapel Hill St at Duke St (EB)
  • University Dr at Martin Luther King Jr Pkwy (EB)
  • Fulton St at Erwin Rd (NB)
  • Mt Moriah Rd at Danziger Dr (NB)
  • Renaissance Pkwy at Renaissance Village (WB)
  • Chapel Dr at Duke University Rd (NB)
  • Chapel Dr at Duke University Rd (SB)
  • Fayetteville Rd at Sutton Station (NB)
  • Wilmington St at Morgan St
  • Blue Ridge Rd at Westchase Blvd (SB)
  • Blue Ridge Rd at Trinity Rd (SB)
  • Western Blvd at Merendino St (WB)
  • Hillsborough St at Glenwood Ave (WB)
  • Hillsborough St at Enterprise St (WB)
  • Hillsborough St at Brooks Ave (WB)
  • Western Blvd at Powell Dr (WB)
  • Hillsborough St at Gardner St (EB)
  • Hillsborough St at Enterprise St (NCSU Bell Tower)
  • Hillsborough St at Faircloth St (WB)
  • Hillsborough St at Turner St (EB)
  • Western Blvd at Heather Dr (EB)
  • Hillsborough St at St Marys St (EB)
  • Ralph Stephens Rd at Collins Crossings Rd
  • S Main St at Rex Hospital (SB)
  • S Main St at Rex Hospital (NB)
  • S Main St at Village Walk Dr (NB)
  • NC 54 at Barbee Rd (WB)
  • Morgan St at Tryon Hill Dr
  • Morgan St at Hillsborough St
  • Morgan St at Boylan Ave
  • Morgan St at Glenwood Ave
  • West St at Raleigh Union Station
  • Martin St at McDowell St (EB)
  • Hillsborough St at Bashford Rd (EB)
  • Hillsborough St at Bashford Rd (WB)
  • Hillsborough St at Wolfwood Dr (EB)
  • Hillsborough St at Wolfwood Dr (WB)
  • Jones Ferry Park-and-Ride
  • Union Station - Bus Platform A
  • Harrington St at Martin St
  • Union Station - Bus Platform B
  • Slater Rd at Copley Pkwy (SB)
  • Slater Rd at Copley Pkwy (NB)
  • Airport Blvd at Slater Rd (EB)
  • Airport Blvd at Slater Rd (WB)
  • Jones Ferry Rd at Willow Creek SC (WB)
  • Jones Ferry Rd at Willow Creek SC (EB)
  • Martin St at Dawson St
  • Willard St at Durham Station
  • S Main St at NC 98 (NB)
  • S Main St at NC 98 (SB)
  • Holding Ave at Brooks St (WB)
  • Elm Ave at White St (EB)
  • S Main St at Wake Dr
  • S Main St at Aldi Food Market
  • S Main St at Ligon Mill Rd
  • S Main St at Ligon Mill Rd/ Walmart
  • S Main St at Rodgers Rd (Factory)
  • S Main St at Rodgers Rd (Wake Forest MS)
  • Wendell Falls Pkwy at Taylor Rd (Publix)
  • Wendell Falls Pkwy at Taylor Rd (WB)
  • Wendell Falls Pkwy at Martin Pond Rd (EB)
  • Wendell Falls Pkwy at Martin Pond Rd (WB)
  • Pony Rd at Duggins Oak Dr (EB)
  • Pony Rd at Duggins Oak Dr (WB)
  • Arendell Av at Gannon Av (NB)
  • Gannon Av at Arendell Ave (WB)
  • Arendell Av at Judd St (NB)
  • Gannon Av at Zebulon Commons (WB)
  • Hargett St at McDowell St
  • Peace St at Blount St
  • N Blount St at E Peace St
  • Morgan St at Dawson St
  • Shiloh Glenn Dr at Walmart (WB)
  • Shiloh Glenn Dr at Walmart (EB)
  • Shiloh Glenn Dr at Lower Shiloh Way (WB)
  • Shiloh Glenn Dr at Lower Shiloh Way (EB)
  • Pettigrew St at Mangum St (EB)
  • Alston St at Dupree St (SB)
  • Alston ave at Dupree St (NB)
  • Lawson St at Ridgeway Ave (EB)
  • Lawson St at Ridgeway Ave (WB)
  • Lawson St at Bacon St (EB)
  • Lawson St at Bacon St (WB)
  • Lawson St at DTCC Public Safety (EB)
  • Lawson St at Durham Tech (WB)
  • Ellis Rd at Feeney St (EB)
  • Ellis Rd at Feeney St (WB)
  • Ellis Rd at Advancement Av (EB)
  • Ellis Rd at Advancement Av (WB)
  • Ellis Rd at New Haven Ln (EB)
  • Ellis Rd at Brookville Ln (WB)
  • Miami Blvd at Ellis Rd (SB)
  • Miami Blvd at Ellis Rd (Bethesda ES)
  • Miami Blvd at New Haven Dr
  • Miami Blvd at Methodist St
  • Miami Blvd at Lumley Rd (SB)
  • Miami Blvd at Lumley Rd (NB)
  • Miami Blvd at TW Alexander Dr (SB)
  • Miami Blvd at TW Alexander Dr (NB)
  • Miami Blvd at Stirrup Creek Dr (PBM Graphics)
  • Miami Blvd at Stirrup Creek Dr (NB)
  • Miami Blvd at Patriot Dr (SB)
  • Miami Blvd at Patriot Dr (NB)
  • Miami Blvd at Cornwallis Rd (SB)
  • Miami Blvd at Cornwallis Rd (NB)
  • TW Alexander Dr at Reserach Commons (SB)
  • TW Alexander Dr at Reserach Commons (NB)
  • T.W. Alexander Dr at Cornwallis Rd (SB)
  • TW Alexander Dr at Cornwallis Rd (NB)
  • TW Alexander Dr at Moore Dr (WB)
  • TW Alexander Dr at Moore Dr (EB)
  • NC 54 at TW Alexander Dr (EB)
  • NC 54 at TW Alexander Dr (WB)
  • Durham Station (Parking Deck)
  • Western Blvd at Pullen Rd (EB)
  • Martin Luther King Jr Blvd at YMCA
  • Martin Luther King Jr Blvd at Airport Dr
  • Hopson Rd at Miami Blvd (WB)
  • Hopson at Faulkner St (EB)
  • Hopson at Faulkner St (WB)
  • Hopson Rd at Shiloh Rd (EB)
  • and 246 more (see the full list on the map or in the GeoJSON)

Over time

Overall score across the last 2 checks — up 0.5 since 2026-08-01.

2026-08-01: 69.22026-08-02: 69.7
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-08-0169.2 first check
2026-08-0269.7 up 0.5

What changed since your last check

  • Correctness up 1.0
  • Freshness no change
  • Rider experience no change

What changed in this feed

Overall score rose 0.5 points since 2026-08-01.

Same feed file as 2026-08-01; the published zip did not change.

No longer reported since 2026-08-01 (2 findings)

  • Future calendar (flagged by the MobilityData validator). (future_calendar)
  • Future feed (flagged by the MobilityData validator). (future_feed)

This records the later feed state. It does not establish who made a change or why.

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

Everything we checked

10 findings, ordered by severity.

Show every finding
  • Warning1959 instances

    1959 of 1959 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 (opens the GTFS Schedule reference on an external site)

  • Warning589 instances

    Some route lines list the same point twice in a row.

    Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export.

    Fix: Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt. (Usually one export setting.)

    Finding code: equal_shape_distance_same_coordinates · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning220 instances

    220 of 496 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 (opens the GTFS Schedule reference on an external site)

  • Warning51 instances

    Some scheduled trips move faster between stops than a bus can.

    Usually a typo'd stop time; riders get arrival times no bus can meet.

    Fix: Check the flagged stop times for transposed minutes. (A few minutes per flagged trip.)

    Finding code: fast_travel_between_consecutive_stops · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning42 instances

    Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: equal_shape_distance_diff_coordinates_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning18 instances

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

    Finding code: same_name_and_description_for_route · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

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

    Finding code: mixed_case_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    Some route long names repeat the route's short name inside them.

    Apps show both names together, so riders see the number twice, like '5 5 Downtown'.

    Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)

    Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    Many of the feed's trips don't run at all in the next 7 days.

    It usually means old service periods are still in the export, making the feed bigger and harder to check.

    Fix: Trim past service periods the next time you export. (One setting in most export tools.)

    Finding code: trip_coverage_not_active_for_next7_days · 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.)

    Finding code: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)

NTD GTFS readiness Ready

Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make 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 195 days.
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) Different (allowed)
Your feed's agency_id is f42c368f-0d16-403f-9c7c-493c9beb84ef; your National Transit Database ID is 40108. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id f42c368f-0d16-403f-9c7c-493c9beb84ef to NTD ID 40108, and keep the feed value stable. Do not change it solely to make the two values equal.
shapes.txt covers your trips Ready
All 1959 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. States wheelchair access on 56% 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 195 days.
Accessible Not yet
States wheelchair access on 56% 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 195 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

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 100 / 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 59 / 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.

GoTriangle GTFS data quality grade: D

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/gotriangle-3183/2026-08-02.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-02. 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.