{
  "agency": {
    "id": "clackco-connects-clackamas-county-2741",
    "name": "ClackCo Connects (Clackamas County) Flex",
    "subdivision_code": "US-OR",
    "subdivision_name": "Oregon"
  },
  "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": 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": true,
          "booking_rule_count": 4,
          "has_booking_rules": true,
          "has_flex": true
        },
        "has_fares": true,
        "headsign_applicable_trips": 90,
        "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": 82,
        "translations": {
          "feed_lang": "en",
          "has_translations": false,
          "languages": [],
          "translated_tables": [],
          "translation_count": 0
        },
        "trips": 90,
        "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": 82,
          "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": "82 of 82 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": 90,
          "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": "90 of 90 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_flex_service",
          "count": 1,
          "effort": "None.",
          "fix": "No action needed.",
          "owner": "",
          "points": 0.0,
          "severity": "INFO",
          "what": "This feed includes flexible (demand-responsive) service, and riders are told how to book it.",
          "why": "Dial-a-ride and zone service are described for trip planners, not just fixed routes."
        }
      ],
      "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": 5,
        "instances_by_severity": {
          "ERROR": 38,
          "INFO": 26,
          "WARNING": 8
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "invalid_pickup_drop_off_window",
          "count": 38,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'invalid_pickup_drop_off_window' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 18.0,
          "severity": "ERROR",
          "what": "Invalid pickup drop off window (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "fast_travel_between_consecutive_stops",
          "count": 8,
          "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 move faster between stops than a bus can.",
          "why": "Usually a typo'd stop time; riders get arrival times no bus can meet."
        },
        {
          "code": "unknown_column",
          "count": 17,
          "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.8,
          "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."
        },
        {
          "code": "unknown_file",
          "count": 8,
          "effort": "A quick look at the flagged file.",
          "fix": "Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra.",
          "owner": "",
          "points": 0.8,
          "severity": "INFO",
          "what": "The feed includes a file that is not part of the GTFS spec.",
          "why": "Apps ignore files they don't know, and a stray file can hide a misspelled standard file name."
        },
        {
          "code": "service_window_outside_feed_period",
          "count": 1,
          "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": 74.0,
      "status": "measured",
      "summary": "The MobilityData validator flagged 5 kinds of issue across 72 instances (38 error, 8 warning, 26 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": 100,
        "effective_expiry_date": "2026-12-01",
        "feed_end_date": "2026-12-01",
        "feed_start_date": "2026-05-21",
        "feed_version": "UTC: 21-May-2026 15:29",
        "has_feed_info": true,
        "last_service_date": "2026-12-01",
        "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 100 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": "1 validator error to resolve.",
        "key": "valid",
        "met": false
      },
      {
        "detail": "Service data covers the next 100 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": "Two requirements remain for this feed to earn the conformance mark. 1 validator error to resolve. 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": "19f89b3711a8203fd12cfaaa888baf462c2d1f1bc1b44c1b2b1d3e04b5417c8d",
    "size_bytes": 145889,
    "source_provenance": "unverified",
    "static_url": "https://oregon-gtfs.trilliumtransit.com/gtfs_data/clackamascounty-or-us/clackamascounty-or-us--flex-v2.zip"
  },
  "fetch": {
    "final_url": "https://oregon-gtfs.trilliumtransit.com/gtfs_data/clackamascounty-or-us/clackamascounty-or-us--flex-v2.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": [
      -122.62561,
      45.28611,
      -122.33389,
      45.43618
    ],
    "lat": 45.35238,
    "lon": -122.58295,
    "stop_count": 82
  },
  "mode_profile": {
    "ferry_only": false,
    "graded": false,
    "has_ferry": false,
    "is_multimodal": false,
    "measured": true,
    "modes": [
      {
        "key": "bus",
        "label": "Bus",
        "route_count": 4,
        "trip_count": 90,
        "trip_share_pct": 100.0
      }
    ],
    "primary_mode": "bus",
    "primary_mode_label": "Bus",
    "route_count": 4,
    "trip_count": 90
  },
  "ntd_id_alignment": {
    "detail": "Your feed's agency_id is 1807; your National Transit Database ID is 00363. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score.",
    "feed_agency_ids": [
      "1807"
    ],
    "fix": "Confirm that P-50 crosswalks agency_id 1807 to NTD ID 00363, and keep the feed value stable. Do not change it solely to make the two values equal.",
    "ntd_id": "00363",
    "status": "mismatch"
  },
  "ntd_readiness": {
    "pillars": [
      {
        "detail": "Published at a public URL.",
        "key": "published",
        "status": "ready"
      },
      {
        "detail": "1 validator error to resolve.",
        "key": "valid",
        "status": "at_risk"
      },
      {
        "detail": "Service data covers the next 113 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": "at_risk",
    "summary": "This feed is close to NTD-ready. 1 validator error to resolve."
  },
  "overall": {
    "grade": "C",
    "margin_to_lower_band": 6.1,
    "margin_to_next_band": 3.9,
    "score": 76.1
  },
  "recommendations": [
    {
      "category": "accessibility",
      "code": "scorecard_stop_name_needs_tts",
      "count": 50,
      "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": "50 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"5th & Monroe\", \"Linn & Oak\", \"Molalla & Oregon City Post Office\", 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": 82,
    "findings": [],
    "orphan_stops": 0,
    "single_stop_trips": 0,
    "trips_total": 90
  },
  "route_map": {
    "drawn_route_count": 4,
    "has_shapes": true,
    "path": "data/artifacts/clackco-connects-clackamas-county-2741/geometry.geojson",
    "route_count": 4,
    "routes": [
      {
        "color": "E31479",
        "color_name": "pink",
        "has_shape": true,
        "id": "19558",
        "label": "Oregon City Shuttle",
        "long": "Oregon City Shuttle",
        "short": "",
        "text_color": "000000",
        "type_label": "Bus"
      },
      {
        "color": "E31479",
        "color_name": "pink",
        "has_shape": true,
        "id": "19559",
        "label": "Clackamas Industrial Area Shuttle",
        "long": "Clackamas Industrial Area Shuttle",
        "short": "",
        "text_color": "000000",
        "type_label": "Bus"
      },
      {
        "color": "E31479",
        "color_name": "pink",
        "has_shape": true,
        "id": "76435",
        "label": "CCCXpress",
        "long": "CCCXpress",
        "short": "",
        "text_color": "000000",
        "type_label": "Bus"
      },
      {
        "color": "E31479",
        "color_name": "pink",
        "has_shape": true,
        "id": "76895",
        "label": "Estacada Shuttle",
        "long": "Estacada Shuttle",
        "short": "",
        "text_color": "000000",
        "type_label": "Bus"
      }
    ],
    "stop_count": 82,
    "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 90 trips have a shape in shapes.txt.",
    "status": "ready",
    "total_trips": 90,
    "trips_with_shape": 90
  },
  "snapshot_date": "2026-08-23",
  "top_fixes": [
    {
      "code": "invalid_pickup_drop_off_window",
      "count": 38,
      "effort": "Varies.",
      "fix": "Review the rule documentation for 'invalid_pickup_drop_off_window' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
      "owner": "",
      "points": 18.0,
      "rank": 1,
      "severity": "ERROR",
      "what": "Invalid pickup drop off window (flagged by the MobilityData validator).",
      "why": "See the linked rule for what this affects."
    },
    {
      "code": "scorecard_wheelchair_boarding_unknown",
      "count": 82,
      "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": 2,
      "severity": "WARNING",
      "what": "82 of 82 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": 90,
      "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": 3,
      "severity": "WARNING",
      "what": "90 of 90 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."
    }
  ],
  "validator_version": "8.0.1"
}