Feed status · checked 2026-08-01
Cobb Community Transit (CCT)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
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 11 hours ago; last fetch returned HTTP 403.
Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.
How we measured this
Confidence in this measurement: provisional.
- Realtime quality was not measured this run. It does not count against the grade.
- The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool
Service data ended 944 day(s) ago. When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category
Review the rule documentation for 'missing_required_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Missing required file (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points in its category
Review the rule documentation for 'invalid_input_files_in_subfolder' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid input files in subfolder (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points in its category
Finding handoff
Move one finding to a recheck
Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.
- Feed evidence
- Service data ended 944 day(s) ago.
- Next action
- Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.
- Recheck
- Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
- Feed evidence
- Missing required file (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'missing_required_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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
- Invalid input files in subfolder (flagged by the MobilityData validator).
- Next action
- Review the rule documentation for 'invalid_input_files_in_subfolder' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
- 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.
Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Review the rule documentation for 'missing_required_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Review the rule documentation for 'invalid_input_files_in_subfolder' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Make the change. Make this change in whatever tool produces your feed, then re-export.
Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.
Rider view: what this feed publishes
A quick read of rider-facing information in this feed.
- Schedule visibility
- The feed's last published service date was 944 days ago.
- 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
- Realtime-feed availability and live-arrival coverage are not known from this scorecard.
Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.
Send your vendor a fix request
You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.
Send the agency a note
Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.
Score by category
The MobilityData validator flagged 4 kinds of issue across 8 instances (7 error, 1 warning, 0 informational).
Service data ended 944 day(s) ago. Trip planners have likely already dropped this feed.
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.
1 accessibility depth signal
670 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Cumberland Blvd at Spring Hill Pkwy", "Spring Rd at Cumberland Blvd", "Cobb Pkwy at Windy Ridge Pkwy", 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.
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 697 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 (black)
- 100 (black)
- 101 (black)
- 102 (black)
- 15 (green)
- 20 (black)
- 25 (black)
- 30 (black)
- 40 (black)
- 45 (black)
- 50 (black)
- BLUE (white)
- GREEN (white)
- RAPID (white)
| Route | Type | Line color |
|---|---|---|
| 10 Arts Center Station/Marietta TC | Bus | black |
| 100 Civic Center Station/Busbee P&R | Bus | black |
| 101 Civic Center/Five Points/MTC | Bus | black |
| 102 Arts Center Station/Acworth P&R | Bus | black |
| 15 CTC - MTC via Windy Hill | Bus | green |
| 20 CTC - MTC via S. Cobb Drive | Bus | black |
| 25 Hamilton E. Holmes Station/CTC | Bus | black |
| 30 Hamilton E. Holmes Station/MTC | Bus | black |
| 40 KSU-Kennesaw - MTC via Marietta | Bus | black |
| 45 KSU-Kennesaw - MTC via US 41 | Bus | black |
| 50 CTC - MTC via Powers Ferry | Bus | black |
| 999 Test Route | Bus | white (no shape in feed) |
| BLUE Cumberland Transfer CTC/Battery | Bus | white |
| GREEN Battery/Windy Hill | Bus | white |
| RAPID Arts Station/KSU-Kennesaw Rapid | Bus | white |
List every stop
- Cobb Pkwy at Kenwood Creek
- 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
- Cobb Pkwy at Lake Park Dr
- Powder Springs St at Griggs St
- Powder Springs St at W Gramling St
- Powder Springs St at Sandtown Rd
- Powder Springs St at Chestnut Hill Rd
- Powder Springs St at Booth Rd
- Powder Springs St at Laurel Springs Ln
- Powder Springs Rd at Baltimore Pl
- Powder Springs St at Cunningham Rd
- Cobb Pkwy at Ed Voyles Honda
- Powder Springs Rd at Chapel Dr
- County Services Pkwy at Cobb County Public Safety
- COUNTY SERVICES PKWY + COBB COUNTY HEALTH DEPARTMENT
- County Services Pkwy at Cobb County Park And Recre
- County Services Pkwy at Al Bishop Dr
- County Services Pkwy at Austell Rd
- Austell Rd at Arkose Dr
- Windy Hill Rd at Cherrywood Ln
- Windy Hill Rd at Favor Rd
- Windy Hill Rd at Larose Dr
- Cobb Pkwy at Windy Hill Rd
- Windy Hill Rd at Benson Poole Rd
- Windy Hill Rd at Old Concord Rd
- Windy Hill Rd at Beaver Creek Rd
- Windy Hill Rd at Belmont Cir
- Windy Hill Rd at Roswell St
- Windy Hill Rd at Cobb Pkwy
- Windy Hill Rd at Cobb Pkwy
- Windy Hill Rd at N Park Pl
- Windy Hill Rd at S Park Pl
- Windy Hill Rd at Corporate Plaza Pkwy
- Cobb Pkwy at Terrell Mill Rd
- Windy Hill Rd at Powers Ferry Rd
- 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 + Khuan's Hair Design/Arkle Veterina
- Cobb Pkwy at Airport Industrial Park Dr
- 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
- Cobb Pkwy at Cumberland Point Dr
- 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 Oak St
- S Cobb Dr at Barber Rd
- S Cobb Dr at Austell Rd
- S Cobb Dr at Walthall Ave
- Cobb Pkwy at After Cumberland Pt Dr
- 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
- Cobb Pkwy at Davis Ln
- 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
- Cobb Pkwy at Franklin Rd
- 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
- Cobb Pkwy at Franklin Dr
- 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
- Cobb Pkwy at Spinks Dr
- 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
- Cobb Pkwy at Wylie Rd
- 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
- Cobb Pkwy at Barclay Cir
- 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
- Cobb Pkwy at After Barclay Circle
- 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
- Cobb Pkwy at New Hope 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
- Cobb Pkwy at Amf Marietta Lanes
- 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
- S Marietta Pkwy at Martin Ct
- Austell Rd at Callaway Rd
- Austell Rd at Waymar Dr
- Austell Rd at Milford Church Rd
- Austell Rd at Pair Rd
- Austell Rd at Raes Creek Rd
- Austell Rd at Mimosa Dr
- Austell Rd at Reed Dr
- Austell Rd SW at Hurt Rd SW
- Austell Rd SW at Mulkey Rd SW
- Austell Rd at Hospital South Dr
- S Marietta Pkwy at Lockheed Ave
- East-West Connector at Brookwood Dr
- East-West Connector at Floyd Rd
- Floyd Rd at Willowbrook Lane
- Floyd Rd at Floyd Dr
- Floyd Rd at Hicks Rd
- Floyd Rd at Nickajack Rd
- Floyd Rd at Patterns Dr
- Floyd Rd at Mableton Park & Ride - Ob
- Floyd Rd at Fontaine Rd
- Floyd Rd at Veterans Memorial Hwy
- S Marietta Pkwy at Lake Dr
- Mableton Pkwy at Glore Cir
- Mableton Pkwy at Old Alabama Rd
- Mableton Pkwy at Old Powder Springs Rd
- Mableton Pkwy SW at Lane Dr
- Mableton Pkwy at Factory Shoals Rd
- Factory Shoals Rd at S Gordon Rd
- Six Flags Dr at Whisper Ct
- Six Flags Dr at Elsner Rd
- Six Flags Dr at Six Flags Pkwy
- Marietta Transfer Center
- Frey Rd at Campus Loop
- Busbee Dr at Townpark Ln
- Cumberland Blvd at S Cobb Dr
- Busbee Pkwy at PGA Superstore
- Ring Rd at Jc Penney Entrance
- S Marietta Pkwy at Hudson Rd
- Busbee Pkwy at Town Center Dr
- Cumberland Pkwy at Atlanta Rd
- Barrett Pkwy at Mall Blvd
- Barrett Pkwy at Barrett Creek Dr
- Barrett Pkwy at Bells Ferry Rd
- Bells Ferry Rd at Barrett Pkwy
- Bells Ferry Rd at Arnold Ave
- Bells Ferry Rd at Laurel Hills Preserve
- Bells Ferry Rd at Oak Harbor Trl
- Bells Ferry Rd at Bridgestone Dr
- S Marietta Pkwy at Rossbacher Way
- Bells Ferry Rd at Cobb Pkwy
- Church St Ext at Loudermilk Dr
- Church St Ext at Elizabeth St
- Church St at Whitcher St
- Church St at Hillside Ave
- Church St at Sessions St
- Church St at Kennesaw Ave
- Cumberland Pkwy at Beech Haven Tr
- Cumberland Blvd at Magnolia Vinings Apts
- S Service Rd at Riverside Pkwy
- S Marietta Pkwy at Technology Pkwy
- Cherokee St at Montgomery St
- Cherokee St at Freyer Rd
- Cherokee St at Chicopee Dr
- Cherokee St at Lewis Dr
- Church St Ext at Elizabeth St
- Bells Ferry Rd at Old 41 Hwy
- Bells Ferry Rd at Cobb Pkwy
- Bells Ferry Rd at Adair Dr
- Bells Ferry Rd at Bridgestone Dr
- Bells Ferry Rd at Mark Ave
- and 447 more (see the full list on the map or in the GeoJSON)
Over time
Overall score across the last 4 checks — unchanged since 2026-07-31.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-07-25 | 38.0 | first check |
| 2026-07-30 | 38.0 | no change |
| 2026-07-31 | 38.0 | no change |
| 2026-08-01 | 38.0 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Everything we checked
9 findings, ordered by severity.
Show every finding
- Error5 instances
Missing required file (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_required_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: missing_required_file · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Invalid input files in subfolder (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_input_files_in_subfolder' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: invalid_input_files_in_subfolder · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Missing calendar and calendar date files (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'missing_calendar_and_calendar_date_files' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: missing_calendar_and_calendar_date_files · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Service data ended 944 day(s) ago.
When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist.
Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)
Finding code: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning1820 instances
1820 of 1820 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)
- Warning697 instances
697 of 697 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
A file GTFS asks for (usually feed_info.txt) is missing.
feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.
Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)
Finding code: missing_recommended_file · 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
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 Not ready
Resolve this before you certify on the D-10. 3 validator errors to resolve. Service data expired 944 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 3 validator errors to resolve.
- Current Not ready
- Service data expired 944 days ago, so FTA would find the link out of date.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
- agency_id equals your NTD ID (optional) Not checked yet
- This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
- shapes.txt covers your trips Ready
- All 1820 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. 3 validator errors to resolve. Service data expired 944 days ago. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Not yet
- 3 validator errors to resolve.
- Current Not yet
- Service data expired 944 days ago.
- 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.
Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks. The feed also carries 7 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.
How this agency maps to the standards
The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.
- Correctness 60 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
- Freshness 0 / 100
- GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
- Rider experience 38 / 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.
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/cobb-community-transit-cct/2026-08-01.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-08-01. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.