{
  "agency": {
    "id": "county-connection-cccta-2421",
    "name": "County Connection (CCCTA)"
  },
  "autofix": {
    "available": false
  },
  "categories": {
    "completeness": {
      "details": {
        "accessibility": {
          "measures": "presence_not_usability",
          "score": 90.4,
          "stops_marked_accessible_pct": 84.4,
          "stops_marked_not_accessible_pct": 0.2,
          "stops_stated_pct": 84.6,
          "trips_stated_pct": 100.0
        },
        "accessibility_measures": "presence_not_usability",
        "components": {
          "contact": 7.5,
          "fares": 15.0,
          "headsigns": 15.0,
          "stop_names": 15.0,
          "wheelchair_stops": 21.1,
          "wheelchair_trips": 15.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": true,
          "has_step_free": false,
          "pathway_count": 0
        },
        "stops": 948,
        "trips": 1498,
        "wheelchair_accessible_pct": 100.0,
        "wheelchair_boarding_pct": 84.6,
        "wheelchair_marked_accessible_pct": 84.4,
        "wheelchair_marked_not_accessible_pct": 0.2
      },
      "findings": [
        {
          "code": "scorecard_wheelchair_boarding_unknown",
          "count": 146,
          "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": 3.9,
          "severity": "WARNING",
          "what": "146 of 948 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_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."
        },
        {
          "code": "scorecard_station_no_pathways",
          "count": 1,
          "effort": "Worth it for multi-level or large stations; flat stops don't need it.",
          "fix": "Add pathways.txt connecting entrances, platforms, and any elevators, with a level for each.",
          "owner": "",
          "points": 0.0,
          "severity": "WARNING",
          "what": "This feed models stations or entrances but has no pathways.txt.",
          "why": "Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users."
        }
      ],
      "name": "completeness",
      "score": 88.6,
      "status": "measured",
      "summary": "85% of stops state wheelchair accessibility (84% 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": 2,
          "WARNING": 68086
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "equal_shape_distance_same_coordinates",
          "count": 60889,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'equal_shape_distance_same_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 8.0,
          "severity": "WARNING",
          "what": "Equal shape distance same coordinates (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "equal_shape_distance_diff_coordinates_distance_below_threshold",
          "count": 6996,
          "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": 8.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": "mixed_case_recommended_field",
          "count": 134,
          "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": 8.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": "missing_recommended_field",
          "count": 37,
          "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": "unused_shape",
          "count": 29,
          "effort": "One setting.",
          "fix": "Enable 'remove unused shapes' (or similar) in your export tool.",
          "owner": "Likely your export tool",
          "points": 6.0,
          "severity": "WARNING",
          "what": "The feed contains route shapes no trip uses.",
          "why": "Harmless to riders, but it bloats the feed and suggests stale export data."
        },
        {
          "code": "missing_recommended_file",
          "count": 1,
          "effort": "One small file, set once in export settings.",
          "fix": "Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date.",
          "owner": "Likely your export tool",
          "points": 4.0,
          "severity": "WARNING",
          "what": "A recommended GTFS file (usually feed_info.txt) is missing.",
          "why": "feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale."
        },
        {
          "code": "unknown_file",
          "count": 2,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'unknown_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 0.5,
          "severity": "INFO",
          "what": "Unknown file (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        }
      ],
      "name": "correctness",
      "score": 59.5,
      "status": "measured",
      "summary": "The MobilityData validator flagged 7 kinds of issue across 68088 instances (0 error, 68086 warning, 2 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": 30,
        "feed_end_date": null,
        "feed_start_date": null,
        "feed_version": null,
        "has_feed_info": false,
        "last_service_date": "2026-08-08",
        "seasonal_boundary": false,
        "service_type": "fixed"
      },
      "findings": [
        {
          "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 (the file itself is absent)",
          "why": "Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates."
        }
      ],
      "name": "freshness",
      "score": 35.0,
      "status": "measured",
      "summary": "Service data covers the next 30 days.",
      "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 covers the next 41 days.",
        "key": "current",
        "met": true
      },
      {
        "detail": "States wheelchair access on 85% 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. States wheelchair access on 85% 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": "71529d3f80dfa0c8383e1700cd9d65feceb9c47df81bae53493152946334b26c",
    "size_bytes": 1388383,
    "static_url": "https://countyconnection.com/GTFS/google_transit.zip"
  },
  "generated_at": "2026-06-28T00:00:00+00:00",
  "geo": {
    "bbox": [
      -122.19179,
      37.65911,
      -121.77813,
      38.01941
    ],
    "lat": 37.94676,
    "lon": -122.04665,
    "stop_count": 948
  },
  "ntd_id_alignment": {
    "detail": "Your feed uses agency_id 2; the NTD asks for your five-digit NTD ID (90078) so the feed lines up with your record.",
    "feed_agency_ids": [
      "2"
    ],
    "fix": "Change the agency_id to 90078 in agency.txt and update the matching agency_id in routes.txt.",
    "ntd_id": "90078",
    "status": "mismatch"
  },
  "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 41 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": "D",
    "margin_to_lower_band": 2.5,
    "margin_to_next_band": 7.5,
    "score": 62.5
  },
  "recommendations": [
    {
      "code": "scorecard_route_color_low_contrast",
      "count": 10,
      "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": "10 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (11, 14, 16, 311, 314, 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_station_missing_step_free_data",
      "count": 2,
      "effort": "Worth it for multi-level or large stations; flat stops don't need it.",
      "fix": "Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.",
      "owner": "",
      "points": 0.0,
      "severity": "WARNING",
      "what": "This feed models stations or entrances but has no pathways.txt and levels.txt.",
      "why": "Without pathways and levels, a wheelchair user can't tell whether a step-free route exists inside the station, and trip planners can't route anyone through it."
    }
  ],
  "recompute": {
    "as_of": "2026-07-09",
    "feed_fetched_date": "2026-07-08",
    "kind": "freshness"
  },
  "routability": {
    "boardable_stops": 941,
    "findings": [],
    "orphan_stops": 0,
    "single_stop_trips": 0,
    "trips_total": 1498
  },
  "rubric_version": "1.1",
  "schema_version": "1.4",
  "snapshot_date": "2026-07-09",
  "top_fixes": [
    {
      "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,
      "rank": 1,
      "severity": "WARNING",
      "what": "feed_info.txt is missing its start/end dates (the file itself is absent)",
      "why": "Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates."
    },
    {
      "code": "equal_shape_distance_same_coordinates",
      "count": 60889,
      "effort": "Varies.",
      "fix": "Review the rule documentation for 'equal_shape_distance_same_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
      "owner": "",
      "points": 8.0,
      "rank": 2,
      "severity": "WARNING",
      "what": "Equal shape distance same coordinates (flagged by the MobilityData validator).",
      "why": "See the linked rule for what this affects."
    },
    {
      "code": "equal_shape_distance_diff_coordinates_distance_below_threshold",
      "count": 6996,
      "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": 8.0,
      "rank": 3,
      "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."
    }
  ],
  "validator_version": "8.0.1"
}