{
  "agency": {
    "id": "kitsap-transit",
    "name": "Kitsap Transit"
  },
  "autofix": {
    "available": false
  },
  "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",
        "components": {
          "contact": 15.0,
          "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_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": 1323,
        "trips": 7485,
        "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": 1323,
          "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": "1323 of 1323 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": 7485,
          "effort": "Often one default setting in your export.",
          "fix": "Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).",
          "owner": "Likely your export tool",
          "points": 15.0,
          "severity": "WARNING",
          "what": "7485 of 7485 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."
        }
      ],
      "name": "completeness",
      "score": 60.0,
      "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": 4,
        "instances_by_severity": {
          "ERROR": 0,
          "INFO": 12,
          "WARNING": 12
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "fast_travel_between_consecutive_stops",
          "count": 6,
          "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 travel implausibly fast between stops.",
          "why": "Usually a typo'd stop time; riders get impossible arrival estimates."
        },
        {
          "code": "unusable_trip",
          "count": 5,
          "effort": "Worth a vendor question if it appears often.",
          "fix": "Check the flagged trips in your scheduling software; remove them or restore their missing stops.",
          "owner": "Likely your export tool",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Some trips serve fewer than two stops.",
          "why": "A trip with one stop can't be ridden; planners ignore it and it may signal an export problem."
        },
        {
          "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": "trip_headsign_matches_intermediate_stop",
          "count": 12,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'trip_headsign_matches_intermediate_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 0.8,
          "severity": "INFO",
          "what": "Trip headsign matches intermediate stop (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        }
      ],
      "name": "correctness",
      "score": 85.2,
      "status": "measured",
      "summary": "The MobilityData validator flagged 4 kinds of issue across 24 instances (0 error, 12 warning, 12 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": 65,
        "feed_end_date": "2026-09-12",
        "feed_start_date": "2026-06-14",
        "feed_version": "S1000066",
        "has_feed_info": true,
        "last_service_date": "2026-09-12",
        "seasonal_boundary": false,
        "service_type": "fixed"
      },
      "findings": [],
      "name": "freshness",
      "score": 100.0,
      "status": "measured",
      "summary": "Service data covers the next 65 days.",
      "weight": 0.2
    },
    "realtime": {
      "details": {
        "coverage_pct": null,
        "kinds_reachable": 1,
        "rt_freshness": null,
        "samples": 9,
        "scheduled_trips_in_window": 0,
        "worst_lag_seconds": null
      },
      "findings": [
        {
          "code": "scorecard_rt_trip_updates_unreachable",
          "count": 1,
          "effort": "Usually a vendor support ticket.",
          "fix": "Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.",
          "owner": "",
          "points": 8.3,
          "severity": "ERROR",
          "what": "The trip updates realtime feed failed during sampling.",
          "why": "When this feed is down, riders see scheduled times presented as if they were live."
        },
        {
          "code": "scorecard_rt_vehicle_positions_unreachable",
          "count": 1,
          "effort": "Usually a vendor support ticket.",
          "fix": "Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.",
          "owner": "",
          "points": 8.3,
          "severity": "ERROR",
          "what": "The vehicle positions realtime feed failed during sampling.",
          "why": "When this feed is down, riders see scheduled times presented as if they were live."
        },
        {
          "code": "scorecard_rt_no_timestamp",
          "count": 1,
          "effort": "A vendor configuration question.",
          "fix": "Set the GTFS-Realtime FeedHeader.timestamp on every response.",
          "owner": "",
          "points": 0.0,
          "severity": "INFO",
          "what": "Realtime feeds didn't include a header timestamp, so freshness couldn't be checked.",
          "why": "Without a header timestamp, apps and this scorecard can't tell how old the data is."
        }
      ],
      "name": "realtime",
      "score": 33.3,
      "status": "measured",
      "summary": "Sampled 9 times outside service hours: 1 of 3 feeds healthy.",
      "weight": 0.2
    }
  },
  "conformance": {
    "awarded": false,
    "criteria": [
      {
        "detail": "Passes validation with no errors.",
        "key": "valid",
        "met": true
      },
      {
        "detail": "Service data covers the next 77 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": "This feed is close to the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each."
  },
  "feed": {
    "license_note": "License: http://www.kitsaptransit.com/privacy-policy#developer",
    "reachable": true,
    "sha256": "cc454c1ebc3314bc3dda081d43221f1345e76eca475c86517a9044cb4c801695",
    "size_bytes": 4559470,
    "static_url": "http://pride.kitsaptransit.com/gtfs/google_transit.zip"
  },
  "generated_at": "2026-06-27T00:00:00+00:00",
  "geo": {
    "bbox": [
      -122.85144,
      47.41174,
      -122.33892,
      47.85481
    ],
    "lat": 47.58974,
    "lon": -122.62968,
    "stop_count": 1323
  },
  "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": [
      "20"
    ],
    "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 77 days.",
        "key": "current",
        "status": "ready"
      }
    ],
    "status": "ready",
    "summary": "This feed looks ready for your NTD certification: published at a public URL, valid, and current. The official check is still your D-10 certification."
  },
  "overall": {
    "grade": "C",
    "margin_to_lower_band": 1.5,
    "margin_to_next_band": 8.5,
    "score": 71.5
  },
  "recommendations": [
    {
      "code": "scorecard_route_color_low_contrast",
      "count": 15,
      "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": "15 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (500, 501, 119, 186, 219, and more).",
      "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": 726,
      "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": "726 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"Southworth & Banner\", \"Harper Church P&R\", \"Colchester & Main 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": 1323,
    "findings": [
      {
        "code": "scorecard_single_stop_trips",
        "count": 5,
        "effort": "Usually an export setting or a stop_times mapping in your software.",
        "fix": "Check your scheduling export: every trip should list each stop it calls at, in order, with times.",
        "owner": "Likely your export tool",
        "points": 0.0,
        "severity": "WARNING",
        "what": "5 of 7485 trips list fewer than two stops.",
        "why": "A trip with one stop has no leg a rider can ride; trip planners can't route anyone on it, so the service effectively does not exist."
      }
    ],
    "orphan_stops": 0,
    "single_stop_trips": 5,
    "trips_total": 7485
  },
  "rubric_version": "1.1",
  "schema_version": "1.4",
  "snapshot_date": "2026-07-09",
  "top_fixes": [
    {
      "code": "scorecard_rt_trip_updates_unreachable",
      "count": 1,
      "effort": "Usually a vendor support ticket.",
      "fix": "Check the trip updates endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.",
      "owner": "",
      "points": 8.3,
      "rank": 1,
      "severity": "ERROR",
      "what": "The trip updates realtime feed failed during sampling.",
      "why": "When this feed is down, riders see scheduled times presented as if they were live."
    },
    {
      "code": "scorecard_rt_vehicle_positions_unreachable",
      "count": 1,
      "effort": "Usually a vendor support ticket.",
      "fix": "Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.",
      "owner": "",
      "points": 8.3,
      "rank": 2,
      "severity": "ERROR",
      "what": "The vehicle positions realtime feed failed during sampling.",
      "why": "When this feed is down, riders see scheduled times presented as if they were live."
    },
    {
      "code": "scorecard_wheelchair_boarding_unknown",
      "count": 1323,
      "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": "1323 of 1323 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"
}