Feed status · checked 2026-11-21
Clinton County Public Transit (CCPT)
Based on the feed source on file; publisher ownership is not verified
Service mode Bus
unchanged since 2026-11-20
Cataloged in New York.
The grade is not a count of validator errors. It also weighs freshness and rider information. How the grade works
Feed file
Feed URL: https://s3.amazonaws.com/datatools-511ny/public/Clinton_County_Public_Transit.zip
Watch this feed for free: we email you before it expires or when its grade drops.
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
135 of 135 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 135 stops in the feed.
⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category
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
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.
This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.
⏱ A review pass in your scheduling software.worth about +8 points in its category
Riders and need behind these fixes
- This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
- New York as a whole measures moderate 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-11-02.
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
- Finding
- Fix 02 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
- Finding
- Fix 03 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.
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. See this feed's finding-clearance log.
Fix 02 · 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. See this feed's finding-clearance log.
Fix 03 · Read the fix guide for stop_without_stop_time
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. See this feed's finding-clearance log.
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 282 days.
- Published accessibility data
- Accessibility information is stated for 0% of stops and 71.4% 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.
About this feed
Looking for times or routes? This page checks the data file that trip planners use. For schedules, use the agency's own website or a trip planner.
Clinton County Public Transit (CCPT)’s published feed lists 10 bus routes, 98 scheduled trips and 135 stops. Its service dates run from 2026-10-01 through 2027-08-30. The published file last changed on 2026-10-21.
Score by category
The MobilityData validator flagged 9 kinds of issue across 153 instances (0 error, 146 warning, 7 informational).
Service data covers the next 282 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 not published.
0% of stops state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.
1 accessibility depth signal
18 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("A&W/ Chase/ Mobil", "Broad St Commons", "80 Sharron Ave Plaza", and more).
Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.
Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, not verified physical usability.
Not scored yet. Nothing here counts against the grade.
Routes and stops
Each route is drawn once, using the longest shape its trips follow; stops are the dots.
This feed has 135 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.
- Keeseville/AuSable (red)
- Mooers (green)
- Champlain/Rouses Point (yellow)
- Clayburg (green)
- Ellenburg (teal)
- Express Shuttle (white)
- Lyon Mountain (purple)
- North-West City (gray)
- South-West City (black)
- SUNY Shuttle (red)
| Route | Type | Line color |
|---|---|---|
| Keeseville/AuSable Keeseville/AuSable - CCPT | Bus | red |
| Mooers Mooers - CCPT | Bus | green |
| Champlain/Rouses Point Champlain/Rouses Point - CCPT | Bus | yellow |
| Clayburg Clayburg - CCPT | Bus | green |
| Ellenburg Ellenburg - CCPT | Bus | teal |
| Express Shuttle Express Shuttle - CCPT | Bus | white |
| Lyon Mountain Lyon Mountain - CCPT | Bus | purple |
| North-West City North-West City - CCPT | Bus | gray |
| South-West City South-West City - CCPT | Bus | black |
| SUNY Shuttle SUNY Shuttle - CCPT | Bus | red |
List every stop
- Dollar General (West Chazy)
- Mooers Town Office
- Connecticut Avenue & Peaceful Way - UR
- College Suites
- The Village Suites - Flag
- South Catherine Street & Village Suites - Flag
- South Catherine Street Across from Renaissance Village - Flag
- Momot Elementary School
- Momot Elementary School - UR
- Seton Catholic Central
- Seton Catholic Central - UR
- MHAB
- ETS / One Work Source
- Yando's Big M
- Southside Grocery - South Peru Street
- South Peru Street - Across from Southside Grocery
- Lakeview Towers / Russell Barnard
- Big Lots
- Kinney Drugs
- Boynton Avenue in Front of Kinney Drugs - Flag
- Broad Street & Durkee St
- Top's Market
- Beekman Towers
- Meadowbrook Healthcare
- ALDI's - UR
- North Woods Apartments
- Broad St Commons
- Consumer Square
- Military Recruitment Center
- UVM-CVPH Health Plaza / Hudson Head Waters
- YMCA / Library
- YMCA on the Oval- Flag
- St. John's Church
- Hannaford - UR
- Clinton Correctional Facility
- Mountain Top Housing
- B's Country Quick Stop
- Across B's County Quick Stop- R
- Behind Starbucks - UR
- Diamond Comics - Flag
- Champlain Centre Mall (Target)
- Cody's Store - Flag
- Across from Cody's Store - Flag
- Altona Post Office
- Art Lefevre Senior Housing - UR
- Cadyville Fire Station - Flag
- Across from Cadyville Fire Station - Flag
- Route 9 in Front of Chazy Rural School - Flag
- 2nd St & Center St
- Mr. Modular
- Clinton County Government Center
- Chazy Post Office
- Price Chopper (Champlain)
- Dollar General (Rouses Point)
- Chazy Stewart's - UR
- Across from AuSable Point Entrance - Flag
- AuSable Point Entrance
- Champlain Valley Family Center (CVFC)
- PFCU Keeseville
- AuSable Forks Post Office
- Villa Motel
- Across from Villa Motel
- Stewarts Rouses Point
- Mobile Station/Dunkin (Route 9)
- Roderick Rock Senior Housing - UR
- One Stop Shop (Northern Cakes)
- Maplefields (Rt3, Saranac)
- Angell College Center
- Russell Barnard Apts
- Across from Tara Lane - Flag
- Saranac Country Store
- Family Dollar (Plattsburgh)
- Stonehelm Motel
- Behavioral Health Services North (BHSN)
- AuSable Chasm - Flag
- Market 32
- Stewarts Dannemora
- Across from Dannemora Prison
- Institute for Advanced Manufacturing
- Westwood Drive - UR
- Morrisonville Post Office
- A&W/ Chase/ Mobil
- UVM-CVPH (Hospital)
- Northern Adirondack Central School
- Senior Citizens Council
- Kinney Drugs - West (off Military Turnpike) - UR
- Sailly Avenue - Flag
- Plattsburgh Medical Care - UR
- Clinton County Mental Health
- Maplefields (Military Turnpike)
- Elm St./ Church St.
- Skyway Plaza
- DeGrandpre Way Medical Offices - UR
- Clinton County Fairgrounds
- Hannaford
- Macdonough Hall
- Plattsburgh High School
- Across from Plattsburgh High School - Flag
- Lakeview Towers
- Wal-Mart Plaza
- Route 374 - Across from Lyon Mountain Post Office - Flag
- Hammond Ln
- Cumberland 12
- Clinton County Sheriff's Office
- Gus's Red Hots
- Lot Between PFCU and Adk Hardware
- Plattsburgh International Airport - UR
- Behavioral Health Services North (BHSN)
- A N Deringer
- Ganienkeh Laundromat & Store
- Maplefields Dannemora - UR
- Eye Care for the ADKs
- Champlain Valley Industries
- Village Liquor Shoppe
- Senior Citizen's Center
- Lyon Mountain Post Office
- St Joseph's Outreach
- Plattsburgh Plaza A-Plus Nails
- Plattsburgh Plaza Family Dollar - UR
- Anchorage Motel
- Shell Station Route 3 - UR
- Plattsburgh Plaza A-Plus Nails - UR
- Lake Country Village - UR
- Mobil Station (Spellman Road)
- West Chazy Post Office
- Commutair - UR
- Beekmantown Fire Dept
- Champlain Family Health (Hudson Headwaters) - UR
- 3rd Street Lyon Mountain
- 80 Sharron Ave Plaza
- Mooers Post Office
- Champlain Valley Family Center (CVFC)
- ALDI
- Mooers Free Library
- Across from Morrisonville Post Office
Over time
Overall score across the last 13 checks — unchanged since 2026-11-20.
Show the numbers
| Check | Score | Change |
|---|---|---|
| 2026-11-09 | 64.3 | first check |
| 2026-11-10 | 64.3 | no change |
| 2026-11-11 | 64.3 | no change |
| 2026-11-12 | 64.3 | no change |
| 2026-11-13 | 64.3 | no change |
| 2026-11-14 | 64.3 | no change |
| 2026-11-15 | 64.3 | no change |
| 2026-11-16 | 64.3 | no change |
| 2026-11-17 | 64.3 | no change |
| 2026-11-18 | 64.3 | no change |
| 2026-11-19 | 64.3 | no change |
| 2026-11-20 | 64.3 | no change |
| 2026-11-21 | 64.3 | no change |
What changed since your last check
- Correctness no change
- Freshness no change
- Rider experience no change
Feed history
Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.
| Checked | Published file | Service dates through | Grade at the time |
|---|---|---|---|
| 2026-11-09 to 2026-11-21 (13 checks) | 7bc5ce65b396 | 2027-08-30 | Current rubric: see the trend above |
| 2026-10-21 to 2026-11-06 (17 checks) | 7bc5ce65b396 | 2027-08-30 | D, 64.3 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade |
| 2026-10-20 | a7718b44eb83 | 2027-08-30 | D, 64.8 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade |
| 2026-10-14 to 2026-10-19 (6 checks) | de5c4346ac3f | 2026-05-31 | F, 20.6 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade |
| 2026-10-13 | 4bb0b0267758 | 2026-05-31 | F, 33.1 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade |
| 2026-10-02 to 2026-10-12 (11 checks) | d2dbe9125136 | 2026-05-31 | F, 35.3 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-25 to 2026-10-01 (65 checks) | d2dbe9125136 | 2026-05-31 | F, 35.3 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade |
| 2026-07-14 to 2026-07-24 (9 checks) | d2dbe9125136 | 2026-05-31 | F, 35.3 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade |
| 2026-06-19 to 2026-07-13 (25 checks) | d2dbe9125136 | 2026-05-31 | F, 35.3 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade |
Everything we checked
14 findings, ordered by severity.
Show every finding
- Warning135 instances
135 of 135 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 (opens the GTFS Schedule reference on an external site)
- Warning79 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 (opens the validator rules on an external site)
- Warning40 instances
Some rows in stop_times.txt leave the timepoint column blank.
That column says whether a time is a real checkpoint or an estimate. Blank leaves apps guessing, and they may show your estimates as promises.
Fix: Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1. (Usually one export setting.)
Finding code: missing_timepoint_value · Read the fix guide for missing_timepoint_value · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning31 instances
31 of 98 trips have no headsign, the text that tells riders where the bus is going. A trip counts when it has trip_headsign or a stop_headsign at every stop.
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 for scorecard_missing_headsigns · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Warning28 instances
28 of 98 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 (opens the GTFS Schedule reference on an external site)
- Warning10 instances
Some route long names repeat the route's short name inside them.
Apps show both names together, so riders see the number twice, like '5 5 Downtown'.
Fix: Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'. (One field per flagged route.)
Finding code: route_long_name_contains_short_name · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning9 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 for mixed_case_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning6 instances
Route short name too long (flagged by the MobilityData validator).
See the linked rule for what this affects.
Fix: Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)
Finding code: route_short_name_too_long · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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 (opens the validator rules on an external site)
- Warning1 instance
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.)
Finding code: missing_recommended_field · Read the fix guide for missing_recommended_field · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- Warning1 instance
The feed contains no fare information.
Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.
Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)
Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices (opens GTFS Best Practices on an external site)
- Info4 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 for service_window_outside_feed_period · See MobilityData GTFS Validator rules (opens the validator rules on an external site)
- 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 (opens the validator rules on an external site)
- 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 (opens the validator rules on an external site)
How we measured this
Checked for changes 18 hours ago; last changed 31 days ago.
Measured 3 of 4 score categories from the feed URL on file (publisher not verified).
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 configured feed URL. Publisher ownership of that URL is not verified.
Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.
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.5, validator 8.0.1.
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 282 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 98 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 71% of trips; the mark needs 90% of each.
- Valid Met
- Passes validation with no errors.
- Current Met
- Service data covers the next 282 days.
- Accessible Not yet
- States wheelchair access on 0% of stops and 71% 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.
- 79 of 135 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 281 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 59 / 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 43 / 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 New York portfolio: the same scorecards for every feed we track in that group, on one free page.
Similar feeds in New York
Other scorecards in New York, starting with the same kind of service at a similar size. Listed for comparison, not ranked.
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/clinton-county-public-transit-ccpt/2026-11-21.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-11-21. 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.