GTFS Scorecard
← All agencies

Feed status · checked 2026-10-20

Charlottesville Area Transit (CAT)

Based on the official feed source on file

Service mode Bus

70.6 / 100

First scorecard for this agency

Cataloged in Virginia.

Covers 85 daysAccessibility gapsRealtime not yet published

Source feed: https://apps.charlottesville.gov/publicfiles/GTFS.zip Version history on the Mobility Database

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.4, validator 8.0.1.

Measured 3 of 4 score categories from the official feed URL on file.

How we measured this

Confidence in this measurement: medium.

  • Realtime quality was not measured this run. It does not count against the grade.
  • The feed was downloaded from the official feed URL on file.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

About this feed

Charlottesville Area Transit (CAT)’s published feed lists 12 bus routes, 1,034 scheduled trips and 337 stops. Its service dates run from 2024-11-09 through 2027-01-13.

Top things to fix

Fix 01

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

337 of 337 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.

Fixing this covers all 337 stops in the feed.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category

Fix 02

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

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

Fixing this covers all 1,034 trips in the feed.

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

Fix 03

Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead.

The feed contains no fare information. Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

This one is about the feed as a whole, so there is no share of it to count.

⏱ A small file for most flat-fare systems.worth about +15 points in its category

Riders and need behind these fixes

  • No ridership snapshot was on hand when this was built, so annual rider-trips are not known.
  • Virginia as a whole measures lower on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-10-19.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

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.

Finding
Fix 01 in Top things to fix: its feed evidence and the requested 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. Fix 01 · Read the fix guide for scorecard_wheelchair_boarding_unknown

    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. Fix 02 · Read the fix guide for scorecard_wheelchair_accessible_unknown

    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. Fix 03 · Read the fix guide for scorecard_no_fare_data

    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 85 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
Realtime-feed availability and live-arrival coverage are not known from this scorecard.

Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.

Send your vendor a fix request

You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.

Score by category

Correctness77.5 / 100

The MobilityData validator flagged 5 kinds of issue across 133 instances (0 error, 130 warning, 3 informational).

Freshness100.0 / 100

Service data covers the next 85 days.

Rider experience37.4 / 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

  • 5 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (2, 3, 5, 7, T).

    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.

  • 292 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Emmet St at Central Grounds Garage", "Emmet St at Snyder Tennis Courts", "Alderman Rd at Stadium Rd", 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 337 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.

  • 1 (orange)
  • 10 (teal)
  • 11 (gray)
  • 2 (brown)
  • 3 (blue)
  • 4 (red)
  • 5 (brown)
  • 6 (yellow)
  • 7 (purple)
  • 8 (gray)
  • 9 (pink)
  • T (green)
Routes in Charlottesville Area Transit (CAT)'s feed
RouteTypeLine color
1 PVCC/Woolen MillsBusorange
10 PantopsBusteal
11 Locust Ave/Rio RdBusgray
2 5th St StationBusbrown
3 Southwood/BelmontBusblue
4 Cherry Ave/Harris RdBusred
5 CommonwealthBusbrown
6 Ridge St/Prospect AveBusyellow
7 Emmet St/Seminole TrailBuspurple
8 Preston Ave/Emmit StBusgray
9 UVA Health/YMCABuspink
T TrolleyBusgreen
List every stop
  • Emmet St at Central Grounds Garage
  • Emmet St at Snyder Tennis Courts
  • Alderman Rd at Stadium Rd
  • E Water St at 3rd St
  • Water St at Omni
  • Ridge McIntire at Omni
  • W Main St at 5th St SW
  • W Main St at 4th St NW
  • W Main St at 8th St NW
  • W Main St at The Flats
  • W Main St at 11th St Westbound
  • W Main St at 11th St Eastbound
  • JPA at Cabell Hall
  • JPA at Montebello Cir
  • JPA at Shamrock Rd
  • W Main St at The Standard
  • JPA at UVA Hospital
  • JPA at Maury Ave
  • Maury Ave at Clark Ct
  • Alderman Rd at AFC
  • University Ave at The Women's Center
  • University Ave at The Rotunda
  • E Market St at 2nd St NE
  • E Market St at 5th St NE
  • E Market St at 10th St NE
  • JPA at Old Lynchburg Rd Southbound
  • JPA at Monte Vista Ave
  • JPA at Azalea Dr
  • Harris Rd at Willard Dr Eastbound
  • Cleveland Ave at JPA
  • W Market St at Old Preston Ave
  • Avon St at Garrett St
  • Bailey Rd at Prospect Ave Westbound
  • Prospect Ave at Greenstone Northbound
  • Cherry Ave at Cherry Ave Shopping
  • JPA at Brandon Ave
  • McCormick Rd at Chemistry Building
  • McCormick Rd at Garret Hall
  • Preston Ave at Madison Ave Southbound
  • JPA at Woodrow St
  • McCormick Rd at UVA Chapel
  • Avon St at Blenheim Ave
  • Avon St at Montrose Ave
  • 1st St at Elliott Ave Northbound
  • Avon St at Hinton Ave
  • Elliott Ave at Burnet St
  • Cherry Ave at 6th St Eastbound
  • Millmont St at USPS
  • Millmont St at Kroger
  • Chesapeake St at Riverview St
  • Monticello Ave at Tufton Ave
  • Fairway Ave at Meade Ave
  • Meade Ave at Caroline Ave
  • Monticello Ave Castalia St
  • E Market St at 18th St NE
  • Fairway Ave at Short 18th St
  • Fairway Ave at Arbor Cir
  • Monticello Ave at Elliott Ave
  • Locust Ave at Smith St Northbound
  • North Ave at Cottonwood Rd
  • Locust Ave at Sycamore St Southbound
  • Locust Ave at Hazel St Southbound
  • PVCC Dickinson Building
  • North Ave at Wilder Dr Eastbound
  • North Ave at Holmes Ave
  • Northeast Park Southbound
  • Calhoun St at Locust Ave
  • Southwood
  • St Clair Ave at Calhoun St
  • 5th St at Bailey Rd Southbound
  • Peartree Ln at St Clair Ave
  • Ridge St at Cherry Ave
  • Ridge St at Dice St Southbound
  • Preston Ave at Booker St
  • Four Seasons Dr at ACAC
  • Rio Rd at Charlottesville Rehab Eastbound
  • Commonwealth Dr at Westfield Rd Eastbound
  • Commonwealth Dr at Commonwealth Ct Northbound
  • Commonwealth Dr at Peyton Dr
  • Four Seasons Dr at Woodlake Dr Northbound
  • Four Seasons Dr at Tennis Dr Northbound
  • Georgetown Rd at Hydraulic Rd Northbound
  • Commonwealth Dr at Northwest Dr Northbound
  • Georgetown Rd at Hessian Hills Way
  • BRSC at Arlington Northbound
  • Barracks Rd at Cedars Ct Northbound
  • Commonwealth Dr at Hydraulic Rd Northbound
  • Georgetown Rd at Court Pl
  • Georgetown Rd at Inglewood Dr Northbound
  • Berkmar Dr at SPCA Southbound
  • Barracks Rd at Bennington Rd
  • Berkmar Dr at UVA Credit Union
  • BRSC at Arlington Southbound
  • Berkmar Dr at SPCA Northbound
  • Sam's Club
  • Walmart
  • Rio Rd at Northside Library
  • Rio Rd at Berkmar Cir
  • E High St at Grove Ave Westbound
  • E High St at Meade Ave
  • E High St at Grove Ave Eastbound
  • Rose Hill Dr at Henry Ave Northbound
  • Rose Hill Dr at Henry Ave Southbound
  • Rose Hill Dr at Dale Ave Southbound
  • Rose Hill Dr at Health Department Southbound
  • Social Security Administration
  • Martha Jefferson Outpatient
  • Del Mar Dr at Oakleaf Ln Westbound
  • Rose Hill Dr at Health Department Northbound
  • Rose Hill Dr at Dale Ave Northbound
  • Rose Hill Dr at Rivanna Ave
  • 10th St at Grady Ave Southbound
  • Ridge St at Hartman's Mill Rd Southbound
  • Preston Ave at Madison Ave Northbound
  • Barracks Rd at Howard Dr
  • Brookwood Dr at Ridge St Northbound
  • Pantops Food Lion
  • Preston Ave at Washington Park
  • E High St at Stewart St
  • Barracks Rd at CVS
  • Ridge St at Barksdale St Northbound
  • Preston Ave at Harris St Westbound
  • Monticello Ave at 6th St Eastbound
  • Monticello Ave at 2nd St Eastbound
  • Preston Ave at Region 10
  • E High St at Hazel St Westbound
  • 1st St at Elliott Ave Southbound
  • Preston Ave at Harris St Eastbound
  • Preston Ave at Rosser Ave
  • Hillsdale Dr at Seminole Square
  • Barracks Rd at Cedars Ct Southbound
  • Preston Ave at Rugby Ave Southbound
  • Barracks Rd at Surrey Rd
  • Hydraulic Rd at Turtle Creek Rd Northbound
  • Georgetown Rd at Hydraulic Rd Southbound
  • Commonwealth Dr at Hydraulic Rd Southbound
  • Commonwealth Dr at Trophy Chase
  • Commonwealth Dr at Commonwealth Ct Westbound
  • Commonwealth Dr at Westfield Rd Westbound
  • Commonwealth Dr at Commonwealth Cir
  • Cherry Ave at Rockcreek Rd
  • Cherry Ave at Hanover St Northbound
  • Cherry Ave at 10th St Eastbound
  • Four Seasons Dr at ACAC Southbound
  • Four Seasons Dr at Woodlake Dr Southbound
  • Berkmar Dr at Barry Ter
  • Georgetown Rd at Terrell Rd
  • Four Seasons Dr at Tennis Dr Southbound
  • Commonwealth Dr at Northwest Dr Southbound
  • PVCC at The Main Bldg
  • Grove Rd at Meadowbrook Heights Eastbound
  • Veterans Administration
  • Georgetown Rd at Barracks Rd
  • Preston Ave at Cabell Ave Southbound
  • Preston Ave at Cabell Ave Northbound
  • 5th St at Holiday Inn
  • 5th St at Sleep Inn
  • Bainbridge St at Monticello Rd
  • Cherry Ave at Highland Ave
  • Cherry Ave at Shamrock Rd Westbound
  • Carlton Ave at Carlton Rd
  • Hinton Ave at Meridian St
  • 5th St at Bent Creed Rd
  • 5th St at Bailey Rd Northbound
  • Ridge St at Elliott Ave
  • Ridge St at Dice St Northbound
  • 5th St at County Office
  • Altavista Ave
  • Altavista Ave at Rialto St
  • Belmont Park
  • Cherry Ave at 6th St Westbound
  • Cherry Ave at IRC
  • Avon St at Druid Ave
  • 10th St at Page St Southbound
  • Rio Rd at Putt Putt
  • Crescent Hall
  • Hillsdale Dr at Walden Ct
  • Emmet St at Rothery Rd
  • Emmet St at Lambeth Northbound
  • Emmet St at Massie Rd
  • Emmet St at Morton Dr
  • E High St at Locust Ave
  • E High St at 9 1/2 St NE
  • Hydraulic Rd at Emmet St
  • Kroger at Hydraulic Rd
  • Emmet St at Angus Rd
  • Hillsdale Dr at Greenbrier Southbound
  • Mall Dr at Hillsdale Dr
  • Hillsdale DR at JABA Southbound
  • Hillsdale Dr at Branchlands Southbound
  • Hillsdale Dr at Branchlands Northbound
  • Hillsdale Dr at Greenbrier Northbound
  • BRSC Kroger
  • Emmet St at Ruffner Hall
  • JPA at Pinn Hall
  • Locust Ave at Watson Ave
  • Emmet St at Sprigg Ln
  • Mall Dr at Royal Ct
  • Hillsdale Dr at Exeter Ct
  • Rio Rd at Greenbrier Dr Southbound
  • Rio Rd at Greenbrier Dr Northbound
  • Locust Ave at Smith St Southbound
  • Rio Rd at Treesdale Apt
  • North Ave at Glendale Rd
  • Locust Ave at Hazel St Northbound
  • Rio Rd at John Warner Pkwy
  • Rio Rd at CATEC
  • Sentara Martha Jefferson Hospital
  • Wilton Farms
  • The Downtown Mall
  • Grove Rd at Meadowbrook Heights Westbound
  • Downtown Transit Station
  • Locust Ave at Long St
  • 9th St at Buford Southbound
  • Locust Ave at Sycamore St Northbound
  • Cherry Ave at Hanover St Southbound
  • Cherry Ave at Rainier Rd
  • Chesapeake St at 18th St NE
  • Stony Point Rd at Winding River Ln
  • Rio Rd at Berkmar Dr
  • Gentry Ln at Walker Upper Northbound
  • Gentry Ln at Walker Upper Southbound
  • Cherry Ave at Shamrock Rd Eastbound
  • Northeast Park Northbound
  • 5th St at Old Lynchburg Rd
  • Avemore Apartments
  • St Clair Ave at St George Ave
  • North Ave at Wilder Dr Westbound
  • Park St at Beechwood Garden
  • St Clair Ave at Smith St
  • Rio Rd at Pen Park Ln
  • Martha Jefferson Dr at State Farm Blvd
  • DMV
  • Pantops Giant
  • E High St at Hazel St Eastbound
  • Riverside Ave Northbound
  • Riverside Ave at Riverbluff Cir
  • Riverside Ave
  • Chesapeake St at Riverview St
  • Chesapeake St at Meade Park
  • Little High St at 12th St Westbound
  • Little High St at 12th St Eastbound
  • Little High St at 11th St Eastbound
  • Little High St at 11th St Westbound
  • Rives St at Carlton Ave
  • Rives St at Hampton St
  • Rives St at Rives Park
  • Monticello Rd at Linden Ave Southbound
  • Monticello Ave at Blenheim Ave
  • Monticello Ave at 6th St Westbound
  • and 87 more (see the full list on the map or in the GeoJSON)

Over time

This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.

Everything we checked

9 findings, ordered by severity.

Show every finding
  • Warning1034 instances

    1034 of 1034 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 for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference

  • Warning337 instances

    337 of 337 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 for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference

  • Warning104 instances

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

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

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

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

  • Warning24 instances

    Some stops exist in the feed but no trip ever stops at them.

    Riders may walk to a stop where no bus is scheduled to arrive.

    Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)

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

  • 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 for missing_feed_contact_email_and_url · See MobilityData GTFS Validator rules

  • Warning1 instance

    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 for mixed_case_recommended_field · 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 for scorecard_no_fare_data · See GTFS Best Practices

  • Info3 instances

    Some files contain columns that are not part of the GTFS spec.

    Harmless to riders, but apps ignore these columns and they can hide typos in real column names.

    Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)

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

  • Info1 instance

    feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

    App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

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

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 85 days.
agency_id provided Ready
agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
agency_id equals your NTD ID (optional) Different (allowed)
Your feed's agency_id is 1; your National Transit Database ID is 30036. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score. Confirm that P-50 crosswalks agency_id 1 to NTD ID 30036, and keep the feed value stable. Do not change it solely to make the two values equal.
shapes.txt covers your trips Ready
All 1034 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

One requirement remains for this feed to earn 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 85 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.

Can riders use it?

Checks beyond structural validation: places where the feed is valid but a rider still could not travel.

  • 24 of 337 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.

These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.

Clears the Google and Apple Maps four-week coverage bar. This feed has 85 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 78 / 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 37 / 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.

Part of the Virginia portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Virginia

Other scorecards in Virginia, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

Charlottesville Area Transit (CAT): GTFS feed quality grade C, 70.6 of 100, checked 2026-10-20. GTFS 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/charlottesville-area-transit-cat/2026-10-20.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-10-20. 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.