GTFS Scorecard
← All agencies

Feed status · checked 2026-08-01

Chatham Area Transit (CAT)

Based on the feed this agency publishes

Service mode Bus

8.7 / 100

unchanged since 2026-07-31

Catalogued in Georgia.

Feed expiredAccessibility 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 20 hours ago; last changed 5 days ago; last fetch returned HTTP 404.

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

Fix 01

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

Fix 02

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

Point near origin (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +24 points in its category

Fix 03

Re-generate shape distances in your export; flag to your vendor if it persists.Likely your export tool

Some trips have stop times whose distances along the route go backwards. Apps can show buses jumping backwards or mis-order stops.

⏱ Usually an export-tool fix, not hand editing.worth about +18 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 1728 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
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. 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.

  2. Review the rule documentation for 'point_near_origin' 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.

  3. Re-generate shape distances in your export; flag to your vendor if it persists.

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

Correctness3.5 / 100

The MobilityData validator flagged 11 kinds of issue across 4817 instances (1178 error, 3638 warning, 1 informational).

Freshness0.0 / 100

Service data ended 1728 day(s) ago. Trip planners have likely already dropped this feed.

Rider experience23.0 / 100

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.

Accessibility0 / 100

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

2 accessibility depth signals

  • 2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (27, 6).

    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.

  • 1215 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("YORK & ABERCORN EB", "ABERCORN & MACON SB", "ABERCORN & HENRY SB", 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 97 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.

  • 10 (gray)
  • 11 (pink)
  • 12 (brown)
  • 14 (purple)
  • 17 (teal)
  • 20 (yellow)
  • 25 (red)
  • 27 (purple)
  • 28 (green)
  • 29 (purple)
  • 3 (brown)
  • 31 (red)
  • 3B (orange)
  • 4 (teal)
  • 6 (yellow)
  • 77 (teal)
  • 7D (red)
  • 7F (green)
Routes in Chatham Area Transit (CAT)'s feed
RouteTypeLine color
10 EAST SAVANNAHBusgray
11 CANDLERBuspink
12 HENRYBusbrown
14 ABERCORN LOCALBuspurple
17 SILK HOPEBusteal
20 SKIDAWAY ISLAND/COFFEE BLUFFBusyellow
25 MLK WESTLAKE APTSBusred
27 WATERSBuspurple
28 WATERSBusgreen
29 W GWINNETTBuspurple
3 WEST CHATHAMBusbrown
31 SKIDAWAY/SANDFLYBusred
3B AUGUSTA AVE/GARDEN CITY/HUDSON HILLBusorange
4 BARNARDBusteal
6 CROSS TOWNBusyellow
77 SAVANNAH BELLES FERRYBusteal
7D 7 EASTERN WHARFBusred
7F 7 FORSYTHBusgreen
List every stop
  • AUGUSTA & E LATHROP WB
  • YORK & ABERCORN EB
  • MLK & TURNER SB
  • MLK & LIBERTY SB
  • LOUISVILLE & ROTHWELL WB
  • LOUISVILLE & STILES WB
  • AUGUSTA & NEWELL WB
  • AUGUSTA & FERRILL WB
  • AUGUSTA & EAGLE WB
  • AUGUSTA & DELYON WB
  • AUGUSTA & BRITTANY WB
  • AUGUSTA & GRAHAM WB
  • BROUGHTON & MONTGOMERY EB
  • W BAY & LISSNER WB
  • ABERCORN & TIBET NB
  • WALMART & FULTON WB
  • ROSE OF SHARON WB
  • US 25 & SHAVERS WB
  • CHATHAM PLAZA
  • MALL BLVD & OGLETHORPE MALL EB
  • ABERCORN & HENRY SB
  • ABERCORN & OGLETHORPE NB
  • OGLETHORPE MALL
  • ABERCORN & TIBET SB
  • SAVANNAH MALL
  • ABERCORN & HENRY NB
  • ABERCORN & LIBERTY SB
  • ABERCORN & JONES SB
  • ABERCORN & WAYNE SB
  • ABERCORN & HUNTINGDON SB
  • ABERCORN & HALL SB
  • ABERCORN & BOLTON SB
  • HWY 21 & CROSSGATE WB
  • ABERCORN & PARK SB
  • ABERCORN & 33rd SB
  • ABERCORN & 35th SB
  • ABERCORN & 37th SB
  • ABERCORN & 39th SB
  • ABERCORN & WASHINGTON SB
  • ABERCORN & 51st SB
  • ABERCORN & 54th SB
  • ABERCORN & 63rd SB
  • ABERCORN & 65th SB
  • ABERCORN & JEWISH EDUCATION ALLIANCE SB
  • ABERCORN & DERENNE SB
  • ABERCORN & 5501 SB
  • ABERCORN & HOMEWOOD SUITES SB
  • ABERCORN & JACKSON SB
  • OGLETHORPE MALL & SEARS AUTO CENTER
  • ABERCORN & HAVERTY'S SB
  • ABERCORN & CHRYSLER JEEP DODGE SB
  • ABERCORN & LEWIS SB
  • ABERCORN & TELEVISION SB
  • ABERCORN & WILSHIRE SB
  • ABERCORN & DEERFIELD SB
  • ABERCORN & LARGO SB
  • ABERCORN & PIZZA HUT SB
  • ABERCORN & MERCY SB
  • ABERCORN & ARTS SB
  • APACHE & MALL ENTRANCE SB
  • ABERCORN & ARMSTRONG CENTER NB
  • ABERCORN & STAPLES NB
  • ABERCORN & LARGO NB
  • ABERCORN & DEERFIELD NB
  • ABERCORN & WILSHIRE NB
  • ABERCORN & TELEVISION NB
  • ABERCORN & LEWIS NB
  • ABERCORN & MONTGOMERY CROSS NB
  • ABERCORN & FAIRMONT NB
  • ABERCORN & WHITE BLUFF NB
  • MALL BOULEVARD & KROGER WB
  • MALL BLVD & ABERCORN WB
  • ABERCORN & ECHOLS NB
  • ABERCORN & STEHPHENSON NB
  • ABERCORN & JANET SB
  • ABERCORN & BRANDYWINE NB
  • ABERCORN & 65th NB
  • ABERCORN & 62nd NB
  • ABERCORN & 56th NB
  • ABERCORN & 54th NB
  • ABERCORN & 51st NB
  • ABERCORN & 49th NB
  • ABERCORN & WASHINGTON NB
  • ABERCORN & 39th NB
  • ABERCORN & 37th NB
  • ABERCORN & 35th NB
  • ABERCORN & ANDERSON NB
  • ABERCORN & PARK NB
  • ABERCORN & BOLTON NB
  • ABERCORN & HUNTINGDON NB
  • ABERCORN & JONES NB
  • ABERCORN & MACON NB
  • ABERCORN & LIBERTY NB
  • ST JOSEPHS HOSPITAL MAIN ENTRANCE
  • PHILLIPS-WINTERS APTS
  • ABERCORN & ANDERSON SB
  • ABERCORN & OGLETHORPE SB

Over time

Overall score across the last 4 checks — unchanged since 2026-07-31.

2026-07-25: 8.72026-07-30: 8.72026-07-31: 8.72026-08-01: 8.7
Show the numbers
CheckScoreChange
2026-07-258.7 first check
2026-07-308.7 no change
2026-07-318.7 no change
2026-08-018.7 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change

Everything we checked

19 findings, ordered by severity.

Show every finding
  • Error1154 instances

    Point near origin (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: point_near_origin · See MobilityData GTFS Validator rules

  • Error21 instances

    Some trips have stop times whose distances along the route go backwards.

    Apps can show buses jumping backwards or mis-order stops.

    Fix: Re-generate shape distances in your export; flag to your vendor if it persists. (Usually an export-tool fix, not hand editing.)

    Finding code: decreasing_or_equal_stop_time_distance · See MobilityData GTFS Validator rules

  • Error2 instances

    Number out of range (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: number_out_of_range · See MobilityData GTFS Validator rules

  • Error1 instance

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

    See the linked rule for what this affects.

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

    Finding code: equal_shape_distance_diff_coordinates · See MobilityData GTFS Validator rules

  • Error1 instance

    Service data ended 1728 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

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

  • Warning3033 instances

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

  • Warning1252 instances

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

  • Warning347 instances

    347 of 3033 trips lack rider-facing destination or direction text.

    When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming.

    Fix: Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign. (Usually one value per route pattern in your scheduling source.)

    Finding code: scorecard_missing_headsigns · Read the fix guide · See GTFS Best Practices

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

  • Warning4 instances

    Some service calendars in the feed have already ended.

    Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.

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

    Finding code: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning3 instances

    Some service calendars have no days of the week switched on.

    Trips tied to these calendars never run; they are dead data that can mask real schedule problems.

    Fix: Delete the empty calendars or set their service days. (A few minutes in your scheduling software.)

    Finding code: service_has_no_active_day_of_the_week · Read the fix guide · See MobilityData GTFS Validator rules

  • 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

  • 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

  • Warning1 instance

    feed_info.txt is missing its start/end dates (the file itself is absent)

    Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.

    Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)

    Finding code: scorecard_missing_feed_info_dates · Read the fix guide · See MobilityData GTFS Validator rules

  • 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

  • Info1071 instances

    About 1071 stop names are written in ALL CAPS.

    Mixed-case names are easier to read in apps and are read more naturally by screen readers.

    Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)

    Finding code: scorecard_stop_names_all_caps · Read the fix guide · See GTFS Best Practices

  • Info1 instance

    The feed includes a file that is not part of the GTFS spec.

    Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.

    Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)

    Finding code: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules

  • 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

NTD GTFS readiness Not ready

Resolve this before you certify on the D-10. 4 validator errors to resolve. Service data expired 1728 days ago, so FTA would find the link out of date.

Published Ready
Published at a public URL.
Valid Needs attention
4 validator errors to resolve.
Current Not ready
Service data expired 1728 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 3033 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. 4 validator errors to resolve. Service data expired 1728 days ago. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.

Valid Not yet
4 validator errors to resolve.
Current Not yet
Service data expired 1728 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 1178 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 4 / 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 23 / 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.

Chatham Area Transit (CAT) GTFS data quality grade: F

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/chatham-area-transit-cat/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.