{ "agency": { "id": "steuben-county-transit", "name": "Steuben County Transit", "subdivision_code": "US-NY", "subdivision_name": "New York" }, "categories": { "completeness": { "details": { "accessibility": { "measures": "presence_not_usability", "score": 0.0, "stops_marked_accessible_pct": 0.0, "stops_marked_not_accessible_pct": 0.0, "stops_stated_pct": 0.0, "trips_stated_pct": 0.0 }, "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": 0.0 }, "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": 25, "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": 20, "translations": { "feed_lang": "en", "has_translations": false, "languages": [], "translated_tables": [], "translation_count": 0 }, "trips": 25, "wheelchair_accessible_pct": 0.0, "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": 20, "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": "20 of 20 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": 25, "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": 15.0, "severity": "WARNING", "what": "25 of 25 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": 25, "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": "25 of 25 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": 22.5, "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": 12, "instances_by_severity": { "ERROR": 4, "INFO": 5, "WARNING": 121 }, "validator_version": "8.0.1" }, "findings": [ { "code": "equal_shape_distance_diff_coordinates", "count": 4, "effort": "Varies.", "fix": "Review the rule documentation for 'equal_shape_distance_diff_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 12.0, "severity": "ERROR", "what": "Equal shape distance diff coordinates (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "equal_shape_distance_same_coordinates", "count": 80, "effort": "Usually one export setting.", "fix": "Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.", "owner": "Likely your export tool", "points": 8.0, "severity": "WARNING", "what": "Some route lines list the same point twice in a row.", "why": "Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export." }, { "code": "equal_shape_distance_diff_coordinates_distance_below_threshold", "count": 18, "effort": "Varies.", "fix": "Review the rule documentation for 'equal_shape_distance_diff_coordinates_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 6.0, "severity": "WARNING", "what": "Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "missing_timepoint_value", "count": 12, "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": 6.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": "trip_distance_exceeds_shape_distance_below_threshold", "count": 6, "effort": "Usually an export-tool fix, not hand editing.", "fix": "Re-generate shape_dist_traveled on export so stop and shape distances use the same units.", "owner": "Likely your export tool", "points": 6.0, "severity": "WARNING", "what": "On some trips the stop distances run a little past the end of the route line.", "why": "The stop and shape distance values don't quite line up, so any math that uses them can drift." }, { "code": "stop_without_stop_time", "count": 2, "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": 4.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": "feed_expiration_date7_days", "count": 1, "effort": "Usually a re-export from your scheduling software.", "fix": "Export and publish an updated GTFS feed that covers at least the next 30 days of service.", "owner": "Likely your export tool", "points": 4.0, "severity": "WARNING", "what": "This feed's service calendar runs out within the next 7 days.", "why": "When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all." }, { "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." }, { "code": "feed_valid_beyond_total_service_window", "count": 1, "effort": "Varies.", "fix": "Review the rule documentation for 'feed_valid_beyond_total_service_window' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 0.5, "severity": "INFO", "what": "Feed valid beyond total service window (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "service_window_outside_feed_period", "count": 1, "effort": "Two fields in feed_info.txt, or one export setting.", "fix": "Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside.", "owner": "Likely your export tool", "points": 0.5, "severity": "INFO", "what": "Some service dates fall outside the date window set in feed_info.txt.", "why": "feed_info.txt should span every day your service runs, so apps know when the data applies." } ], "name": "correctness", "score": 44.5, "status": "measured", "summary": "The MobilityData validator flagged 12 kinds of issue across 130 instances (4 error, 121 warning, 5 informational).", "weight": 0.35 }, "freshness": { "details": { "days_until_expiry": -235, "effective_expiry_date": "2025-12-31", "feed_end_date": "2025-12-31", "feed_start_date": "2024-12-16", "feed_version": null, "has_feed_info": true, "last_service_date": "2026-12-31", "seasonal_boundary": false, "service_horizon_review_years": 10, "service_horizon_status": "within_review_threshold", "service_type": "fixed" }, "findings": [ { "code": "scorecard_feed_expired", "count": 1, "effort": "Usually one export setting; export on a schedule so it never lapses again.", "fix": "Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.", "owner": "Likely your export tool", "points": 100.0, "severity": "ERROR", "what": "Service data ended 235 day(s) ago.", "why": "When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist." } ], "name": "freshness", "score": 0.0, "status": "measured", "summary": "Service data ended 235 day(s) ago. Trip planners have likely already dropped this feed.", "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 expired 235 days ago.", "key": "current", "met": false }, { "detail": "States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.", "key": "accessible", "met": false } ], "status": "not_yet", "summary": "This feed does not meet the conformance requirements yet. Here is what the mark needs: 1 validator error to resolve. Service data expired 235 days ago. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.", "version": 2 }, "feed": { "license_note": "No stated data license in the Mobility Database; verify before publishing.", "reachable": true, "sha256": "fee0495e762508035556b258f2c0fd011abbea61e9636359ec97881746c3cea6", "size_bytes": 52192, "source_provenance": "unverified", "static_url": "https://s3.amazonaws.com/datatools-511ny/public/Steuben_County_Transit.zip" }, "fetch": { "final_url": "https://s3.amazonaws.com/datatools-511ny/public/Steuben_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": [ -77.3504, 42.09021, -76.80598, 42.40798 ], "lat": 42.33755, "lon": -77.30946, "stop_count": 20 }, "mode_profile": { "ferry_only": false, "graded": false, "has_ferry": false, "is_multimodal": false, "measured": true, "modes": [ { "key": "bus", "label": "Bus", "route_count": 3, "trip_count": 25, "trip_share_pct": 100.0 } ], "primary_mode": "bus", "primary_mode_label": "Bus", "route_count": 3, "trip_count": 25 }, "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": [ "SCT-Steuben-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 expired 222 days ago, so FTA would find the link out of date.", "key": "current", "status": "not_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": "not_ready", "summary": "Resolve this before you certify on the D-10. 1 validator error to resolve. Service data expired 222 days ago, so FTA would find the link out of date." }, "overall": { "grade": "F", "margin_to_lower_band": 26.5, "margin_to_next_band": 33.5, "score": 26.5 }, "recommendations": [ { "category": "accessibility", "code": "scorecard_stop_name_needs_tts", "count": 4, "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": "4 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"Save-A-Lot/Tractor Supply\", \"Corning P&C Plaza\", \"Schoolhouse - Liberty Street & Washington Street\", 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": 20, "findings": [ { "code": "scorecard_orphan_stops", "count": 2, "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": "2 of 20 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": 2, "single_stop_trips": 0, "trips_total": 25 }, "route_map": { "drawn_route_count": 3, "has_shapes": true, "path": "data/artifacts/steuben-county-transit/geometry.geojson", "route_count": 3, "routes": [ { "color": "1A7A46", "color_name": "green", "has_shape": true, "id": "3609", "label": "2", "long": "Village of Bath", "short": "2", "text_color": "FFFFFF", "type_label": "Bus" }, { "color": "1A7A46", "color_name": "green", "has_shape": true, "id": "3610", "label": "1", "long": "Bath-Corning", "short": "1", "text_color": "FFFFFF", "type_label": "Bus" }, { "color": "1A7A46", "color_name": "green", "has_shape": true, "id": "3611", "label": "3", "long": "Hammondsport", "short": "3", "text_color": "FFFFFF", "type_label": "Bus" } ], "stop_count": 20, "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 25 trips have a shape in shapes.txt.", "status": "ready", "total_trips": 25, "trips_with_shape": 25 }, "snapshot_date": "2026-08-23", "top_fixes": [ { "code": "scorecard_feed_expired", "count": 1, "effort": "Usually one export setting; export on a schedule so it never lapses again.", "fix": "Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.", "owner": "Likely your export tool", "points": 100.0, "rank": 1, "severity": "ERROR", "what": "Service data ended 235 day(s) ago.", "why": "When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist." }, { "code": "equal_shape_distance_diff_coordinates", "count": 4, "effort": "Varies.", "fix": "Review the rule documentation for 'equal_shape_distance_diff_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 12.0, "rank": 2, "severity": "ERROR", "what": "Equal shape distance diff coordinates (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "scorecard_wheelchair_boarding_unknown", "count": 20, "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": 3, "severity": "WARNING", "what": "20 of 20 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." } ], "validator_version": "8.0.1" }