{
  "agency": {
    "id": "marin-transit-2937",
    "name": "Marin Transit"
  },
  "autofix": {
    "available": false
  },
  "categories": {
    "completeness": {
      "details": {
        "accessibility": {
          "measures": "presence_not_usability",
          "score": 87.6,
          "stops_marked_accessible_pct": 70.6,
          "stops_marked_not_accessible_pct": 29.4,
          "stops_stated_pct": 100.0,
          "trips_stated_pct": 67.0
        },
        "accessibility_measures": "presence_not_usability",
        "components": {
          "contact": 15.0,
          "fares": 15.0,
          "headsigns": 15.0,
          "stop_names": 15.0,
          "wheelchair_stops": 25.0,
          "wheelchair_trips": 10.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": 545,
        "trips": 1612,
        "wheelchair_accessible_pct": 67.0,
        "wheelchair_boarding_pct": 100.0,
        "wheelchair_marked_accessible_pct": 70.6,
        "wheelchair_marked_not_accessible_pct": 29.4
      },
      "findings": [
        {
          "code": "scorecard_wheelchair_accessible_unknown",
          "count": 532,
          "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": 5.0,
          "severity": "WARNING",
          "what": "532 of 1612 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_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": 95.0,
      "status": "measured",
      "summary": "100% of stops state wheelchair accessibility (71% marked accessible, 29% 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": 6,
        "instances_by_severity": {
          "ERROR": 55,
          "INFO": 8,
          "WARNING": 5
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "trip_distance_exceeds_shape_distance",
          "count": 53,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 24.0,
          "severity": "ERROR",
          "what": "Trip distance exceeds shape distance (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "missing_required_column",
          "count": 2,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'missing_required_column' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 12.0,
          "severity": "ERROR",
          "what": "Missing required column (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "expired_calendar",
          "count": 5,
          "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": "unknown_file",
          "count": 6,
          "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.8,
          "severity": "INFO",
          "what": "Unknown file (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "feed_valid_beyond_total_service_window",
          "count": 1,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'feed_valid_beyond_total_service_window' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 0.5,
          "severity": "INFO",
          "what": "Feed valid beyond total service window (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "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": 58.2,
      "status": "measured",
      "summary": "The MobilityData validator flagged 6 kinds of issue across 68 instances (55 error, 5 warning, 8 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": 31,
        "feed_end_date": "2027-01-09",
        "feed_start_date": "2026-04-12",
        "feed_version": "UTC: 04-Feb-2026 00:08",
        "has_feed_info": true,
        "last_service_date": "2026-08-09",
        "seasonal_boundary": false,
        "service_type": "fixed"
      },
      "findings": [],
      "name": "freshness",
      "score": 51.7,
      "status": "measured",
      "summary": "Service data covers the next 31 days.",
      "weight": 0.2
    },
    "realtime": {
      "details": {
        "coverage_pct": 0.0,
        "covered_trips": 0,
        "kinds_reachable": 0,
        "rt_freshness": null,
        "samples": 9,
        "scheduled_trips_in_window": 15,
        "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_service_alerts_unreachable",
          "count": 1,
          "effort": "Usually a vendor support ticket.",
          "fix": "Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.",
          "owner": "",
          "points": 8.3,
          "severity": "ERROR",
          "what": "The service alerts realtime feed failed during sampling.",
          "why": "When this feed is down, riders see scheduled times presented as if they were live."
        },
        {
          "code": "scorecard_rt_trip_coverage",
          "count": 15,
          "effort": "A vendor data-mapping question.",
          "fix": "Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs.",
          "owner": "",
          "points": 35.0,
          "severity": "WARNING",
          "what": "15 of 15 trips scheduled during the sampling window had no live predictions.",
          "why": "Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates."
        }
      ],
      "name": "realtime",
      "score": 0.0,
      "status": "measured",
      "summary": "Sampled 9 times: 0 of 3 feeds healthy; 0.0% of scheduled trips had live predictions.",
      "weight": 0.2
    }
  },
  "conformance": {
    "awarded": false,
    "criteria": [
      {
        "detail": "2 validator errors to resolve.",
        "key": "valid",
        "met": false
      },
      {
        "detail": "Service data covers the next 43 days.",
        "key": "current",
        "met": true
      },
      {
        "detail": "States wheelchair access on 100% of stops and 67% of trips; the mark needs 90% of each.",
        "key": "accessible",
        "met": false
      }
    ],
    "status": "not_yet",
    "summary": "This feed is close to the conformance mark. 2 validator errors to resolve. States wheelchair access on 100% of stops and 67% 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": "d03b333bc4558f3ea80a473091c4af59711907a5107da8f2cfab0ce733ee506e",
    "size_bytes": 1386563,
    "static_url": "https://marintransit.gov/data/google_transit.zip"
  },
  "generated_at": "2026-06-27T00:00:00+00:00",
  "geo": {
    "bbox": [
      -122.85152,
      37.85714,
      -122.45614,
      38.12453
    ],
    "lat": 37.97664,
    "lon": -122.53646,
    "stop_count": 545
  },
  "ntd_id_alignment": {
    "detail": "Your feed uses agency_id 33; the NTD asks for your five-digit NTD ID (90234) so the feed lines up with your record.",
    "feed_agency_ids": [
      "33"
    ],
    "fix": "Change the agency_id to 90234 in agency.txt and update the matching agency_id in routes.txt.",
    "ntd_id": "90234",
    "status": "mismatch"
  },
  "ntd_readiness": {
    "pillars": [
      {
        "detail": "Published at a public URL.",
        "key": "published",
        "status": "ready"
      },
      {
        "detail": "2 validator errors to resolve.",
        "key": "valid",
        "status": "at_risk"
      },
      {
        "detail": "Service data covers the next 43 days.",
        "key": "current",
        "status": "ready"
      }
    ],
    "status": "at_risk",
    "summary": "This feed is close to NTD-ready. 2 validator errors to resolve."
  },
  "overall": {
    "grade": "F",
    "margin_to_lower_band": 54.5,
    "margin_to_next_band": 5.5,
    "score": 54.5
  },
  "recommendations": [
    {
      "code": "scorecard_route_color_low_contrast",
      "count": 8,
      "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": "8 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (71, 219, 228, 245, 49, 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": 543,
    "findings": [],
    "orphan_stops": 0,
    "single_stop_trips": 0,
    "trips_total": 1612
  },
  "rubric_version": "1.1",
  "schema_version": "1.4",
  "snapshot_date": "2026-07-09",
  "top_fixes": [
    {
      "code": "trip_distance_exceeds_shape_distance",
      "count": 53,
      "effort": "Varies.",
      "fix": "Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
      "owner": "",
      "points": 24.0,
      "rank": 1,
      "severity": "ERROR",
      "what": "Trip distance exceeds shape distance (flagged by the MobilityData validator).",
      "why": "See the linked rule for what this affects."
    },
    {
      "code": "missing_required_column",
      "count": 2,
      "effort": "Varies.",
      "fix": "Review the rule documentation for 'missing_required_column' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
      "owner": "",
      "points": 12.0,
      "rank": 2,
      "severity": "ERROR",
      "what": "Missing required column (flagged by the MobilityData validator).",
      "why": "See the linked rule for what this affects."
    },
    {
      "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": 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."
    }
  ],
  "validator_version": "8.0.1"
}