{
  "agency": {
    "id": "metro-transit-205",
    "name": "Metro Transit"
  },
  "autofix": {
    "available": false
  },
  "categories": {
    "completeness": {
      "details": {
        "accessibility": {
          "measures": "presence_not_usability",
          "score": 99.8,
          "stops_marked_accessible_pct": 86.8,
          "stops_marked_not_accessible_pct": 12.9,
          "stops_stated_pct": 99.7,
          "trips_stated_pct": 100.0
        },
        "accessibility_measures": "presence_not_usability",
        "components": {
          "contact": 15.0,
          "fares": 0.0,
          "headsigns": 15.0,
          "stop_names": 15.0,
          "wheelchair_stops": 24.9,
          "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": true,
          "has_levels": true,
          "has_pathways": true,
          "has_stations": true,
          "has_step_free": true,
          "pathway_count": 42
        },
        "stops": 8244,
        "trips": 24910,
        "wheelchair_accessible_pct": 100.0,
        "wheelchair_boarding_pct": 99.7,
        "wheelchair_marked_accessible_pct": 86.8,
        "wheelchair_marked_not_accessible_pct": 12.9
      },
      "findings": [
        {
          "code": "scorecard_wheelchair_boarding_unknown",
          "count": 26,
          "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.1,
          "severity": "WARNING",
          "what": "26 of 8244 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_station_pathways",
          "count": 42,
          "effort": "None.",
          "fix": "No action needed.",
          "owner": "",
          "points": 0.0,
          "severity": "INFO",
          "what": "This feed describes station pathways, including step-free (elevator) routes.",
          "why": "Riders can be routed through the station, and wheelchair users can see whether a step-free route exists."
        }
      ],
      "name": "completeness",
      "score": 84.9,
      "status": "measured",
      "summary": "100% of stops state wheelchair accessibility (87% marked accessible, 13% 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": 9,
        "instances_by_severity": {
          "ERROR": 0,
          "INFO": 25045,
          "WARNING": 101
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "unused_shape",
          "count": 76,
          "effort": "One setting.",
          "fix": "Enable 'remove unused shapes' (or similar) in your export tool.",
          "owner": "Likely your export tool",
          "points": 8.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": "equal_shape_distance_same_coordinates",
          "count": 21,
          "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": 6.0,
          "severity": "WARNING",
          "what": "Equal shape distance same coordinates (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "expired_calendar",
          "count": 3,
          "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": "same_name_and_description_for_route",
          "count": 1,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'same_name_and_description_for_route' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Same name and description for route (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "unsorted_stop_times",
          "count": 24910,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'unsorted_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 1.0,
          "severity": "INFO",
          "what": "Unsorted stop times (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "platform_without_parent_station",
          "count": 120,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'platform_without_parent_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 1.0,
          "severity": "INFO",
          "what": "Platform without parent station (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "unknown_column",
          "count": 7,
          "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": "big_gap_in_service",
          "count": 6,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'big_gap_in_service' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 0.8,
          "severity": "INFO",
          "what": "Big gap in service (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "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": 74.0,
      "status": "measured",
      "summary": "The MobilityData validator flagged 9 kinds of issue across 25146 instances (0 error, 101 warning, 25045 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": 35,
        "feed_end_date": "2026-08-21",
        "feed_start_date": "2026-06-27",
        "feed_version": "1782334167",
        "has_feed_info": true,
        "last_service_date": "2026-08-14",
        "seasonal_boundary": false,
        "service_type": "fixed"
      },
      "findings": [],
      "name": "freshness",
      "score": 58.3,
      "status": "measured",
      "summary": "Service data covers the next 35 days.",
      "weight": 0.2
    },
    "realtime": {
      "details": {
        "coverage_pct": 96.4,
        "covered_trips": 160,
        "drift": {
          "median_seconds": 7,
          "observations": 12848,
          "on_time_share_pct": 63.1,
          "p90_abs_seconds": 299
        },
        "kinds_reachable": 2,
        "rt_freshness": "fresh",
        "samples": 9,
        "scheduled_trips_in_window": 166,
        "vehicles_checked": 705,
        "vehicles_on_route_pct": 78.2,
        "worst_lag_seconds": 16
      },
      "findings": [
        {
          "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": 6,
          "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": 1.3,
          "severity": "WARNING",
          "what": "6 of 166 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."
        },
        {
          "code": "scorecard_rt_vehicles_off_route",
          "count": 154,
          "effort": "A vendor support ticket with the trip ids attached.",
          "fix": "Ask your AVL vendor to check vehicle-to-trip assignments for the flagged trips.",
          "owner": "",
          "points": 3.3,
          "severity": "WARNING",
          "what": "154 of 705 sampled vehicle positions were far from their assigned route (worst: 11520531 m).",
          "why": "A bus shown off its route usually means a wrong trip assignment; riders watch their bus drive the wrong streets."
        }
      ],
      "name": "realtime",
      "score": 87.1,
      "status": "measured",
      "summary": "Sampled 9 times: 2 of 3 feeds healthy; 96.4% of scheduled trips had live predictions; 78.2% of vehicles on their route; predictions ran a median of 7s behind schedule.",
      "weight": 0.2
    }
  },
  "conformance": {
    "awarded": true,
    "criteria": [
      {
        "detail": "Passes validation with no errors.",
        "key": "valid",
        "met": true
      },
      {
        "detail": "Service data covers the next 45 days.",
        "key": "current",
        "met": true
      },
      {
        "detail": "States wheelchair access on 100% of stops and 100% of trips.",
        "key": "accessible",
        "met": true
      }
    ],
    "status": "awarded",
    "summary": "This feed earns the conformance mark: valid, current, and stating wheelchair access on nearly every stop and trip."
  },
  "feed": {
    "license_note": "No stated data license in the Mobility Database; verify before publishing.",
    "reachable": true,
    "sha256": "79b0cbca38e756a25ad442ec2b49735fb39a995df7d6046e67f59c5e76ee078f",
    "size_bytes": 23810525,
    "static_url": "https://svc.metrotransit.org/mtgtfs/gtfs.zip"
  },
  "generated_at": "2026-06-30T00:00:00+00:00",
  "geo": {
    "bbox": [
      -93.73042,
      44.70708,
      -92.8059,
      45.32974
    ],
    "lat": 44.97528,
    "lon": -93.26292,
    "stop_count": 8244
  },
  "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": [
      "0",
      "1",
      "2",
      "4",
      "5",
      "6",
      "10",
      "11"
    ],
    "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 45 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": 6.2,
    "margin_to_next_band": 3.8,
    "score": 76.2
  },
  "recommendations": [
    {
      "code": "scorecard_route_color_low_contrast",
      "count": 7,
      "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": "7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (134, 156, 686, 765, 802, 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": 8136,
      "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": "8136 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"Chicago Ave S & 8th St S\", \"Chicago Ave S & 17th St E\", \"Chicago Ave S & 18th St E\", 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-10",
    "feed_fetched_date": "2026-06-30",
    "kind": "freshness"
  },
  "routability": {
    "boardable_stops": 8216,
    "findings": [],
    "orphan_stops": 0,
    "single_stop_trips": 0,
    "trips_total": 24910
  },
  "rubric_version": "1.1",
  "schema_version": "1.4",
  "snapshot_date": "2026-07-10",
  "top_fixes": [
    {
      "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,
      "rank": 1,
      "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_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": "unused_shape",
      "count": 76,
      "effort": "One setting.",
      "fix": "Enable 'remove unused shapes' (or similar) in your export tool.",
      "owner": "Likely your export tool",
      "points": 8.0,
      "rank": 3,
      "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."
    }
  ],
  "validator_version": "8.0.1"
}