Feed status · checked 2026-08-02
CobbLinc
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-08-01
Catalogued in Georgia.
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 47 minutes ago; last changed 31 days ago.
Measured 4 of 4 score categories from the agency's own feed.
How we measured this
Confidence in this measurement: high.
- All four score categories were measured this run.
- Realtime was sampled in one bounded window of 9 snapshots.
- 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
Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The trip updates realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
⏱ Usually a vendor support ticket.worth about +33 points in its category
Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The vehicle positions realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
⏱ Usually a vendor support ticket.worth about +33 points in its category
Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
The service alerts realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.
⏱ Usually a vendor support ticket.worth about +33 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
- The trip updates realtime feed failed during sampling.
- Next action
- Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
- 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
- Feed evidence
- The vehicle positions realtime feed failed during sampling.
- Next action
- Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
- 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
- Feed evidence
- The service alerts realtime feed failed during sampling.
- Next action
- Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.
- 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.
Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · 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.
Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · 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.
Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. · 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 is in 151 days.
- Published accessibility data
- Accessibility information is stated for 0% 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
- No realtime feed was reachable during sampling.
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
The MobilityData validator flagged 4 kinds of issue across 4 instances (0 error, 2 warning, 2 informational).
Service data covers the next 151 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.
2 accessibility depth signals
1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (10).
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.
612 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("17th Street at Market St Am", "17th St at Village Dr", "Akers Mill Rd at The Crossings At Akers", 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.
Sampled 9 times outside service hours: 0 of 3 configured feeds healthy; vehicle position plausibility was not measurable.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 625 stops.
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.
- 10 (orange)
- R10 (yellow)
- 15 (pink)
- BLU (gray)
- 20 (gray)
- 25 (teal)
- 30 (green)
- 40 (green)
- 45 (gray)
- 50 (brown)
| Route | Type | Line color |
|---|---|---|
| 10 MARTA Arts Center - Marietta TC | Bus | orange |
| R10 Midtown ATL - KSU-Kennesaw Rapid | Bus | yellow |
| 15 CTC - MTC via Windy Hill | Bus | pink |
| BLU Cumberland Circulator | Bus | gray |
| 20 CTC - MTC via S. Cobb Drive | Bus | gray |
| 25 MARTA H.E. Holmes - Cumberland | Bus | teal |
| 30 MARTA H.E. Holmes - Marietta TC | Bus | green |
| 40 KSU-Kennesaw - MTC via Marietta | Bus | green |
| 45 KSU-Kennesaw - MTC via US 41 | Bus | gray |
| 50 CTC - MTC via Powers Ferry | Bus | brown |
List every stop
- 17th Street at Market St Am
- 17th St at Village Dr
- Akers Mill Rd at The Crossings At Akers
- Akers Mill Rd at Cumberland Mall Entranc
- Burton Rd at Hamilton E Holmes Dr
- Hamilton E Holmes Dr at Burton Rd NW
- MLK Jr Dr at Stone Hurst Pl
- Six Flags Pkwy at S Service Rd
- Marta Holmes Station
- 15th Street @ West Peachtree Street
- Cumberland Transfer Center
- Cumberland Blvd at Spring Hill Pkwy
- Spring Rd at Cumberland Blvd
- Cobb Pkwy at Windy Ridge Pkwy
- Cobb Pkwy at Herodian Way
- Cobb Pkwy at Kenwood Creek
- Cobb Pkwy at Lake Park Dr
- Cobb Pkwy at Ed Voyles Honda
- Cobb Pkwy at Windy Hill Rd
- Cobb Pkwy at Terrell Mill Rd
- Cobb Pkwy at Airport Industrial Park Dr
- Cobb Pkwy at Cumberland Point Dr
- Cobb Pkwy at After Cumberland Pt Dr
- Cobb Pkwy at Davis Ln
- Cobb Pkwy at Franklin Rd
- Cobb Pkwy at Franklin Dr
- Cobb Pkwy at Spinks Dr
- Cobb Pkwy at Wylie Rd
- Cobb Pkwy at Barclay Cir
- Cobb Pkwy at After Barclay Circle
- Cobb Pkwy at New Hope Rd
- Cobb Pkwy at Amf Marietta Lanes
- S Marietta Pkwy at Martin Ct
- S Marietta Pkwy at Lockheed Ave
- S Marietta Pkwy at Lake Dr
- Marietta Transfer Center
- S Marietta Pkwy at Rossbacher Way
- S Marietta Pkwy at Technology Pkwy
- Cobb Pkwy at S Marietta Pkwy
- Cobb Pkwy at Life'S Way
- Cobb Pkwy at Former Team Nissan
- Cobb Pkwy at Wylie Rd
- Cobb Pkwy at Spinks Dr
- Cobb Pkwy at Franklin Dr
- Cobb Pkwy at Franklin Dr
- Cobb Pkwy at Franklin Rd
- Cobb Pkwy at Enterprise Way
- Cobb Pkwy at Cumberland Point Dr
- Cobb Pkwy at Caswell Pkwy
- Cobb Pkwy at Terrell Mill Rd
- Cobb Pkwy at Windy Hill Rd
- Cobb Pkwy at Steve Rayman Chevrolet
- Cobb Pkwy at Lake Park Dr
- Cobb Pkwy at 2330 Cobb Apartment Homes
- Cobb Pkwy at Hargrove Rd
- Spring Rd at Cobb Pkwy
- Cumberland Blvd at Spring Hill Pkwy
- Powers Ferry Rd at Custom Signs Building
- W/H @ S Park Pl
- W/H @ S Park Pl
- W/H @ Venlo Ave
- W/H @ Cobb Pkwy
- W/H @ Chris Volvo
- W/H @ Roswell St
- W/H @ Atlanta Rd
- W/H @ Belmont Cir
- W/H @ San Fernando Dr
- W/H @ Old Concord Rd
- W/H @ Wakita Dr
- W/H @ Bouldercrest Dr
- W/H @ Larose Dr
- W/H @ Kennedy Ln
- W/H @ Beverly Ln
- Austell Rd at Arkose Dr
- County Services Pkwy at Kurt Dr
- County Services Pkwy at Al Bishop Dr
- County Services Pkwy at Cobb Co Composti
- County Services Pkwy at Cobb County Heal
- County Services Pkwy at Department Of Mo
- P/S @ Cunningham Rd
- P/S @ Bellemeade Dr
- P/S @ Natchez Trace
- P/S @ Longwood Dr
- P/S @ Booth Rd
- P/S @ Springs Landing Apts
- P/S @ Chestnut Hill Rd
- P/S @ Sandtown Rd
- Powder Springs St at W Dixie Ave
- Roswell St at Anderson St
- Roswell St at Cole St
- Fairground St at Pierce St
- Fairground St at Frasier St
- S Marietta Pkwy at Parkway Plaza
- Fairground St at S Marietta Pkwy
- Fairground St at Frasier St
- Fairground St at Pierce St
- Roswell St at Rogers St
- Roswell St at Lakewood Dr
- P/S @ Griggs St
- P/S @ W Gramling St
- P/S @ Sandtown Rd
- P/S @ Chestnut Hill Rd
- P/S @ Booth Rd
- P/S @ Laurel Springs Ln
- P/S @ Baltimore Pl
- P/S @ Cunningham Rd
- County Services Pkwy at Cobb County Publ
- County Services Pkwy at Cobb County Heal
- County Services Pkwy at Cobb County Park
- County Services Pkwy at Al Bishop Dr
- County Services Pkwy at Austell Rd
- Austell Rd at Arkose Dr
- W/H @ Cherrywood Ln
- W/H @ Favor Rd
- W/H @ Larose Dr
- W/H @ Benson Poole Rd
- W/H @ Old Concord Rd
- W/H @ Beaver Creek Rd
- W/H @ Belmont Cir
- W/H @ Roswell St
- W/H @ Cobb Pkwy
- W/H @ Cobb Pkwy
- W/H @ N Park Pl
- W/H @ S Park Pl
- W/H @ Corporate Plaza Pkwy
- Windy Hill Road @ Circle 75 Parkway
- Spring Rd SE at Galleria Ln
- Spring Rd SE at Carolyn Dr
- Spring Rd SE at Cumberland Valley Dr
- Spring Rd at Jonquil Dr
- Concord Rd SE at Atlanta Rd
- Concord Rd SE at Khuan'S Hair Design / A
- S Cobb Dr at Mill Pond Rd
- S Cobb Dr
- S Cobb Dr at King Springs Rd
- S Cobb Dr at Lake Dr
- S Cobb Dr at Concord Rd
- S Cobb Dr at Ask-Kay Dr
- S Cobb Dr at Plaza Dr
- S Cobb Dr at Powder Springs St
- S Cobb Dr at Glendale Pl
- S Cobb Dr at Windy Hill Rd
- S Cobb Dr at Old Concord Rd
- S Cobb Dr at Pat Mell Rd
- S Cobb Dr at Dink Ln
- S Cobb Dr at Harmony Meadows Apartments
- S Cobb Dr at Waldrep Cir
- S Cobb Dr at Oak St
- S Cobb Dr at Barber Rd
- S Cobb Dr at Austell Rd
- S Cobb Dr at Walthall Ave
- S Cobb Dr at Leader Rd
- S Cobb Dr at Leader Rd
- S Cobb Dr at Beech Rd
- S Cobb Dr at Carruth Dr
- S Cobb Dr at Appleton Dr
- S Cobb Dr at Pearl St
- Fairground St at Commerce Park Dr
- Fairground St at S Marietta Pkwy
- Fairground St at Commerce Park Dr
- Fairground St at Glover St
- Fairground St at S Cobb Dr
- S Cobb Dr at Atlanta St
- S Cobb Dr at Pearl St
- S Cobb Dr at Appleton Dr
- S Cobb Dr at Lakeside Apts
- S Cobb Dr at Beech Rd
- S Cobb Dr at Booth Rd
- S Cobb Dr at Walthall Ave
- S Cobb Dr at Austell Rd
- S Cobb Dr at Oak St
- S Cobb Dr at Waldrep Cir
- S Cobb Dr at Harmony Meadows Apts
- S Cobb Dr at Pat Mell Rd
- S Cobb Dr at Benson Poole Rd
- S Cobb Dr at Windy Hill Rd
- S Cobb Dr at Glendale Pl
- S Cobb Dr at Powder Springs St
- S Cobb Dr at Plaza Dr
- S Cobb Dr at Ask-Kay Dr
- S Cobb Dr at Church Rd
- S Cobb Dr at Concord Rd
- Concord Rd SE at Mccaulley Rd
- Spring Rd SE at Atlanta Rd
- Spring Rd SE at Jonquil Dr
- Spring Rd SE at Village Pkwy
- Spring Rd SE at Campbell Rd
- S Service Rd at Riverside Pkwy
- Six Flags Dr at Riverside Pkwy
- Six Flags Dr at Six Flags Pkwy
- Six Flags Dr at Elsner Rd
- Six Flags Dr at Factory Shoals Rd
- S Cobb Dr at King Springs Rd
- S Cobb Dr at Cooper Lake Rd
- Factory Shoals Rd at Britt Rd
- Factory Shoals Rd at Mableton Pkwy
- Mableton Pkwy at Old Powder Springs Rd
- Mableton Pkwy at Old Gordon Road
- Mableton Pkwy at Veterans Memorial Hwy
- Floyd Rd at Veterans Memorial Hwy
- Floyd Rd at Fontaine Rd
- Mable House Park And Ride
- Floyd Rd at Ayres Rd
- Floyd Rd at White Blvd
- Floyd Rd at Hicks Rd
- Floyd Rd at Bates Rd
- Floyd Rd at Trestle Dr
- Floyd Rd at East-West Conn
- East-West Connector at Floyd Rd
- East-West Connector at Hospital South Dr
- Austell Rd at East-West Conn
- Austell Rd at Hospital South Dr
- Austell Rd at Story Pl SW
- Austell Rd at Floyd Rd
- Austell Rd at Mimosa Dr
- Austell Rd at Amy Ln
- Austell Rd at Westbrook Mobile Homes
- Austell Rd at Lanier Dr
- Austell Rd at Byers Dr
- Austell Rd at Milford Church Rd
- Austell Rd at Crest Ridge Rd
- Austell Rd at E Callaway Rd
- Austell Rd at Hicks Rd
- Austell Rd at County Services Pkwy
- Austell Rd at Lorene Dr
- Austell Rd at Pat Mell Rd
- Austell Rd at Cunningham Rd
- Austell Rd at Austell Circle
- Austell Rd at Sandtown Rd
- Austell Rd at Cochran Rd
- Austell Rd at Knox Dr
- Austell Rd at Pair St
- Atlanta Rd at Austell Rd
- Atlanta St at S Cobb Dr
- S Marietta Pkwy at Atlanta St
- S Marietta Pkwy at Manget St
- S Marietta Pkwy at Manget St
- Atlanta St at S Marietta Pkwy
- Atlanta St at S Cobb Dr
- Atlanta Rd at Clay Dr
- Austell Rd at Joyner Ave
- Austell Rd at S Cobb Dr
- Austell Rd at Pair St
- Austell Rd at Sandtown Rd
- Austell Rd at Austell Cir
- Austell Rd at Cunningham Rd
- Austell Rd at Pat Mell Rd
- Austell Rd at Kurt Dr
- Austell Rd at Windy Hill Rd
- Austell Rd at Callaway Rd
- and 375 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-08-01.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 61.2 | first check |
| 2026-07-30 | 61.2 | no change |
| 2026-08-01 | 61.2 | no change |
| 2026-08-02 | 61.2 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
- Realtime quality no change
What changed in this feed
Overall grade and score held steady since 2026-08-01.
Same feed file as 2026-08-01; 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
11 findings, ordered by severity.
Show every finding
- Error1 instance
The trip updates realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)
Finding code: scorecard_rt_trip_updates_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Error1 instance
The vehicle positions realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)
Finding code: scorecard_rt_vehicle_positions_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Error1 instance
The service alerts realtime feed failed during sampling.
When this feed is down, riders see scheduled times presented as if they were live.
Fix: Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request. (Usually a vendor support ticket.)
Finding code: scorecard_rt_service_alerts_unreachable · Read the fix guide · See GTFS-Realtime reference (opens the GTFS-Realtime reference on an external site)
- Warning1177 instances
1177 of 1177 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)
- Warning625 instances
625 of 625 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)
- 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 (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)
- Info1 instance
Future calendar (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'future_calendar' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: future_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info1 instance
Future feed (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'future_feed' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: future_feed · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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 (opens the validator rules 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 151 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) 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 1177 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 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 151 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.
Realtime reliability
The realtime feed responded on 0.0% of 200 checks over the last 34 days, with lag not reported by the feed.
Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.
Clears the Google and Apple Maps four-week coverage bar. This feed has 151 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 91 / 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 38 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality 0 / 100
- 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.
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/cobblinc/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.