{
  "agency": {
    "id": "spokane-transit-authority-sta-290",
    "name": "Spokane Transit Authority (STA)"
  },
  "autofix": {
    "available": true,
    "download_path": "data/artifacts/spokane-transit-authority-sta-290/corrected.zip",
    "download_url": "https://d14aimrgrbaz2a.cloudfront.net/data/artifacts/spokane-transit-authority-sta-290/corrected.zip",
    "fixes": [
      {
        "code": "autofix_trim_whitespace",
        "count": 28,
        "examples": [
          "'stop_desc': '0 ' -> '0'",
          "'stop_desc': '0 ' -> '0'",
          "'stop_desc': '0 ' -> '0'"
        ],
        "label": "Trimmed surrounding whitespace"
      },
      {
        "code": "autofix_route_name_case",
        "count": 1,
        "examples": [
          "SFCC -> Sfcc"
        ],
        "label": "Recased shouting route names"
      }
    ],
    "total": 29
  },
  "categories": {
    "completeness": {
      "details": {
        "accessibility": {
          "measures": "presence_not_usability",
          "score": 100.0,
          "stops_marked_accessible_pct": 96.4,
          "stops_marked_not_accessible_pct": 3.6,
          "stops_stated_pct": 100.0,
          "trips_stated_pct": 100.0
        },
        "accessibility_measures": "presence_not_usability",
        "components": {
          "contact": 7.5,
          "fares": 15.0,
          "headsigns": 15.0,
          "stop_names": 15.0,
          "wheelchair_stops": 25.0,
          "wheelchair_trips": 15.0
        },
        "fare_free": false,
        "fares": {
          "applied": true,
          "has_leg_rules": true,
          "has_products": true,
          "has_transfer_rules": true,
          "model": "v2",
          "product_count": 4
        },
        "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": 1665,
        "trips": 8396,
        "wheelchair_accessible_pct": 100.0,
        "wheelchair_boarding_pct": 100.0,
        "wheelchair_marked_accessible_pct": 96.4,
        "wheelchair_marked_not_accessible_pct": 3.6
      },
      "findings": [
        {
          "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": 92.5,
      "status": "measured",
      "summary": "100% of stops state wheelchair accessibility (96% marked accessible, 4% 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": 8,
        "instances_by_severity": {
          "ERROR": 0,
          "INFO": 10,
          "WARNING": 77
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "mixed_case_recommended_field",
          "count": 43,
          "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": 6.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": "service_has_no_active_day_of_the_week",
          "count": 21,
          "effort": "A few minutes in your scheduling software.",
          "fix": "Delete the empty calendars or set their service days.",
          "owner": "Likely your export tool",
          "points": 6.0,
          "severity": "WARNING",
          "what": "Some service calendars have no days of the week switched on.",
          "why": "Trips tied to these calendars never run; they are dead data that can mask real schedule problems."
        },
        {
          "code": "stop_too_far_from_shape_using_user_distance",
          "count": 9,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 6.0,
          "severity": "WARNING",
          "what": "Stop too far from shape using user distance (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "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": "missing_recommended_field",
          "count": 1,
          "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": "unusable_trip",
          "count": 1,
          "effort": "Worth a vendor question if it appears often.",
          "fix": "Check the flagged trips in your scheduling software; remove them or restore their missing stops.",
          "owner": "Likely your export tool",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Some trips serve fewer than two stops.",
          "why": "A trip with one stop can't be ridden; planners ignore it and it may signal an export problem."
        },
        {
          "code": "big_gap_in_service",
          "count": 10,
          "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."
        }
      ],
      "name": "correctness",
      "score": 65.2,
      "status": "measured",
      "summary": "The MobilityData validator flagged 8 kinds of issue across 87 instances (0 error, 77 warning, 10 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": 71,
        "feed_end_date": "2026-09-19",
        "feed_start_date": "2026-05-17",
        "feed_version": "MAY2026v3_20260521",
        "has_feed_info": true,
        "last_service_date": "2026-09-19",
        "seasonal_boundary": false,
        "service_type": "fixed"
      },
      "findings": [],
      "name": "freshness",
      "score": 100.0,
      "status": "measured",
      "summary": "Service data covers the next 71 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": true,
    "criteria": [
      {
        "detail": "Passes validation with no errors.",
        "key": "valid",
        "met": true
      },
      {
        "detail": "Service data covers the next 81 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": "beb4539e6a6062ffe9d933abb49007efe0414520e1c64a2536ba9f6163c8fea7",
    "size_bytes": 2493830,
    "static_url": "https://www.spokanetransit.com/gtfs"
  },
  "generated_at": "2026-06-30T00:00:00+00:00",
  "geo": {
    "bbox": [
      -117.70575,
      47.47668,
      -117.07599,
      47.76888
    ],
    "lat": 47.66663,
    "lon": -117.39685,
    "stop_count": 1665
  },
  "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": [
      "STA"
    ],
    "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 81 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.4,
    "margin_to_next_band": 7.6,
    "score": 82.4
  },
  "recommendations": [
    {
      "code": "scorecard_fares_v2_no_rider_categories",
      "count": 0,
      "effort": "Usually a short file naming the discount groups you already publish.",
      "fix": "Add rider_categories.txt for the fares you already offer, then reference those categories from your fare products.",
      "owner": "",
      "points": 0.0,
      "severity": "INFO",
      "what": "The feed publishes fare products but no rider_categories.txt defining who qualifies for each fare.",
      "why": "Without rider categories, apps can only show the full adult fare and can't surface senior, youth, or student discounts a rider may be eligible for."
    },
    {
      "code": "scorecard_stop_name_needs_tts",
      "count": 1596,
      "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": "1596 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"Washington @ North River Drive\", \"5th @ Deaconess Hospital\", \"6th @ Stevens\", 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": 1665,
    "findings": [
      {
        "code": "scorecard_single_stop_trips",
        "count": 1,
        "effort": "Usually an export setting or a stop_times mapping in your software.",
        "fix": "Check your scheduling export: every trip should list each stop it calls at, in order, with times.",
        "owner": "Likely your export tool",
        "points": 0.0,
        "severity": "WARNING",
        "what": "1 of 8396 trips list fewer than two stops.",
        "why": "A trip with one stop has no leg a rider can ride; trip planners can't route anyone on it, so the service effectively does not exist."
      }
    ],
    "orphan_stops": 0,
    "single_stop_trips": 1,
    "trips_total": 8396
  },
  "rubric_version": "1.1",
  "schema_version": "1.4",
  "snapshot_date": "2026-07-10",
  "top_fixes": [
    {
      "code": "mixed_case_recommended_field",
      "count": 43,
      "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": 6.0,
      "rank": 1,
      "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": "service_has_no_active_day_of_the_week",
      "count": 21,
      "effort": "A few minutes in your scheduling software.",
      "fix": "Delete the empty calendars or set their service days.",
      "owner": "Likely your export tool",
      "points": 6.0,
      "rank": 2,
      "severity": "WARNING",
      "what": "Some service calendars have no days of the week switched on.",
      "why": "Trips tied to these calendars never run; they are dead data that can mask real schedule problems."
    },
    {
      "code": "stop_too_far_from_shape_using_user_distance",
      "count": 9,
      "effort": "Varies.",
      "fix": "Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
      "owner": "",
      "points": 6.0,
      "rank": 3,
      "severity": "WARNING",
      "what": "Stop too far from shape using user distance (flagged by the MobilityData validator).",
      "why": "See the linked rule for what this affects."
    }
  ],
  "validator_version": "8.0.1"
}