{ "agency": { "id": "greene-county-transit", "name": "Greene County Transit", "subdivision_code": "US-NY", "subdivision_name": "New York" }, "categories": { "completeness": { "details": { "accessibility": { "measures": "presence_not_usability", "score": 15.6, "stops_marked_accessible_pct": 0.0, "stops_marked_not_accessible_pct": 0.0, "stops_stated_pct": 0.0, "trips_stated_pct": 41.7 }, "accessibility_measures": "presence_not_usability", "cemv": { "declared": false, "supported": false }, "components": { "contact": 7.5, "fares": 0.0, "headsigns": 0.0, "stop_names": 15.0, "wheelchair_stops": 0.0, "wheelchair_trips": 6.2 }, "fare_free": false, "fares": { "applied": false, "has_leg_rules": false, "has_products": false, "has_transfer_rules": false, "model": "none", "product_count": 0 }, "flex": { "booking_reachable": false, "booking_rule_count": 0, "has_booking_rules": false, "has_flex": false }, "has_fares": false, "headsign_applicable_trips": 24, "headsign_loop_exempt_trips": 0, "headsign_pct": 0.0, "headsign_scored_pct": 0.0, "mixed_case_stop_name_pct": 100.0, "pathways": { "has_entrances": false, "has_levels": false, "has_pathways": false, "has_stations": false, "has_step_free": false, "pathway_count": 0 }, "stops": 141, "translations": { "feed_lang": "en", "has_translations": false, "languages": [], "translated_tables": [], "translation_count": 0 }, "trips": 24, "wheelchair_accessible_pct": 41.7, "wheelchair_boarding_pct": 0.0, "wheelchair_marked_accessible_pct": 0.0, "wheelchair_marked_not_accessible_pct": 0.0 }, "findings": [ { "code": "scorecard_wheelchair_boarding_unknown", "count": 141, "effort": "A column in stops.txt; your scheduling software likely has it.", "fix": "Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.", "owner": "Likely your team", "points": 25.0, "severity": "WARNING", "what": "141 of 141 stops don't say whether a wheelchair user can board there.", "why": "Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all." }, { "code": "scorecard_wheelchair_accessible_unknown", "count": 14, "effort": "A default or per-trip field in your export.", "fix": "Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.", "owner": "Likely your export tool", "points": 8.7, "severity": "WARNING", "what": "14 of 24 trips don't say whether the vehicle is wheelchair accessible.", "why": "Even with accessible stops, riders need to know the bus itself can take them." }, { "code": "scorecard_no_fare_data", "count": 1, "effort": "A small file for most flat-fare systems.", "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.", "owner": "", "points": 15.0, "severity": "WARNING", "what": "The feed contains no fare information.", "why": "Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected." }, { "code": "scorecard_missing_headsigns", "count": 24, "effort": "Usually one value per route pattern in your scheduling source.", "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.", "owner": "", "points": 15.0, "severity": "WARNING", "what": "24 of 24 trips lack rider-facing destination or direction text.", "why": "When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming." }, { "code": "scorecard_no_feed_contact", "count": 1, "effort": "One field.", "fix": "Add feed_contact_email to feed_info.txt.", "owner": "", "points": 7.5, "severity": "INFO", "what": "feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).", "why": "Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger." } ], "name": "completeness", "score": 28.8, "status": "measured", "summary": "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.", "weight": 0.25 }, "correctness": { "details": { "distinct_codes": 10, "instances_by_severity": { "ERROR": 1, "INFO": 3, "WARNING": 440 }, "validator_version": "8.0.1" }, "findings": [ { "code": "trip_distance_exceeds_shape_distance", "count": 1, "effort": "Varies.", "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.", "owner": "", "points": 12.0, "severity": "ERROR", "what": "Trip distance exceeds shape distance (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "missing_timepoint_value", "count": 362, "effort": "Usually one export setting.", "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.", "owner": "Likely your export tool", "points": 8.0, "severity": "WARNING", "what": "Some rows in stop_times.txt leave the timepoint column blank.", "why": "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." }, { "code": "stop_without_stop_time", "count": 50, "effort": "A review pass in your scheduling software.", "fix": "Remove retired stops from the export, or add them back to the trips that should serve them.", "owner": "Likely your export tool", "points": 6.0, "severity": "WARNING", "what": "Some stops exist in the feed but no trip ever stops at them.", "why": "Riders may walk to a stop where no bus is scheduled to arrive." }, { "code": "fast_travel_between_consecutive_stops", "count": 18, "effort": "A few minutes per flagged trip.", "fix": "Check the flagged stop times for transposed minutes.", "owner": "", "points": 6.0, "severity": "WARNING", "what": "Some scheduled trips move faster between stops than a bus can.", "why": "Usually a typo'd stop time; riders get arrival times no bus can meet." }, { "code": "fast_travel_between_far_stops", "count": 4, "effort": "Minutes per flagged trip once you open it.", "fix": "Check the two stop times for a wrong digit first. Then check whether a stop sits at the wrong coordinates, or a stop between them is missing.", "owner": "", "points": 4.0, "severity": "WARNING", "what": "Between two distant stops, the times imply a speed no bus reaches.", "why": "A rider gets a trip plan that cannot happen. Live systems then report delays that are not real." }, { "code": "mixed_case_recommended_field", "count": 3, "effort": "Often a bulk fix in your scheduling software.", "fix": "Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').", "owner": "Likely your export tool", "points": 4.0, "severity": "WARNING", "what": "Some rider-facing names are in ALL CAPS or all lowercase.", "why": "ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers." }, { "code": "leading_or_trailing_whitespaces", "count": 1, "effort": "Usually one export setting.", "fix": "Trim leading and trailing spaces on export. The scorecard's auto-fixed copy already does this.", "owner": "Likely your export tool", "points": 4.0, "severity": "WARNING", "what": "Some values have extra spaces at the start or end.", "why": "A stray space can break a match, so a stop or route may fail to link across files." }, { "code": "missing_feed_contact_email_and_url", "count": 1, "effort": "One field, set once in export settings.", "fix": "Add feed_contact_email or feed_contact_url to feed_info.txt.", "owner": "Likely your export tool", "points": 4.0, "severity": "WARNING", "what": "feed_info.txt lists no contact email and no contact URL.", "why": "Without a contact, apps like Google Maps can't reach you when they find a problem in the feed." }, { "code": "missing_recommended_field", "count": 1, "effort": "A field at a time; not urgent.", "fix": "Review the flagged fields and fill in the ones your riders would use.", "owner": "", "points": 4.0, "severity": "WARNING", "what": "Some files leave out fields that GTFS asks for but does not require.", "why": "Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners." }, { "code": "unknown_column", "count": 3, "effort": "A quick look at the flagged files.", "fix": "Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras.", "owner": "", "points": 0.5, "severity": "INFO", "what": "Some files contain columns that are not part of the GTFS spec.", "why": "Harmless to riders, but apps ignore these columns and they can hide typos in real column names." } ], "name": "correctness", "score": 47.5, "status": "measured", "summary": "The MobilityData validator flagged 10 kinds of issue across 444 instances (1 error, 440 warning, 3 informational).", "weight": 0.35 }, "freshness": { "details": { "days_until_expiry": 131, "effective_expiry_date": "2027-01-01", "feed_end_date": "2027-01-01", "feed_start_date": "2025-11-17", "feed_version": null, "has_feed_info": true, "last_service_date": "2027-01-01", "seasonal_boundary": false, "service_horizon_review_years": 10, "service_horizon_status": "within_review_threshold", "service_type": "fixed" }, "findings": [], "name": "freshness", "score": 100.0, "status": "measured", "summary": "Service data covers the next 131 days.", "weight": 0.2 }, "realtime": { "name": "realtime", "status": "not_yet_measured", "summary": "Not scored yet. Nothing here counts against the grade.", "weight": 0.2 } }, "confidence": { "feed_age_days": 0, "fetch_source": "origin", "level": "medium", "measured_categories": 3, "notes": [ "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." ], "rt_windows": 0, "total_categories": 4 }, "conformance": { "awarded": false, "criteria": [ { "detail": "1 validator error to resolve.", "key": "valid", "met": false }, { "detail": "Service data covers the next 131 days.", "key": "current", "met": true }, { "detail": "States wheelchair access on 0% of stops and 42% of trips; the mark needs 90% of each.", "key": "accessible", "met": false } ], "status": "not_yet", "summary": "Two requirements remain for this feed to earn 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.", "version": 2 }, "feed": { "license_note": "License: https://data.ny.gov/download/77gx-ii52/application/pdf", "reachable": true, "sha256": "d99738364c713904173ef2f48839f9fff65ef4e55b8cc3855d3901c69b7bf35c", "size_bytes": 325563, "source_provenance": "unverified", "static_url": "https://s3.amazonaws.com/datatools-511ny/public/Greene_County_Transit.zip" }, "fetch": { "final_url": "https://s3.amazonaws.com/datatools-511ny/public/Greene_County_Transit.zip", "max_attempts": 4, "reader_archive_profile": "raw-v1", "source": "origin", "user_agent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36" }, "generated_at": "2026-08-10T00:00:00+00:00", "geo": { "bbox": [ -74.43542, 42.11024, -73.77837, 42.45316 ], "lat": 42.25518, "lon": -73.88669, "stop_count": 141 }, "mode_profile": { "ferry_only": false, "graded": false, "has_ferry": false, "is_multimodal": false, "measured": true, "modes": [ { "key": "bus", "label": "Bus", "route_count": 7, "trip_count": 24, "trip_share_pct": 100.0 } ], "primary_mode": "bus", "primary_mode_label": "Bus", "route_count": 7, "trip_count": 24 }, "ntd_id_alignment": { "detail": "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.", "feed_agency_ids": [ "GCT-Greene-ny-us" ], "status": "unknown" }, "ntd_readiness": { "pillars": [ { "detail": "Published at a public URL.", "key": "published", "status": "ready" }, { "detail": "1 validator error to resolve.", "key": "valid", "status": "at_risk" }, { "detail": "Service data covers the next 144 days.", "key": "current", "status": "ready" }, { "detail": "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.", "key": "agency_id", "status": "ready" } ], "status": "at_risk", "summary": "This feed is close to NTD-ready. 1 validator error to resolve." }, "overall": { "grade": "F", "margin_to_lower_band": 54.8, "margin_to_next_band": 5.2, "score": 54.8 }, "recommendations": [ { "category": "accessibility", "code": "scorecard_route_color_low_contrast", "count": 3, "effort": "A per-route color setting in your scheduling software.", "fix": "Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.", "owner": "Likely your export tool", "points": 0.0, "severity": "WARNING", "what": "3 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (702, 711, 700/701).", "why": "Low-contrast route badges are hard to read for riders with low vision and wash out on a phone screen in sunlight at the stop." }, { "category": "accessibility", "code": "scorecard_stop_name_needs_tts", "count": 32, "effort": "A short text field per affected stop; start with the busiest.", "fix": "Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.", "owner": "", "points": 0.0, "severity": "INFO", "what": "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).", "why": "Riders who use a screen reader hear the raw name, so 'Main St & 2nd Ave' can come out as 'Main saint' or drop the ampersand." } ], "recompute": { "as_of": "2026-08-23", "feed_fetched_date": "2026-08-22", "kind": "freshness" }, "routability": { "boardable_stops": 141, "findings": [ { "code": "scorecard_orphan_stops", "count": 50, "effort": "A cleanup pass in your scheduling software.", "fix": "Remove stops no route serves, or add the trips that should call at them.", "owner": "Likely your export tool", "points": 0.0, "severity": "INFO", "what": "50 of 141 boardable stops are never served by any trip.", "why": "Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data." } ], "orphan_stops": 50, "single_stop_trips": 0, "trips_total": 24 }, "route_map": { "drawn_route_count": 7, "has_shapes": true, "path": "data/artifacts/greene-county-transit/geometry.geojson", "route_count": 7, "routes": [ { "color": "4A90E2", "color_name": "teal", "has_shape": true, "id": "700_701_BLUE", "label": "700/701", "long": "Catskill-Jefferson Heights-Leeds-Cairo.", "short": "700/701", "text_color": "FFFFFF", "type_label": "Bus" }, { "color": "CC6600", "color_name": "orange", "has_shape": true, "id": "702_ORANGE", "label": "702", "long": "Catskill-Coxsackie-9W Corridor", "short": "702", "text_color": "FFFFFF", "type_label": "Bus" }, { "color": "493329", "color_name": "black", "has_shape": true, "id": "706 BROWN", "label": "706", "long": "Catskill-Earlton-Greenville-Acra-Durham-Oak Hill-Cairo-Leeds", "short": "706", "text_color": "FFFFFF", "type_label": "Bus" }, { "color": "F7F0F0", "color_name": "white", "has_shape": true, "id": "708 WHITE", "label": "708", "long": "Catskill-Palenville-Tannersville-Hunter-Jewett-Lexington", "short": "708", "text_color": "000000", "type_label": "Bus" }, { "color": "D0021B", "color_name": "red", "has_shape": true, "id": "709 RED", "label": "709", "long": "Catskill-Acra-Durham-E. Windham-Ashland-Prattsville", "short": "709", "text_color": "FFFFFF", "type_label": "Bus" }, { "color": "10BAB3", "color_name": "teal", "has_shape": true, "id": "711 TEAL", "label": "711", "long": "Catskill-CGCC-CMH-Hudson Amtrak", "short": "711", "text_color": "FFFFFF", "type_label": "Bus" }, { "color": "F0F10C", "color_name": "yellow", "has_shape": true, "id": "Shuttle YELLOW", "label": "Sh", "long": "Catskill Shuttle Yellow", "short": "Sh", "text_color": "000000", "type_label": "Bus" } ], "stop_count": 141, "stop_points_capped": false }, "rubric_version": "1.3", "schema_version": "1.18", "scoring_profile": { "id": "gtfs-scorecard-1.3", "provenance": "GTFS Scorecard's project-authored weights, deductions, thresholds, grade bands, and fix ranking, informed by the California Transit Data Guidelines and the MobilityData gtfs-validator. It is not a worldwide standard or a compliance determination.", "rubric_version": "1.3" }, "shapes_readiness": { "detail": "All 24 trips have a shape in shapes.txt.", "status": "ready", "total_trips": 24, "trips_with_shape": 24 }, "snapshot_date": "2026-08-23", "top_fixes": [ { "code": "trip_distance_exceeds_shape_distance", "count": 1, "effort": "Varies.", "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.", "owner": "", "points": 12.0, "rank": 1, "severity": "ERROR", "what": "Trip distance exceeds shape distance (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "scorecard_wheelchair_boarding_unknown", "count": 141, "effort": "A column in stops.txt; your scheduling software likely has it.", "fix": "Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every stop. A field survey can start with the busiest stops.", "owner": "Likely your team", "points": 25.0, "rank": 2, "severity": "WARNING", "what": "141 of 141 stops don't say whether a wheelchair user can board there.", "why": "Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all." }, { "code": "scorecard_missing_headsigns", "count": 24, "effort": "Usually one value per route pattern in your scheduling source.", "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.", "owner": "", "points": 15.0, "rank": 3, "severity": "WARNING", "what": "24 of 24 trips lack rider-facing destination or direction text.", "why": "When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming." } ], "validator_version": "8.0.1" }