{
  "agency": {
    "id": "seattle-children-s-hospital-shuttle",
    "name": "Seattle Children's Hospital Shuttle"
  },
  "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": 7.5,
          "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": 13,
        "trips": 757,
        "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": 13,
          "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": "13 of 13 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": 757,
          "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": "757 of 757 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_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."
        }
      ],
      "name": "completeness",
      "score": 52.5,
      "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": 10,
        "instances_by_severity": {
          "ERROR": 9,
          "INFO": 7,
          "WARNING": 13
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "block_trips_with_overlapping_stop_times",
          "count": 9,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 18.0,
          "severity": "ERROR",
          "what": "Block trips with overlapping stop times (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "stop_without_stop_time",
          "count": 4,
          "effort": "A review pass in your scheduling software.",
          "fix": "Remove retired stops from the export, or add them back to the trips that should serve them.",
          "owner": "Likely your export tool",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Some stops exist in the feed but no trip ever stops at them.",
          "why": "Riders may walk to a stop where no bus is scheduled to arrive."
        },
        {
          "code": "missing_recommended_field",
          "count": 3,
          "effort": "A field at a time; not urgent.",
          "fix": "Review the flagged fields and fill in the ones your riders would use.",
          "owner": "",
          "points": 4.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": "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": "missing_feed_contact_email_and_url",
          "count": 1,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Missing feed contact email and url (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "mixed_case_recommended_field",
          "count": 1,
          "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": 4.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": "stop_too_far_from_shape",
          "count": 1,
          "effort": "A few minutes per flagged stop.",
          "fix": "Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced.",
          "owner": "Likely your export tool",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Some stops sit far from the route line they belong to.",
          "why": "Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner."
        },
        {
          "code": "stops_match_shape_out_of_order",
          "count": 1,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'stops_match_shape_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Stops match shape out of order (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "trip_coverage_not_active_for_next7_days",
          "count": 1,
          "effort": "One setting in most export tools.",
          "fix": "Trim past service periods the next time you export.",
          "owner": "Likely your export tool",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Many of the feed's trips don't run at all in the next 7 days.",
          "why": "It usually means old service periods are still in the export, making the feed bigger and harder to check."
        },
        {
          "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."
        }
      ],
      "name": "correctness",
      "score": 49.2,
      "status": "measured",
      "summary": "The MobilityData validator flagged 10 kinds of issue across 29 instances (9 error, 13 warning, 7 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": -738,
        "feed_end_date": null,
        "feed_start_date": null,
        "feed_version": "PDT: 15-Jun-2023 02:48",
        "has_feed_info": true,
        "last_service_date": "2024-07-01",
        "seasonal_boundary": false,
        "service_type": "fixed"
      },
      "findings": [
        {
          "code": "scorecard_feed_expired",
          "count": 1,
          "effort": "Usually one export setting; export on a schedule so it never lapses again.",
          "fix": "Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.",
          "owner": "Likely your export tool",
          "points": 100.0,
          "severity": "ERROR",
          "what": "Service data ended 738 day(s) ago.",
          "why": "When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist."
        },
        {
          "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",
          "why": "Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates."
        }
      ],
      "name": "freshness",
      "score": 0.0,
      "status": "measured",
      "summary": "Service data ended 738 day(s) ago. Trip planners have likely already dropped this feed.",
      "weight": 0.2
    },
    "realtime": {
      "name": "realtime",
      "status": "not_yet_measured",
      "summary": "This agency publishes realtime, but the feed needs an access key we don't have yet. Nothing here counts against the grade.",
      "weight": 0.2
    }
  },
  "conformance": {
    "awarded": false,
    "criteria": [
      {
        "detail": "1 validator error to resolve.",
        "key": "valid",
        "met": false
      },
      {
        "detail": "Service data expired 726 days ago.",
        "key": "current",
        "met": false
      },
      {
        "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. 1 validator error to resolve. Service data expired 726 days ago. States wheelchair access on 0% of stops and 0% 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": "92527f870859bb90d61fe8a69620016882e98aaac86dbca9b62f986489b7e51f",
    "size_bytes": 25533,
    "static_url": "https://gtfs.sound.obaweb.org/prod/98_gtfs.zip"
  },
  "generated_at": "2026-06-27T00:00:00+00:00",
  "geo": {
    "bbox": [
      -122.31747,
      47.65008,
      -122.2568,
      47.67873
    ],
    "lat": 47.66353,
    "lon": -122.28302,
    "stop_count": 13
  },
  "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": [
      "98"
    ],
    "status": "unknown"
  },
  "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 expired 726 days ago, so FTA would find the link out of date.",
        "key": "current",
        "status": "not_ready"
      }
    ],
    "status": "not_ready",
    "summary": "Resolve this before you certify on the D-10. 1 validator error to resolve. Service data expired 726 days ago, so FTA would find the link out of date."
  },
  "overall": {
    "grade": "F",
    "margin_to_lower_band": 37.9,
    "margin_to_next_band": 22.1,
    "score": 37.9
  },
  "recommendations": [
    {
      "code": "scorecard_stop_name_needs_tts",
      "count": 7,
      "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": "7 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"NE 45th St & Union Bay Pl NE\", \"Montlake Blvd NE & NE Pacific Pl - Bay 5\", \"NE 45th St & Mary Gates Memorial Dr NE\", 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": 13,
    "findings": [
      {
        "code": "scorecard_orphan_stops",
        "count": 4,
        "effort": "A cleanup pass in your scheduling software.",
        "fix": "Remove stops no route serves, or add the trips that should call at them.",
        "owner": "Likely your export tool",
        "points": 0.0,
        "severity": "INFO",
        "what": "4 of 13 boardable stops are never served by any trip.",
        "why": "Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data."
      }
    ],
    "orphan_stops": 4,
    "single_stop_trips": 0,
    "trips_total": 757
  },
  "rubric_version": "1.1",
  "schema_version": "1.4",
  "snapshot_date": "2026-07-09",
  "top_fixes": [
    {
      "code": "scorecard_feed_expired",
      "count": 1,
      "effort": "Usually one export setting; export on a schedule so it never lapses again.",
      "fix": "Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.",
      "owner": "Likely your export tool",
      "points": 100.0,
      "rank": 1,
      "severity": "ERROR",
      "what": "Service data ended 738 day(s) ago.",
      "why": "When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist."
    },
    {
      "code": "block_trips_with_overlapping_stop_times",
      "count": 9,
      "effort": "Varies.",
      "fix": "Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
      "owner": "",
      "points": 18.0,
      "rank": 2,
      "severity": "ERROR",
      "what": "Block trips with overlapping stop times (flagged by the MobilityData validator).",
      "why": "See the linked rule for what this affects."
    },
    {
      "code": "scorecard_wheelchair_boarding_unknown",
      "count": 13,
      "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": "13 of 13 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"
}