{
  "agency": {
    "id": "mount-adams-transportation-service-580",
    "name": "Mount Adams Transportation Service"
  },
  "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": 15.0,
          "fares": 15.0,
          "headsigns": 10.1,
          "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": true
        },
        "has_fares": true,
        "headsign_pct": 67.6,
        "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": 77,
        "trips": 37,
        "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": 77,
          "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": "77 of 77 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": 37,
          "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": "37 of 37 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_missing_headsigns",
          "count": 12,
          "effort": "Usually a bulk edit in your scheduling software.",
          "fix": "Populate trip_headsign to match what the bus displays.",
          "owner": "Likely your export tool",
          "points": 4.9,
          "severity": "WARNING",
          "what": "12 of 37 trips have no headsign.",
          "why": "Riders at the stop can't tell which direction a bus is going."
        },
        {
          "code": "scorecard_flex_no_booking_rules",
          "count": 1,
          "effort": "A small file; one rule often covers the whole service.",
          "fix": "Add booking_rules.txt saying how far ahead and how to book (phone, app, or web).",
          "owner": "",
          "points": 0.0,
          "severity": "WARNING",
          "what": "This feed describes flexible (demand-responsive) service but has no booking_rules.txt.",
          "why": "Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service."
        }
      ],
      "name": "completeness",
      "score": 55.1,
      "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": 4,
        "instances_by_severity": {
          "ERROR": 0,
          "INFO": 43,
          "WARNING": 36
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "stop_without_stop_time",
          "count": 36,
          "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": 6.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": "unknown_column",
          "count": 34,
          "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": "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": "service_window_outside_feed_period",
          "count": 1,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'service_window_outside_feed_period' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 0.5,
          "severity": "INFO",
          "what": "Service window outside feed period (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        }
      ],
      "name": "correctness",
      "score": 92.0,
      "status": "measured",
      "summary": "The MobilityData validator flagged 4 kinds of issue across 79 instances (0 error, 36 warning, 43 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": 176,
        "feed_end_date": "2027-01-01",
        "feed_start_date": "2026-06-29",
        "feed_version": "UTC: 30-Jun-2026 05:12",
        "has_feed_info": true,
        "last_service_date": "2027-01-01",
        "seasonal_boundary": false,
        "service_type": "fixed"
      },
      "findings": [],
      "name": "freshness",
      "score": 100.0,
      "status": "measured",
      "summary": "Service data covers the next 176 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 185 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": "This feed is close to the conformance mark. 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": "06b7081261ebd4be78c8b30f3e8b9eb7fde7a8f6778f34ab4c6a7e9a31a3c4ec",
    "size_bytes": 287416,
    "static_url": "http://data.trilliumtransit.com/gtfs/mountadams-wa-us/mountadams-wa-us.zip"
  },
  "generated_at": "2026-06-30T00:00:00+00:00",
  "geo": {
    "bbox": [
      -122.65009,
      45.53347,
      -119.10209,
      46.59325
    ],
    "lat": 45.72232,
    "lon": -121.13871,
    "stop_count": 77
  },
  "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": [
      "1815"
    ],
    "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 185 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": "B",
    "margin_to_lower_band": 2.5,
    "margin_to_next_band": 7.5,
    "score": 82.5
  },
  "recommendations": [
    {
      "code": "scorecard_flex_completeness_no_booking_rules",
      "count": 1,
      "effort": "A small file; one rule often covers the whole service.",
      "fix": "Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).",
      "owner": "",
      "points": 0.0,
      "severity": "WARNING",
      "what": "Flex zones are published but no booking_rules.txt is present.",
      "why": "Riders can see the service area but not how to book, so they can't complete a trip."
    },
    {
      "code": "scorecard_stop_name_needs_tts",
      "count": 23,
      "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": "23 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"Pioneer Center and Senior Services 501 NE Washington Street, White Salmon\", \"Port Transfer Site Riverside Drive and N 1st Street, Hood River\", \"White Salmon/Hood River Bridge Park and Ride\", 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": 77,
    "findings": [
      {
        "code": "scorecard_orphan_stops",
        "count": 36,
        "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": "36 of 77 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": 36,
    "single_stop_trips": 0,
    "trips_total": 37
  },
  "route_map": {
    "drawn_route_count": 3,
    "has_shapes": true,
    "path": "data/artifacts/mount-adams-transportation-service-580/geometry.geojson",
    "route_count": 3,
    "routes": [
      {
        "color": "D38F2B",
        "color_name": "orange",
        "has_shape": true,
        "id": "19664",
        "label": "White Salmon to Hood River",
        "long": "White Salmon to Hood River",
        "short": "",
        "text_color": "000000",
        "type_label": "Bus"
      },
      {
        "color": "D38F2B",
        "color_name": "orange",
        "has_shape": true,
        "id": "19748",
        "label": "Goldendale to The Dalles",
        "long": "Goldendale to The Dalles",
        "short": "",
        "text_color": "000000",
        "type_label": "Bus"
      },
      {
        "color": "00BEFD",
        "color_name": "teal",
        "has_shape": true,
        "id": "77838",
        "label": "Lyle Connector",
        "long": "Lyle Connector",
        "short": "",
        "text_color": "000000",
        "type_label": "Bus"
      }
    ],
    "stop_count": 77,
    "stop_points_capped": false
  },
  "rubric_version": "1.1",
  "schema_version": "1.4",
  "snapshot_date": "2026-07-09",
  "top_fixes": [
    {
      "code": "scorecard_wheelchair_boarding_unknown",
      "count": 77,
      "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": 1,
      "severity": "WARNING",
      "what": "77 of 77 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": 37,
      "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,
      "rank": 2,
      "severity": "WARNING",
      "what": "37 of 37 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": "stop_without_stop_time",
      "count": 36,
      "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": 6.0,
      "rank": 3,
      "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."
    }
  ],
  "validator_version": "8.0.1"
}