Prep for a call: printable one-page brief · For your board packet: printable one-pager · Compare with another agency · Watch this feed: get an email before it expires
Feed status · checked 2026-07-09
Xpress
Based on the feed this agency publishes
unchanged since 2026-07-08
Ahead of 47% of all tracked agencies and 46% of small agencies. Operates 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.1, validator 8.0.1.
Checked for changes 8 hours 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
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 1105 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
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
Review the rule documentation for 'invalid_email' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Invalid email (flagged by the MobilityData validator). See the linked rule for what this affects.
⏱ Varies.worth about +12 points
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
96 of 96 stops don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points
Close the loop on each fix. Read the guide, make the change in your tool, and let the next run verify it — the scorecard shows the fix; the agency publishes it.
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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Review the rule documentation for 'invalid_email' 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.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. · Read the fix guide
Make the change. Make this change in whatever tool produces your feed, then re-export.
Prove it cleared. The next scorecard run re-checks this automatically and, once it is gone, mints a dated receipt. Self-check a feed before you publish.
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 5 instances (1 error, 4 warning, 0 informational).
Service data ended 1105 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 published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
Fares are applied to trips.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
Skip to route and stop dataBasemap: OpenFreeMap, © OpenStreetMap contributors. Routes and stops: this agency's GTFS feed.
- 400 (teal)
- 401 (teal)
- 410 (teal)
- 411 (teal)
- 412 (teal)
- 413 (teal)
- 414 (teal)
- 416 (teal)
- 417 (teal)
- 419 (green)
- 423 (green)
- 426 (green)
- 428 (green)
- 430 (orange)
- 431 (orange)
- 432 (orange)
- 440 (orange)
- 441 (orange)
- 442 (orange)
- 453 (orange)
- 463 (purple)
- 476 (purple)
- 480 (teal)
- 483 (teal)
- 484 (teal)
- 485 (teal)
- 490 (teal)
| Route | Type | Line color |
|---|---|---|
| 400 Cumming - Downtown | Bus | teal |
| 401 Cumming - Perimeter | Bus | teal |
| 410 Sugarloaf Mills - Lindbergh Cent | Bus | teal |
| 411 Hamilton Mill/Mall of GA - MT | Bus | teal |
| 412 Sugarloaf Mills - Midtown | Bus | teal |
| 413 Hamilton Mill/Mall of GA - DT | Bus | teal |
| 414 Ham Mill/Mall of GA/Sugarloaf-MT | Bus | teal |
| 416 Dacula - Downtown | Bus | teal |
| 417 Sugarloaf Mills - Perimeter | Bus | teal |
| 419 Snellville/Hewatt/Stone Mtn - DT | Bus | green |
| 423 E Conyer/W Conyer/Panola - MT | Bus | green |
| 426 E Conyer/W Conyer/Panola - DT | Bus | green |
| 428 W Conyers/Panola - Perimeter | Bus | green |
| 430 McDonough - Downtown | Bus | orange |
| 431 BrandsMart/Stockbridge - MT | Bus | orange |
| 432 BrandsMart/Stockbridge - DT | Bus | orange |
| 440 Hampton/Jonesboro - DT/MT | Bus | orange |
| 441 Jonesboro - Downtown/Midtown | Bus | orange |
| 442 Riverdale - Downtown | Bus | orange |
| 453 Newnan/Union City - DT/MT | Bus | orange |
| 463 W Douglas/Douglas MMTC - DT/MT | Bus | purple |
| 476 Hiram/Powder Springs - DT/MT | Bus | purple |
| 480 Acworth/Town Center - Downtown | Bus | teal |
| 483 Woodstock/Town Center - Midtown | Bus | teal |
| 484 Hickory Grove - Midtown | Bus | teal |
| 485 Hickory Grove - Downtown | Bus | teal |
| 490 Woodstock - Downtown | Bus | teal |
| 999 Test Route | Bus | white (no shape in feed) |
| 9999 Test Route NORTH OPS | Bus | white (no shape in feed) |
| 99999 Test Route for COBB Garage | Bus | white (no shape in feed) |
This feed has 96 stops.
List every stop
- Pryor St at Garnett St
- Central Ave at Garnett St
- Mitchell St at Peachtree St
- Ted Turner Dr (S) at Brotherton St
- Ted Turner Dr (N) at Brotherton St
- Peachtree Center Ave at Peachtree St
- Acworth Park and Ride
- BrandsMart Park and Ride
- Cumming Park and Ride
- Dacula Park and Ride (Hebron Church)
- Douglas MMTC Park and Ride
- East Conyers Park and Ride
- Hamilton Mill Park and Ride
- Hampton Park and Ride
- Hewatt Rd Park and Ride
- Hiram Park and Ride
- Jonesboro Park and Ride
- Mall of Georgia Park and Ride
- McDonough Park and Ride
- Newnan Park and Ride
- Panola Rd Park and Ride
- Powder Springs Park and Ride
- Riverdale Park and Ride
- Snellville Park and Ride
- Stockbridge Park and Ride
- Stone Mountain Park and Ride
- Sugarloaf Mills GRTA Park and Ride
- Town Center/Big Shanty Park and Ride
- Union City Park and Ride
- West Conyers Park and Ride (DT)
- West Douglas Park and Ride
- Woodstock Park and Ride
- Ivan Allen at Alexander St
- John Portman Blvd at Peachtree St
- Mitchell St at Forsyth St
- Pryor St at Mitchell St
- Ted Turner Dr at Mitchell St
- Wall St at Central Ave
- Williams St at Baker St
- Baker St at Williams St
- North Ave at Peachtree St
- Spring St at 17th St
- Spring St at 5th St
- Spring St just before Linden Ave
- Arts Center Station
- Peachtree-Dunwoody Rd at Concourse Pkwy
- Peachtree-Dunwoody Rd at Concourse Pkwy
- Perimeter Center at Perimeter Center Pkwy
- Perimeter Center West at Perimeter Center Pkwy
- Perimeter Center Pkwy Office Park (N)
- Perimeter Center Pkwy Office Park (S)
- Medical Center Station
- Sandy Springs Station
- Dunwoody Station
- Thornton Rd (N) at Bankhead Hwy
- Thornton Rd (S) at Maxham Rd
- Thornton Rd (N) at Maxham Rd
- Thornton Rd (N) at North Blairs Bridge Rd
- Thornton Rd (S) at North Blairs Bridge Rd
- Thornton Rd at Oak Ridge Rd
- Thornton Rd at Skyview Dr
- Thornton Rd at Westfork Blvd
- Lindbergh Center Station
- Baker St at Peachtree St
- Central Ave at Wall St
- John Portman Blvd at Courtland St
- Peachtree Center Ave at Auburn Ave
- Civic Center Station (NB)
- Civic Center Station (SB)
- West Peachtree St at Peachtree Pl
- West Peachtree St at 5th St
- North Ave Station
- West Peachtree St after 14 St
- Sugarloaf Mills GCT Park and Ride
- Baker St at Peachtree St
- 17th St at Spring St
- 17th St at Market St
- West Conyers Park and Ride (MT/Peri)
- Ponce De Leon Ave at W Peachtree St
- Thornton Rd (S) at Bankhead Hwy
- Hickory Grove Park and Ride
- Peachtree St at Five Points Station
- Washington St at MLK Jr Dr
- Central Ave at Mitchell St
- Courtland St at Auburn Ave
- Courtland St at Ellis St
- Courtland St at Gilmer St
- Forsyth St at MLK Jr Dr
- MLK Jr Dr at Peachtree St
- Central Ave at MLK Jr Dr
- Peachtree Center Ave at Andrew Young Int'l Blvd
- Peachtree Center Ave at John Wesley Dobbs Ave
- Peachtree St at Baker St
- Peachtree St at Renaissance Pkwy
- Ted Turner Dr at West Peachtree Pl
- West Peachtree St at 12th St
Over time
Overall score across the last 10 checks — unchanged since 2026-07-08.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-06-30 | 56.7 | first check |
| 2026-07-01 | 56.7 | no change |
| 2026-07-02 | 56.7 | no change |
| 2026-07-03 | 56.7 | no change |
| 2026-07-04 | 56.7 | no change |
| 2026-07-05 | 56.7 | no change |
| 2026-07-06 | 56.7 | no change |
| 2026-07-07 | 56.7 | no change |
| 2026-07-08 | 56.7 | no change |
| 2026-07-09 | 56.7 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
What changed in this feed
Overall grade and score held steady since 2026-07-08.
Same feed file as 2026-07-08; the published zip did not change.
Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.
Everything we checked
- Error1 instance
Invalid email (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'invalid_email' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Validator rule: invalid_email · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Error1 instance
Service data ended 1105 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.)
Agencies here usually clear this within about 1 week (based on 18 observed fixes).
Validator rule: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning96 instances
96 of 96 stops don't say whether a wheelchair user can board there.
Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.
Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)
Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning2 instances
Some files leave out fields that GTFS asks for but does not require.
Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners.
Fix: Review the flagged fields and fill in the ones your riders would use. (A field at a time; not urgent.)
Agencies here usually clear this within about 2 weeks (based on 8 observed fixes).
Validator rule: missing_recommended_field · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
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.)
Agencies here usually clear this within about 1 week (based on 61 observed fixes).
Validator rule: expired_calendar · 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.)
Agencies here usually clear this within about 1 week (based on 31 observed fixes).
Validator rule: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
Beyond the grade
Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.
11 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (419, 423, 426, 428, 430, and more).
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.
64 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Pryor St at Garnett St", "Central Ave at Garnett St", "Mitchell St at Peachtree St", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
NTD certification readiness Not ready
Resolve this before you certify on the D-10. 1 validator error to resolve. Service data expired 1105 days ago, so FTA would find the link out of date.
- Published Ready
- Published at a public URL.
- Valid Needs attention
- 1 validator error to resolve.
- Current Not ready
- Service data expired 1105 days ago, so FTA would find the link out of date.
- agency_id matches your NTD ID Not checked yet
- Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.
- shapes.txt covers your trips Ready
- All 197 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed and confirm it once a year. This box is a heads-up on whether yours looks ready; it is not the official sign-off.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). Aligning agency_id with your NTD ID lets the feed line up with your NTD record; the July 2025 final rule links the two on the P-50 form rather than requiring that feed change, and requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed is close to the conformance mark. 1 validator error to resolve. Service data expired 1105 days ago. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.
- Valid Not yet
- 1 validator error to resolve.
- Current Not yet
- Service data expired 1105 days ago.
- Accessible Not yet
- States wheelchair access on 0% of stops and 100% 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 1 validator error, the other thing Maps checks at onboarding; the findings below name each fix.
How this agency maps to the standards
A data-quality lens, not a compliance determination. Each category shows this feed's score and the standards it relates to: the FTA National Transit Database GTFS requirement, the MobilityData grading scheme, and the Google Transit gate. Read the full standards crosswalk.
- Correctness 76 / 100
- GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading: stop locations, route names and colors. Google Transit: a feed must pass validation to stay in Maps.
- Freshness 0 / 100
- The FTA National Transit Database expectation of a valid, current feed. Google Transit: an expired calendar drops the agency from Maps.
- Rider experience 75 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading: stop names and headsigns.
- Realtime quality Not yet published
- GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.
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/xpress-1118/2026-07-09.json and never overwritten, pinning the grade, category scores, rubric version, validator version, and the scored feed's sha256 as they stood on 2026-07-09. Use it in a board packet, an NTD narrative, or a research citation instead of linking the live page, whose content will differ on your next visit.
Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.