{
  "agency": {
    "id": "lake-county-connection",
    "name": "Lake County Connection"
  },
  "autofix": {
    "available": true,
    "download_path": "data/artifacts/lake-county-connection/corrected.zip",
    "download_url": "https://d14aimrgrbaz2a.cloudfront.net/data/artifacts/lake-county-connection/corrected.zip",
    "fixes": [
      {
        "code": "autofix_trim_whitespace",
        "count": 4,
        "examples": [
          "'stop_name': 'W Main St/N Pulsifer Ave ' -> 'W Main St/N Pulsifer Ave'",
          "'route_desc': 'Leesburg to Eustis ' -> 'Leesburg to Eustis'",
          "'route_desc': 'The Villages to Leesburg ' -> 'The Villages to Leesburg'"
        ],
        "label": "Trimmed surrounding whitespace"
      },
      {
        "code": "autofix_stop_name_case",
        "count": 5,
        "examples": [
          "FL-44/US-441 -> Fl-44/us-441",
          "FL-19/FL-44 -> Fl-19/fl-44",
          "FL-19/FL-44 -> Fl-19/fl-44"
        ],
        "label": "Recased shouting stop names"
      }
    ],
    "total": 9
  },
  "categories": {
    "completeness": {
      "details": {
        "accessibility": {
          "measures": "presence_not_usability",
          "score": 37.8,
          "stops_marked_accessible_pct": 0.4,
          "stops_marked_not_accessible_pct": 0.0,
          "stops_stated_pct": 0.4,
          "trips_stated_pct": 100.0
        },
        "accessibility_measures": "presence_not_usability",
        "components": {
          "contact": 7.5,
          "fares": 0.0,
          "headsigns": 15.0,
          "stop_names": 14.8,
          "wheelchair_stops": 0.1,
          "wheelchair_trips": 15.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_pct": 100.0,
        "mixed_case_stop_name_pct": 98.9,
        "pathways": {
          "has_entrances": false,
          "has_levels": false,
          "has_pathways": false,
          "has_stations": false,
          "has_step_free": false,
          "pathway_count": 0
        },
        "stops": 452,
        "trips": 153,
        "wheelchair_accessible_pct": 100.0,
        "wheelchair_boarding_pct": 0.4,
        "wheelchair_marked_accessible_pct": 0.4,
        "wheelchair_marked_not_accessible_pct": 0.0
      },
      "findings": [
        {
          "code": "scorecard_wheelchair_boarding_unknown",
          "count": 450,
          "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": 24.9,
          "severity": "WARNING",
          "what": "450 of 452 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_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_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": "App makers and state data programs have nobody to email when they spot a problem with your feed, so problems linger."
        }
      ],
      "name": "completeness",
      "score": 52.4,
      "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": 5,
        "instances_by_severity": {
          "ERROR": 0,
          "INFO": 0,
          "WARNING": 20
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "missing_recommended_field",
          "count": 11,
          "effort": "A field at a time; not urgent.",
          "fix": "Review the flagged fields and fill in the ones your riders would use.",
          "owner": "",
          "points": 6.0,
          "severity": "WARNING",
          "what": "Some files are missing recommended (not required) fields.",
          "why": "Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners."
        },
        {
          "code": "mixed_case_recommended_field",
          "count": 6,
          "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": "expired_calendar",
          "count": 1,
          "effort": "One setting in most export tools.",
          "fix": "Remove past service periods the next time you export the feed.",
          "owner": "Likely your export tool",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Some service calendars in the feed have already expired.",
          "why": "Expired calendars are dead weight and can hide real schedule problems from your staff and vendors."
        },
        {
          "code": "missing_feed_contact_email_and_url",
          "count": 1,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Missing feed contact email and url (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "trip_coverage_not_active_for_next7_days",
          "count": 1,
          "effort": "One setting in most export tools.",
          "fix": "Trim past service periods the next time you export.",
          "owner": "Likely your export tool",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Many of the feed's trips don't run at all in the next 7 days.",
          "why": "It usually means old service periods are still in the export, making the feed bigger and harder to check."
        }
      ],
      "name": "correctness",
      "score": 76.0,
      "status": "measured",
      "summary": "The MobilityData validator flagged 5 kinds of issue across 20 instances (0 error, 20 warning, 0 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": -2271,
        "feed_end_date": null,
        "feed_start_date": null,
        "feed_version": null,
        "has_feed_info": true,
        "last_service_date": "2020-04-20",
        "seasonal_boundary": false,
        "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 2271 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": "scorecard_missing_feed_info_dates",
          "count": 1,
          "effort": "Two fields, set once in export settings.",
          "fix": "Add feed_info.txt with feed_start_date and feed_end_date to your export.",
          "owner": "Likely your export tool",
          "points": 15.0,
          "severity": "WARNING",
          "what": "feed_info.txt is missing its start/end dates",
          "why": "Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates."
        }
      ],
      "name": "freshness",
      "score": 0.0,
      "status": "measured",
      "summary": "Service data ended 2271 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
    }
  },
  "conformance": {
    "awarded": false,
    "criteria": [
      {
        "detail": "Passes validation with no errors.",
        "key": "valid",
        "met": true
      },
      {
        "detail": "Service data expired 2259 days ago.",
        "key": "current",
        "met": false
      },
      {
        "detail": "States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.",
        "key": "accessible",
        "met": false
      }
    ],
    "status": "not_yet",
    "summary": "This feed is close to the conformance mark. Service data expired 2259 days ago. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each."
  },
  "feed": {
    "license_note": "No stated data license in the Mobility Database; verify before publishing.",
    "reachable": true,
    "sha256": "1921faff920d681e72e66d47c4397befbc0f29eea49b805a63f69a8b689f906b",
    "size_bytes": 103164,
    "static_url": "http://www.ftis.org/PostFileDownload.aspx?id=160A0"
  },
  "generated_at": "2026-06-27T00:00:00+00:00",
  "geo": {
    "bbox": [
      -81.94832,
      28.53219,
      -81.58979,
      28.9617
    ],
    "lat": 28.82022,
    "lon": -81.74647,
    "stop_count": 452
  },
  "ntd_id_alignment": {
    "detail": "If you report to the National Transit Database, your GTFS agency_id should be your five-digit NTD ID by report year 2026 (2025 for full reporters). We don't have your NTD ID on file, so this one is not checked yet.",
    "feed_agency_ids": [],
    "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 expired 2259 days ago, so FTA would find the link out of date.",
        "key": "current",
        "status": "not_ready"
      }
    ],
    "status": "not_ready",
    "summary": "Resolve this before you certify on the D-10. Service data expired 2259 days ago, so FTA would find the link out of date."
  },
  "overall": {
    "grade": "F",
    "margin_to_lower_band": 49.6,
    "margin_to_next_band": 10.4,
    "score": 49.6
  },
  "recommendations": [
    {
      "code": "scorecard_route_color_low_contrast",
      "count": 1,
      "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": "1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (50E).",
      "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."
    },
    {
      "code": "scorecard_stop_name_needs_tts",
      "count": 452,
      "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": "452 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"E Myers Blvd/S Sunset Ave\", \"E Myers Blvd/Putnam St\", \"E Myers Blvd/Blett St\", 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-07-09",
    "feed_fetched_date": "2026-07-08",
    "kind": "freshness"
  },
  "routability": {
    "boardable_stops": 452,
    "findings": [],
    "orphan_stops": 0,
    "single_stop_trips": 0,
    "trips_total": 153
  },
  "rubric_version": "1.1",
  "schema_version": "1.4",
  "snapshot_date": "2026-07-09",
  "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 2271 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": "scorecard_wheelchair_boarding_unknown",
      "count": 450,
      "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": 24.9,
      "rank": 2,
      "severity": "WARNING",
      "what": "450 of 452 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_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,
      "rank": 3,
      "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."
    }
  ],
  "validator_version": "8.0.1"
}