{
  "agency": {
    "id": "rochester-transit-service",
    "name": "Livingston County",
    "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": 15.0,
          "headsigns": 15.0,
          "stop_names": 15.0,
          "wheelchair_stops": 0.0,
          "wheelchair_trips": 0.0
        },
        "fare_free": false,
        "fares": {
          "applied": true,
          "has_leg_rules": false,
          "has_products": false,
          "has_transfer_rules": false,
          "model": "legacy",
          "product_count": 0
        },
        "flex": {
          "booking_reachable": false,
          "booking_rule_count": 0,
          "has_booking_rules": false,
          "has_flex": false
        },
        "has_fares": true,
        "headsign_applicable_trips": 87,
        "headsign_loop_exempt_trips": 0,
        "headsign_pct": 100.0,
        "headsign_scored_pct": 100.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": 46,
        "translations": {
          "feed_lang": "en",
          "has_translations": false,
          "languages": [],
          "translated_tables": [],
          "translation_count": 0
        },
        "trips": 87,
        "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": 46,
          "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": "46 of 46 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": 87,
          "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": "87 of 87 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_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": 52.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 published.",
      "weight": 0.25
    },
    "correctness": {
      "details": {
        "distinct_codes": 7,
        "instances_by_severity": {
          "ERROR": 0,
          "INFO": 116,
          "WARNING": 37
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "mixed_case_recommended_field",
          "count": 31,
          "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": 6.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": "route_short_name_too_long",
          "count": 3,
          "effort": "Varies.",
          "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.",
          "owner": "",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Route short name too long (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "missing_recommended_field",
          "count": 2,
          "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": "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": "service_extends_far_in_the_future",
          "count": 87,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 1.0,
          "severity": "INFO",
          "what": "Service extends far in the future (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "big_gap_in_service",
          "count": 25,
          "effort": "A review of your calendar dates.",
          "fix": "Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar.",
          "owner": "",
          "points": 0.8,
          "severity": "INFO",
          "what": "The feed has a stretch of two weeks or more with no service running.",
          "why": "A long gap can mean dates were left out of the calendar. Apps then show no trips on those days."
        },
        {
          "code": "service_window_outside_feed_period",
          "count": 4,
          "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": 79.8,
      "status": "measured",
      "summary": "The MobilityData validator flagged 7 kinds of issue across 153 instances (0 error, 37 warning, 116 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": 1262,
        "effective_expiry_date": "2030-02-05",
        "feed_end_date": "2030-02-05",
        "feed_start_date": "2025-08-25",
        "feed_version": "Livingston v1.2",
        "has_feed_info": true,
        "last_service_date": "2030-02-05",
        "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 1262 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": "Passes validation with no errors.",
        "key": "valid",
        "met": true
      },
      {
        "detail": "Service data covers the next 1262 days.",
        "key": "current",
        "met": true
      },
      {
        "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": "One requirement remains for this feed to earn the conformance mark. 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": "a39bb5f2ffacf2797fef5b537da85ede60ed92ce4388eabf9e594585e0a53328",
    "size_bytes": 881239,
    "source_provenance": "unverified",
    "static_url": "https://scheduledata.rgrta.com/Regionals/Livingston.zip"
  },
  "fetch": {
    "final_url": "https://scheduledata.rgrta.com/Regionals/Livingston.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.99181,
      42.55813,
      -77.44235,
      43.16271
    ],
    "lat": 42.79799,
    "lon": -77.8073,
    "stop_count": 46
  },
  "mode_profile": {
    "ferry_only": false,
    "graded": false,
    "has_ferry": false,
    "is_multimodal": false,
    "measured": true,
    "modes": [
      {
        "key": "bus",
        "label": "Bus",
        "route_count": 5,
        "trip_count": 87,
        "trip_share_pct": 100.0
      }
    ],
    "primary_mode": "bus",
    "primary_mode_label": "Bus",
    "route_count": 5,
    "trip_count": 87
  },
  "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": [
      "56d7f77c-bbc9-499b-8fcd-9ca98e419a2b"
    ],
    "status": "unknown"
  },
  "ntd_readiness": {
    "pillars": [
      {
        "detail": "Published at a public URL.",
        "key": "published",
        "status": "ready"
      },
      {
        "detail": "Passes validation with no errors.",
        "key": "valid",
        "status": "ready"
      },
      {
        "detail": "Service data covers the next 1275 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": "ready",
    "summary": "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."
  },
  "overall": {
    "grade": "C",
    "margin_to_lower_band": 6.3,
    "margin_to_next_band": 3.7,
    "score": 76.3
  },
  "recommendations": [
    {
      "category": "accessibility",
      "code": "scorecard_route_color_low_contrast",
      "count": 2,
      "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": "2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (231 / 243, 232).",
      "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": 21,
      "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": "21 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"Corner Rte 36 @ Stoner Hill Rd\", \"Corner Rte 436 @ Valley Rd\", \"M & T Bank\", 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": 46,
    "findings": [],
    "orphan_stops": 0,
    "single_stop_trips": 0,
    "trips_total": 87
  },
  "route_map": {
    "drawn_route_count": 5,
    "has_shapes": true,
    "path": "data/artifacts/rochester-transit-service/geometry.geojson",
    "route_count": 5,
    "routes": [
      {
        "color": "77BC1F",
        "color_name": "brown",
        "has_shape": true,
        "id": "1028",
        "label": "232",
        "long": "Mt M/Dansv/Nunda/Perry",
        "short": "232",
        "text_color": "FFFFFF",
        "type_label": "Bus"
      },
      {
        "color": "77BC1F",
        "color_name": "brown",
        "has_shape": true,
        "id": "1029",
        "label": "231 / 243",
        "long": "Mt. Morris/Geneseo/Avon",
        "short": "231 / 243",
        "text_color": "FFFFFF",
        "type_label": "Bus"
      },
      {
        "color": "173A79",
        "color_name": "green",
        "has_shape": true,
        "id": "1039",
        "label": "Rochester Shuttle",
        "long": "Geneseo/Rochester",
        "short": "Rochester Shuttle",
        "text_color": "FFFFFF",
        "type_label": "Bus"
      },
      {
        "color": "173A79",
        "color_name": "green",
        "has_shape": true,
        "id": "1042",
        "label": "Campus Shuttle",
        "long": "Geneseo/Campus Shuttle",
        "short": "Campus Shuttle",
        "text_color": "FFFFFF",
        "type_label": "Bus"
      },
      {
        "color": "173A79",
        "color_name": "green",
        "has_shape": true,
        "id": "1046",
        "label": "Knight Express",
        "long": "Geneseo/Knight Express",
        "short": "Knight Express",
        "text_color": "FFFFFF",
        "type_label": "Bus"
      }
    ],
    "stop_count": 46,
    "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 87 trips have a shape in shapes.txt.",
    "status": "ready",
    "total_trips": 87,
    "trips_with_shape": 87
  },
  "snapshot_date": "2026-08-23",
  "top_fixes": [
    {
      "code": "scorecard_wheelchair_boarding_unknown",
      "count": 46,
      "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": 1,
      "severity": "WARNING",
      "what": "46 of 46 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": 87,
      "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,
      "rank": 2,
      "severity": "WARNING",
      "what": "87 of 87 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": "mixed_case_recommended_field",
      "count": 31,
      "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": 6.0,
      "rank": 3,
      "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."
    }
  ],
  "validator_version": "8.0.1"
}
