GTFS Scorecard
← All agencies

Feed status · checked 2026-08-01

Greene County Transit

Based on the feed this agency publishes

Service mode Bus

54.8 / 100

unchanged since 2026-07-31

Catalogued in New York.

Covers 153 daysAccessibility gapsRealtime not yet published

A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.3, validator 8.0.1.

Checked for changes 11 hours ago; last changed 41 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

Fix 01

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

Trip distance exceeds shape distance (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +12 points in its category

Fix 02

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

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

Fix 03

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.

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

⏱ Usually one value per route pattern in your scheduling source.worth about +15 points in its category

Finding handoff

Move one finding to a recheck

Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.

Feed evidence
Trip distance exceeds shape distance (flagged by the MobilityData validator).
Next action
Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
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. Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  2. 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.

    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. 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. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

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 153 days.
Published accessibility data
Accessibility information is stated for 0% of stops and 41.7% 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

Correctness47.5 / 100

The MobilityData validator flagged 10 kinds of issue across 444 instances (1 error, 440 warning, 3 informational).

Freshness100.0 / 100

Service data covers the next 153 days.

Rider experience28.8 / 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.

Accessibility15.6 / 100

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

2 accessibility depth signals

  • 3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (702, 711, 700/701).

    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.

  • 32 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Flag stops along CR-20/Old Rte 23", "Flag stops along Roosevelt Ave in Cairo", "Chicken Run / South Road", 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 141 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.

  • 700/701 (teal)
  • 702 (orange)
  • 706 (black)
  • 708 (white)
  • 709 (red)
  • 711 (teal)
  • Sh (yellow)
Routes in Greene County Transit's feed
RouteTypeLine color
700/701 Catskill-Jefferson Heights-Leeds-Cairo.Busteal
702 Catskill-Coxsackie-9W CorridorBusorange
706 Catskill-Earlton-Greenville-Acra-Durham-Oak Hill-Cairo-LeedsBusblack
708 Catskill-Palenville-Tannersville-Hunter-Jewett-LexingtonBuswhite
709 Catskill-Acra-Durham-E. Windham-Ashland-PrattsvilleBusred
711 Catskill-CGCC-CMH-Hudson AmtrakBusteal
Sh Catskill Shuttle YellowBusyellow
List every stop
  • Cumberland Farms
  • East Durham Post Office
  • PROS (Mental Health)
  • Flag Stops along West Bridge Street (EB)
  • Flag Stops along West Bridge Street (WB)
  • Landon Ave (North)
  • Purling Roller Rink
  • Mountain View Apartments
  • Independence Lane & Route 144
  • Mountain View Apartments
  • Windham Willows
  • Acra Post Office / Acra Manor
  • Bethany Village
  • Flag stops along CR-20/Old Rte 23
  • 2nd Street & South Montgomery Street
  • Mental Health Resources
  • Tops Market - Greenville
  • Route 385 & Sutton Place
  • Arc of Ulster-Green - Cairo Center
  • Fairground Estates
  • Dollar General
  • Rainbow Cabins, Route 32, Kiskatom
  • Greene County Office Building
  • Flag Stops along Route 9W
  • Jewett Senior Service Center
  • Selena's Diner
  • Father and Sons Auto | U-Haul
  • Pinetree Apartments
  • Earlton Fire Department
  • Hillcrest Road
  • Route 23 & Five Mile Woods Road
  • Catskill - Main Street
  • Flag Stops Along Routes 23/32
  • Athens Post Office
  • Freehold Post Office
  • Lexington Post Office
  • Rivertown Senior Apartments
  • Stewart's
  • Haines Falls Fire Dept./ Stewart's
  • Price Chopper Plaza
  • Broad St thru Spring St
  • B&B Lounge
  • North Warren St. - Rivertown Center
  • US-9W & Division Street
  • Arc Mid-Hudson - Catskill
  • Winter Clove Road
  • Flag stops along Roosevelt Ave in Cairo
  • NY-385 & Mansion Street
  • Leeds CR-23B (Main Street)
  • Columbia-Greene Community College
  • McDonald's
  • Chicken Run / South Road
  • South Cairo Post Office
  • Flag Stops Along Routes 23/32
  • South Cairo
  • Four Corners
  • Alpine Garden Village
  • Sleepy Hollow Lake Entrance (Route 385)
  • Tops Market - Coxsackie
  • Windham Post Office / Valero
  • Community Action/Catskill Inn
  • Community Action of Greene County
  • 9W
  • Hemlock Nob
  • Autumn Grove Apts.
  • 428 West Main
  • US-9W
  • Community Action/ Catskill Inn On Request
  • Acra Senior Services Center
  • Route 83 and 23A
  • Catskill Post Office
  • Greene Medical Arts Center
  • Great American
  • Acra Manor
  • Irving Road
  • Flag Stops Along RT 45
  • Medical Arts - 5 Mile Woods
  • Catskill Senior Nutrition Site
  • New Baltimore Rest Area
  • Oak Hill Post Office
  • Diederich's Trailer Park
  • Stewarts - GC Visitors Center
  • Bridge Street Theater
  • Hensonville Post Office
  • Ashland Fire Dept.
  • Malden Rest Area
  • Brookside Campground
  • Pineview Road & Schoharie Turnpike
  • Catskill Hub
  • Green Medical Arts Center
  • Olivett Lane
  • Columbia Memorial Hospital
  • Catskill Court House
  • Wal-Mart/Catskills Common Area
  • Story Farms
  • Kaaterskill United Methodist Church
  • Dutchman's Landing (Seasonal)
  • Hannaford
  • Windham Fire Dept.
  • Howard Drive & Apple Blossom Lane
  • Central Mall, Route 83 and 23A
  • Cedar Lane & RT 144
  • Hop-O-Nose Apartments
  • Catskill High School
  • Xtra Mart
  • Leeds Post Office
  • PLACEHOLDER Sleepy Hollow
  • Tops Market - Tannersville
  • Eastview Garden Apts.
  • Catskill Library
  • Ashland Post Office
  • Hill St. (Hop-O-Nose/Main) On Request
  • Flag Stops along Broad St
  • GCMH Cairo
  • Walgreens - Urgent Care
  • Carson City Motel Southbound
  • Carson City Motel Northbound
  • The Mews
  • Hudson Train Station
  • Flag Stops along Route 9G
  • Willows at Brandow Point ON REQUEST
  • Silver Spring Road
  • West Main Apartments
  • Flag stops along Main Street Cairo
  • Main Street - Cairo
  • Devasego Park
  • New Baltimore Post Office - NY-144
  • Field Goods - Schoharie
  • Field Goods - Athens
  • Mansion Street & Reed
  • Tranquility Rd & NY-81
  • Four Seasons Motel, Route 32, Kiskatom
  • RT-81 Norton Hill
  • Hill St & Main St (Hop-O-Nose)
  • Flag Stops along Spring St
  • Embought Road
  • PLACEHOLDER Catskill Urgent Care
  • Mental Health ON REQUEST
  • Country Estates
  • DSS Water St
  • DSS Main St

Over time

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

2026-07-25: 54.82026-07-30: 54.82026-07-31: 54.82026-08-01: 54.8
Show the numbers
CheckScoreChange
2026-07-2554.8 first check
2026-07-3054.8 no change
2026-07-3154.8 no change
2026-08-0154.8 no change

What changed since your last check

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

Everything we checked

15 findings, ordered by severity.

Show every finding
  • Error1 instance

    Trip distance exceeds shape distance (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: trip_distance_exceeds_shape_distance · See MobilityData GTFS Validator rules

  • Warning362 instances

    Missing timepoint value (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

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

  • Warning141 instances

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

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

  • Warning24 instances

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

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

  • Warning14 instances

    14 of 24 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

  • Warning4 instances

    Fast travel between far stops (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

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

  • Warning3 instances

    Some rider-facing names are in ALL CAPS or all lowercase.

    ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers.

    Fix: Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE'). (Often a bulk fix in your scheduling software.)

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

  • Warning1 instance

    Some values have extra spaces at the start or end.

    A stray space can break a match, so a stop or route may fail to link across files.

    Fix: Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this. (Usually one export setting.)

    Finding code: leading_or_trailing_whitespaces · 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 · See MobilityData GTFS Validator rules

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

  • Warning1 instance

    The feed contains no fare information.

    Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

    Fix: Add fare_attributes.txt (or Fares v2 files) with your fare structure. If your service is fare-free, ask to have it marked fare-free instead. (A small file for most flat-fare systems.)

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

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

  • Info1 instance

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

    Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.

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

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

NTD GTFS readiness Needs attention

This feed is close to NTD-ready. 1 validator error to resolve.

Published Ready
Published at a public URL.
Valid Needs attention
1 validator error to resolve.
Current Ready
Service data covers the next 153 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 24 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. 1 validator error to resolve. States wheelchair access on 0% of stops and 42% of trips; the mark needs 90% of each.

Valid Not yet
1 validator error to resolve.
Current Met
Service data covers the next 153 days.
Accessible Not yet
States wheelchair access on 0% of stops and 42% 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.

  • 50 of 141 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 152 days of service ahead, clearing the four-week (28-day) window Maps asks for. 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

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 48 / 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 29 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality Not yet published
GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Show your grade

Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.

Greene County Transit GTFS data quality grade: F

Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.

Cite this record

This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/greene-county-transit/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.