Feed status · checked 2026-08-01
Chittenden County Transportation Authority (CCTA)
Based on the feed this agency publishes
Service mode Bus
unchanged since 2026-07-31
Catalogued in Vermont.
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 80 minutes ago; last changed 17 days ago.
Measured 3 of 4 score categories from the agency's own feed.
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 agency's own URL.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
Top things to fix
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
1177 of 1177 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 in its category
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
893 of 893 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the bus itself can take them.
⏱ A default or per-trip field in your export.worth about +15 points in its category
Remove retired stops from the export, or add them back to the trips that should serve them.Likely your export tool
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.
⏱ A review pass in your scheduling software.worth about +8 points in its category
Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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
- 1177 of 1177 stops don't say whether a wheelchair user can board there.
- Next action
- Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.
- 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
- 893 of 893 trips don't say whether the vehicle is wheelchair accessible.
- Next action
- Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
- 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
- Some stops exist in the feed but no trip ever stops at them.
- Next action
- Remove retired stops from the export, or add them back to the trips that should serve them.
- 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.
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. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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.
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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.
Remove retired stops from the export, or add them back to the trips that should serve them. · Read the fix guide
Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.
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 61 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
- Fare information is published using GTFS Fares v1.
- 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 Trillium a fix request
This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. Each fix names the validator notice and a guide link.
Score by category
The MobilityData validator flagged 5 kinds of issue across 704 instances (0 error, 656 warning, 48 informational).
Service data covers the next 61 days.
0% of stops state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
3 accessibility depth signals
8 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 96, 778, 5, 6, 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.
158 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Northern Lights/downhill", "Northern Lights/uphill", "Rt 302 and Richardson Rd", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
This feed models stations or entrances but has no pathways.txt and levels.txt.
Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.
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.
Fares are applied to trips.
This agency publishes realtime, but the feed needs an access key we don't have 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 1177 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.
- 16 (teal)
- 19 (teal)
- 20 (teal)
- 1 (red)
- 7 (pink)
- 2 (blue)
- 6 (teal)
- 5 (green)
- 9 (green)
- 8 (yellow)
- 11 (pink)
- 86 (gray)
- 96 (gray)
- 756 (green)
- 778 (teal)
- 4 (orange)
| Route | Type | Line color |
|---|---|---|
| 16 Hannaford Tuesday Special | Bus | teal |
| 19 Price Chopper | Bus | teal |
| 20 Price Chopper | Bus | teal |
| 1 Williston | Bus | red |
| 7 North Avenue | Bus | pink |
| 2 Essex Junction | Bus | blue |
| 6 Shelburne Road | Bus | teal |
| 5 Pine Street | Bus | green |
| 9 Winooski | Bus | green |
| 8 City Loop | Bus | yellow |
| 11 City Connector | Bus | pink |
| 86 Montpelier LINK Express | Bus | gray |
| 96 Franklin County Commuter | Bus | gray |
| 109 Price Chopper Shopping Shuttle | Bus | brown (no shape in feed) |
| 334 Integrated Arts Academy, Edmunds, Champlain Elementary | Bus | teal (no shape in feed) |
| 336 Hunt Middle School, Flynn Elementary, CP Smith Elementary | Bus | teal (no shape in feed) |
| 342 CP Smith Elementary Flynn Elementary Hunt Middle School | Bus | teal (no shape in feed) |
| 344 Champlain/Edmunds | Bus | teal (no shape in feed) |
| 348 Champlain | Bus | teal (no shape in feed) |
| 349 Hunt/BHS | Bus | teal (no shape in feed) |
| 326 Edmunds/Integrated Arts Academy | Bus | teal (no shape in feed) |
| 756 South End Circulator Sunday | Bus | green |
| 778 North End Circulator Sunday | Bus | teal |
| 4 Essex Center | Bus | orange |
List every stop
- Champlain School Parking Lot
- GMT-Berlin office
- Northern Lights/downhill
- Northern Lights/uphill
- Rt 302 and Richardson Rd
- Brookside II Apartments
- Mad River Valley - Visitor Ctr
- Route 302 at Knoll Motel
- Waterbury State Complex
- Dept. of Public Safety
- Granite City Primary Care
- Barre Health Center
- Berlin Street at S Vine Street
- UVM at Tilley Drive
- UVM Dental Clinic
- Adirondack Circle
- Academy Street
- Essex Experience
- Williston Road at Mills Avenue
- Northgate
- Pine St at Hickock St
- Northfield Senior Center
- Main Street at Crestview Road
- Main Street and Educational Drive
- N Champlain Street and Peru Street
- Jericho Road and Allen Martin Drive
- Jericho Road and Allen Martin Drive
- Downtown Transit Center - A, C, E, G, I
- Downtown Transit Center - B, D, F, H, J
- Downtown Transit Center - Spot P
- Downtown Transit Center - Spot O
- Downtown Transit Center - Spot K
- Downtown Transit Center - Spot L
- Downtown Transit Center - Spot Q
- Downtown Transit Center - Spot R
- Downtown Transit Center - Spot S
- 194 St Paul Street (Eagles Landing)
- Pinnacle Sports
- Rt. 108 at Opposite Cady Hill Lodge North
- Apple Tree/uphill
- Pond Street at Depot Street
- West Branch Apt/downhill
- Baggy Knees Plaza/uphill
- Rt. 108 at Opposite Cady Hill Lodge South
- Rt. 108 at Cady Hill Lodge South
- Rt. 108 at Cady Hill Lodge North
- Route 108 at M&T Bank
- Sun & Ski Resort/downhill
- Piecasso/downhill
- Darkside/uphill
- Stowe Motel/downhill
- Route 108 at Opposite Toll House
- Route 108 at Toll House
- Mt. Glen/uphill
- Rt. 108 at Main St
- Montpelier Transit Center
- Season's Pass
- South Village
- Wild Fire
- Lower Sugarbush Club (inbound)
- Sugarbush Access Rd. at Christmas Tree Rd.
- Yestermorrow (outbound)
- Yestermorrow (inbound)
- American Flatbread
- M.R. Green/Northfield Bank
- M. R. Green/Taste Place
- Lawson’s/Movie Theater
- Old County Road (across from Health Center)
- Weathertop
- Pindari
- Mad River Barn
- Horseshoe Road
- Creek Farm Plaza
- MRV Senior Center
- Washington Street at Perry Street (McFarland State Office Building)
- Washington Street at City Hall Park
- Berlin Kohl's
- Downstreet Apts
- Downtown BHS
- Industrial Avenue at VT 2A
- Price Chopper
- Berlin St. at 65 Berlin St.
- Vtrans and Airport Road
- Hill St. at S. Main St
- Mountain Haus Uphill
- Mountain Haus Downhill
- Pine Street at Baird Park
- Mountain Rd at PHIT Performance
- Mountain Rd. at Opposite PHIT Performance
- Washington County, VT, USA
- Chittenden County, VT, USA
- Grand Isle, VT, USA
- Barre, VT, USA
- Montpelier, VT, USA
- Burlington, VT, USA
- 1537 US 302
- Stowe Events Field Parking Lot
- Route 108 at Cape Cod Rd.
- Route 108 at Opposite Cape Cod Rd.
- Route 100 at Village Square
- Route 100 at Opposite Village Square
- Route 100 at Opposite Carroll Rd.
- Sugarbush Access Rd. at Opposite Christmas Tree Rd.
- Sugarbush Access Rd. at Wheeler Brook Rd.
- Sugarbush Access Rd. at Opposite Wheeler Brook Rd.
- Stowe Cross Country Center
- E Allen Street at Hillside Park
- Shelburne Road at Harrington Ave
- Route 108 at Little River Inn
- Rt.100 at Opp Green Goddess Cafe
- Mansfield Base at Lot D
- Williston Park & Ride
- Gauthier Drive at Keurig Green Mountain
- Route 15 at Packard Rd.
- Route 15 Opposite Packard Rd.
- Meadowland Drive at Dynapower
- Opposite Horseshoe Rd.
- Sugarbush Administrative Office
- Club Sugarbush North
- German Flats Rd. at Sugarbush Inn
- German Flats Rd. at Opposite Sugarbush Inn
- German Flats Rd. at Hamilton House Drive
- Rt. 100 at Mac's Market
- Opposite Boys & Girls Club
- Swanson Inn
- Club Sugarbush South
- Champlain Parkway at Home Ave
- Champlain Parkway at Flynn Ave
- Pine Street at Kilburn Street
- Waterbury State Complex at State Drive South Entrance
- Lyman C. Hunt Middle School
- Shelburne Road at Opposite Marion St
- Shelburne Road at Opposite Prospect Parkway
- Pearl Street at Opposite North Champlain Street
- Queen City Park Rd. at 733 Queen City Park Rd.
- North Ave at Burlington Police Department
- South Burlington City Center
- Hinesburg Road at Prouty Parkway
- Hinesburg Road at Wright Court
- Hinesburg Road at Opposite Simpson Court
- Hinesburg Road at Opposite Iby Street
- Market Street at Garden Street
- Market Street at Hinesburg Road
- Market Street at Garden Street
- Market Street at Hinesburg Road
- Saint Albans Park and Ride
- Route 302 at Overlake Drive
- Hinesburg Road at Williston Road
- 620 Hinesburg Rd
- Creek Farm Plaza
- River Street at Main Street
- US 7 at Opposite Lake Road
- US 7 at Opposite Kilburn Road
- River Street Park
- River Street at Opposite Villemaire Lane
- 259 US 7-Milton Square
- Fairfield Street at Northwestern Medical Center
- Fairfield Street at opposite Northwestern Medical Center
- Berlin Street at Valley View Road
- Berlin Street at Addison Drive
- Austin Drive at Ledgewood Circle
- South Cove Road at Austin Drive
- Stanbury Road at Opposite Woodbury Road
- Opposite MRV Welcome Center/Chamber Comm.
- MRV Professional Center
- Weathertop Inn at Number 9 Rd
- Mt. Ellen Parking Lot
- The SugarTree (Sugarbush Admin Office)
- Route 302 at Highland Ave
- South Burlington City Center
- Depot Street at Thomas Lane
- 5138 Shelburne Road
- Route 302 at Cody Chevrolet
- Route 302 at Salon 42
- 652-654 Granger Road
- 10 North Champlain Street
- 146 Colchester Avenue
- Main Street at Pine Street
- Main Street at Church Street
- Lakeside Avenue at Champlain Parkway
- Champlain Parkway at Sears Lane
- Shelburne Road at Hoover Street
- West Spring Street at Mallets Bay Avenue
- Montpelier Transit Center
- S. Winooski Avenue at Bank Street
- Main Street at S. Winooski
- Main Street at S. Union Street
- Main Street at S. Willard Street
- Main Street at S. Prospect Street
- University Heights
- Dorset Street at Williston Road
- Dorset Street at Peoples United Bank
- University Mall
- Dorset Street at Brookwood Drive
- Dorset Street at The Pines
- Dorset Street at Fire Station
- Kennedy Drive at Dorset Street
- Kennedy Drive at Twin Oaks Terrace
- Kennedy Drive at Timber Lane
- Williston Road at Heath Street
- Williston Road at Davis Parkway
- Williston Road at Hayden Parkway
- Williston Road at Elsom Parkway
- Williston Road at Victoria Drive
- Williston Road at Mills Avenue
- Airport Drive at Airport Entrance
- Burlington International Airport
- White Street at Dumont Avenue
- White Street at Pump Lane
- White Street at Airport Parkway
- White Street at Opposite Myers Court
- White Street at Maplewood Drive
- White Street at Charles Street
- White Street at Patchen Road
- Patchen Road at Williston Road
- Hinesburg Road at Williston Road
- Hinesburg Road at Village Green Drive
- Hinesburg Road at Iby Street
- Hinesburg Road at Simpson Court
- Hinesburg Road at Sunset Avenue
- Hinesburg Road at Opposite Prouty Parkway
- Hinesburg Road at Kennedy Drive
- Kennedy Drive at Manor Woods
- Kennedy Drive at South Burlington High School
- Dorset Street at South Burlington High School
- Dorset Street at San Remo Drive
- Dorset Street at Champlain Oil
- Dorset Street at San Remo Drive
- Dorset Street at Barnes & Noble
- Williston Road at Sheraton Hotel
- University Heights
- Main Street at S. Willard Street
- Main Street at S Union Street
- Main Street at Church Street
- Main Street at Pine Street
- Battery Street at College Street
- Battery Street at Cherry Street
- S Union Street at Adams Street
- S Union Street at Spruce Street
- S Union Street at Howard Street
- S Union Street at St Paul Street
- Shelburne Road at Gove Court
- Shelburne Road at Opposite Hoover Street
- Shelburne Road at Birchcliff Parkway
- Shelburne Road at Burlington Subaru
- Shelburne Road at Ferguson Avenue
- Shelburne Road at Lyman Avenue
- Shelburne Road at Scarff Avenue
- Shelburne Road at Home Avenue
- Shelburne Road at Queen City Parkway
- and 927 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 | 81.1 | first check |
| 2026-07-30 | 81.1 | no change |
| 2026-07-31 | 81.1 | no change |
| 2026-08-01 | 81.1 | 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-31.
Same feed file as 2026-07-31; 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
10 findings, ordered by severity.
Show every finding
- Warning1177 instances
1177 of 1177 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)
- Warning893 instances
893 of 893 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)
- Warning655 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning28 instances
28 of 893 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 (opens GTFS Best Practices on an external site)
- 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
This feed describes flexible (demand-responsive) service but has no booking_rules.txt.
Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.
Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)
Finding code: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Warning1 instance
This feed models stations or entrances but has no pathways.txt.
Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.
Fix: Add pathways.txt connecting entrances, platforms, and any elevators, with a level for each. (Worth it for multi-level or large stations; flat stops don't need it.)
Finding code: scorecard_station_no_pathways · Read the fix guide · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)
- Info34 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 · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Info8 instances
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 (opens the validator rules on an external site)
- Info6 instances
Some service dates fall outside the date window set in feed_info.txt.
feed_info.txt should span every day your service runs, so apps know when the data applies.
Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)
Finding code: service_window_outside_feed_period · 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.
Flex zones are published but no booking_rules.txt is present.
Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).
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 61 days.
- agency_id provided Ready
- agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.
- agency_id equals your NTD ID (optional) Not checked yet
- This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.
- shapes.txt covers your trips Ready
- All 893 trips have a shape in shapes.txt.
In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.
A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.
Conformance mark Not yet
This feed is close to the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 61 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.
- 655 of 1176 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 61 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 86 / 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 60 / 100
- GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
- Realtime quality Access needed to measure
- 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/chittenden-county-transportation-authority-ccta/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.