{
  "agency": {
    "id": "81-connection-citygo-kanconnect",
    "name": "81 Connection, CityGo, KanConnect"
  },
  "autofix": {
    "available": true,
    "download_path": "data/artifacts/81-connection-citygo-kanconnect/corrected.zip",
    "download_url": "https://d14aimrgrbaz2a.cloudfront.net/data/artifacts/81-connection-citygo-kanconnect/corrected.zip",
    "fixes": [
      {
        "code": "autofix_trim_whitespace",
        "count": 1,
        "examples": [
          "'stop_name': 'Faith Drive ' -> 'Faith Drive'"
        ],
        "label": "Trimmed surrounding whitespace"
      }
    ],
    "total": 1
  },
  "categories": {
    "completeness": {
      "details": {
        "accessibility": {
          "measures": "presence_not_usability",
          "score": 98.7,
          "stops_marked_accessible_pct": 97.9,
          "stops_marked_not_accessible_pct": 0.0,
          "stops_stated_pct": 97.9,
          "trips_stated_pct": 100.0
        },
        "accessibility_measures": "presence_not_usability",
        "components": {
          "contact": 7.5,
          "fares": 0.0,
          "headsigns": 15.0,
          "stop_names": 15.0,
          "wheelchair_stops": 24.5,
          "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": 100.0,
        "pathways": {
          "has_entrances": false,
          "has_levels": false,
          "has_pathways": false,
          "has_stations": false,
          "has_step_free": false,
          "pathway_count": 0
        },
        "stops": 192,
        "trips": 28,
        "wheelchair_accessible_pct": 100.0,
        "wheelchair_boarding_pct": 97.9,
        "wheelchair_marked_accessible_pct": 97.9,
        "wheelchair_marked_not_accessible_pct": 0.0
      },
      "findings": [
        {
          "code": "scorecard_wheelchair_boarding_unknown",
          "count": 4,
          "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": 0.5,
          "severity": "WARNING",
          "what": "4 of 192 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": 77.0,
      "status": "measured",
      "summary": "98% of stops state wheelchair accessibility (98% 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": 0,
          "INFO": 1,
          "WARNING": 7688
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "leading_or_trailing_whitespaces",
          "count": 7670,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'leading_or_trailing_whitespaces' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 8.0,
          "severity": "WARNING",
          "what": "Leading or trailing whitespaces (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "route_long_name_contains_short_name",
          "count": 5,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'route_long_name_contains_short_name' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Route long name contains short name (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "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": "stop_too_far_from_shape",
          "count": 3,
          "effort": "A few minutes per flagged stop.",
          "fix": "Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced.",
          "owner": "Likely your export tool",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Some stops sit far from the route line they belong to.",
          "why": "Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner."
        },
        {
          "code": "expired_calendar",
          "count": 2,
          "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": "mixed_case_recommended_field",
          "count": 2,
          "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": "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": "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."
        },
        {
          "code": "unknown_column",
          "count": 1,
          "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": 59.5,
      "status": "measured",
      "summary": "The MobilityData validator flagged 10 kinds of issue across 7689 instances (0 error, 7688 warning, 1 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": -921,
        "feed_end_date": "2023-12-31",
        "feed_start_date": "2018-12-26",
        "feed_version": "2.0",
        "has_feed_info": true,
        "last_service_date": "2023-12-31",
        "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 921 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 921 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 909 days ago.",
        "key": "current",
        "met": false
      },
      {
        "detail": "States wheelchair access on 98% of stops and 100% of trips.",
        "key": "accessible",
        "met": true
      }
    ],
    "status": "not_yet",
    "summary": "This feed is close to the conformance mark. Service data expired 909 days ago."
  },
  "feed": {
    "license_note": "No stated data license in the Mobility Database; verify before publishing.",
    "reachable": true,
    "sha256": "5a33e87229f4225a76ad67db2b378a5c71bb9fecb99d8db5e7dadae1c1756ccd",
    "size_bytes": 113835,
    "static_url": "https://salinacitygo.com/wp-content/uploads/2022/11/export-2022-11-30T10-18-07.zip"
  },
  "generated_at": "2026-06-27T00:00:00+00:00",
  "geo": {
    "bbox": [
      -97.70615,
      38.78352,
      -97.37185,
      39.82333
    ],
    "lat": 38.83089,
    "lon": -97.60991,
    "stop_count": 192
  },
  "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": [
      "1",
      "2",
      "3"
    ],
    "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 909 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 909 days ago, so FTA would find the link out of date."
  },
  "overall": {
    "grade": "F",
    "margin_to_lower_band": 50.1,
    "margin_to_next_band": 9.9,
    "score": 50.1
  },
  "recommendations": [
    {
      "code": "scorecard_stop_name_needs_tts",
      "count": 106,
      "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": "106 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"7th & Walnut\", \"United Building (Iron & 7th)\", \"Iron & Connecticut\", 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": 192,
    "findings": [],
    "orphan_stops": 0,
    "single_stop_trips": 0,
    "trips_total": 28
  },
  "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 921 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_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": 2,
      "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": "leading_or_trailing_whitespaces",
      "count": 7670,
      "effort": "Varies.",
      "fix": "Review the rule documentation for 'leading_or_trailing_whitespaces' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
      "owner": "",
      "points": 8.0,
      "rank": 3,
      "severity": "WARNING",
      "what": "Leading or trailing whitespaces (flagged by the MobilityData validator).",
      "why": "See the linked rule for what this affects."
    }
  ],
  "validator_version": "8.0.1"
}