{
  "agency": {
    "id": "tahoe-transportation-district",
    "name": "Tahoe Transportation District",
    "subdivision_code": "US-NV",
    "subdivision_name": "Nevada"
  },
  "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",
        "cemv": {
          "declared": false,
          "supported": false
        },
        "components": {
          "contact": 15.0,
          "fares": 0.0,
          "headsigns": 15.0,
          "stop_names": 15.0,
          "wheelchair_stops": 0.0,
          "wheelchair_trips": 0.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_applicable_trips": 132,
        "headsign_loop_exempt_trips": 0,
        "headsign_pct": 100.0,
        "headsign_scored_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": 127,
        "translations": {
          "feed_lang": "en-US",
          "has_translations": false,
          "languages": [],
          "translated_tables": [],
          "translation_count": 0
        },
        "trips": 132,
        "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": 127,
          "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": "127 of 127 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": 132,
          "effort": "A default or per-trip field in your export.",
          "fix": "Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.",
          "owner": "Likely your export tool",
          "points": 15.0,
          "severity": "WARNING",
          "what": "132 of 132 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_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."
        }
      ],
      "name": "completeness",
      "score": 45.0,
      "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 not published.",
      "weight": 0.25
    },
    "correctness": {
      "details": {
        "distinct_codes": 7,
        "instances_by_severity": {
          "ERROR": 0,
          "INFO": 4,
          "WARNING": 22
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "equal_shape_distance_same_coordinates",
          "count": 12,
          "effort": "Usually one export setting.",
          "fix": "Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.",
          "owner": "Likely your export tool",
          "points": 6.0,
          "severity": "WARNING",
          "what": "Some route lines list the same point twice in a row.",
          "why": "Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export."
        },
        {
          "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": "trip_distance_exceeds_shape_distance_below_threshold",
          "count": 4,
          "effort": "Usually an export-tool fix, not hand editing.",
          "fix": "Re-generate shape_dist_traveled on export so stop and shape distances use the same units.",
          "owner": "Likely your export tool",
          "points": 4.0,
          "severity": "WARNING",
          "what": "On some trips the stop distances run a little past the end of the route line.",
          "why": "The stop and shape distance values don't quite line up, so any math that uses them can drift."
        },
        {
          "code": "missing_feed_info_date",
          "count": 1,
          "effort": "Two fields, likely set once in your export settings.",
          "fix": "Fill in feed_start_date and feed_end_date in feed_info.txt.",
          "owner": "Likely your export tool",
          "points": 4.0,
          "severity": "WARNING",
          "what": "feed_info.txt does not state when this feed starts and ends.",
          "why": "Without stated dates, apps can't warn anyone before your data goes stale; it just disappears one day."
        },
        {
          "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 leave out fields that GTFS asks for but does not require.",
          "why": "Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners."
        },
        {
          "code": "unknown_file",
          "count": 3,
          "effort": "A quick look at the flagged file.",
          "fix": "Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra.",
          "owner": "",
          "points": 0.5,
          "severity": "INFO",
          "what": "The feed includes a file that is not part of the GTFS spec.",
          "why": "Apps ignore files they don't know, and a stray file can hide a misspelled standard file name."
        },
        {
          "code": "service_extends_far_in_the_future",
          "count": 1,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 0.5,
          "severity": "INFO",
          "what": "Service extends far in the future (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        }
      ],
      "name": "correctness",
      "score": 77.0,
      "status": "measured",
      "summary": "The MobilityData validator flagged 7 kinds of issue across 26 instances (0 error, 22 warning, 4 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": 26793,
        "effective_expiry_date": "2099-12-31",
        "feed_end_date": null,
        "feed_start_date": "2024-06-29",
        "feed_version": "Summer 2024 Schedule",
        "has_feed_info": true,
        "last_service_date": "2099-12-31",
        "seasonal_boundary": false,
        "service_horizon_review_years": 10,
        "service_horizon_status": "unusually_distant",
        "service_type": "fixed"
      },
      "findings": [
        {
          "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": 85.0,
      "status": "measured",
      "summary": "Service is published through 2099-12-31, an unusually distant end date. It may be intentional, but confirm it before treating the feed as maintained.",
      "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
    }
  },
  "confidence": {
    "feed_age_days": 0,
    "fetch_source": "origin",
    "level": "medium",
    "measured_categories": 3,
    "notes": [
      "Realtime quality was not measured this run. It does not count against the grade.",
      "The feed was downloaded from the configured feed URL. Publisher ownership of that URL is not verified."
    ],
    "rt_windows": 0,
    "total_categories": 4
  },
  "conformance": {
    "awarded": false,
    "criteria": [
      {
        "detail": "Passes validation with no errors.",
        "key": "valid",
        "met": true
      },
      {
        "detail": "The published window is current, but its service end date is unusually distant; confirm that date is intentional.",
        "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": "One requirement remains for this feed to earn the conformance mark. States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.",
    "version": 2
  },
  "feed": {
    "license_note": "No stated data license in the Mobility Database; verify before publishing.",
    "reachable": true,
    "sha256": "c9644d27c7e535add0048a9bfb8b7e3595cb48d1584b5040ea31613ee1b8d84b",
    "size_bytes": 163633,
    "source_provenance": "unverified",
    "static_url": "https://data.trilliumtransit.com/gtfs/tahoe-ca-us/tahoe-ca-us.zip"
  },
  "fetch": {
    "final_url": "https://data.trilliumtransit.com/gtfs/tahoe-ca-us/tahoe-ca-us.zip",
    "max_attempts": 4,
    "reader_archive_profile": "raw-v1",
    "source": "origin",
    "user_agent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36"
  },
  "generated_at": "2026-08-10T00:00:00+00:00",
  "geo": {
    "bbox": [
      -120.01012,
      38.89462,
      -119.73989,
      39.25181
    ],
    "lat": 38.94565,
    "lon": -119.95217,
    "stop_count": 127
  },
  "mode_profile": {
    "ferry_only": false,
    "graded": false,
    "has_ferry": false,
    "is_multimodal": false,
    "measured": true,
    "modes": [
      {
        "key": "bus",
        "label": "Bus",
        "route_count": 5,
        "trip_count": 132,
        "trip_share_pct": 100.0
      }
    ],
    "primary_mode": "bus",
    "primary_mode_label": "Bus",
    "route_count": 5,
    "trip_count": 132
  },
  "ntd_id_alignment": {
    "detail": "This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison is not checked yet.",
    "feed_agency_ids": [
      "215"
    ],
    "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": "The published window is current, but its service end date is unusually distant; confirm that date is intentional.",
        "key": "current",
        "status": "ready"
      },
      {
        "detail": "agency.txt provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk each value on the P-50 form.",
        "key": "agency_id",
        "status": "ready"
      }
    ],
    "status": "ready",
    "summary": "Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination."
  },
  "overall": {
    "grade": "D",
    "margin_to_lower_band": 9.0,
    "margin_to_next_band": 1.0,
    "score": 69.0
  },
  "recommendations": [
    {
      "category": "accessibility",
      "code": "scorecard_route_color_low_contrast",
      "count": 1,
      "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": "1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (55).",
      "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."
    },
    {
      "category": "accessibility",
      "code": "scorecard_stop_name_needs_tts",
      "count": 118,
      "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": "118 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"South Ave/3rd St (Barton Hospital)\", \"3rd St (Tahoe Senior Plaza)\", \"US 50/3rd St (Orchids)\", 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-08-23",
    "feed_fetched_date": "2026-08-22",
    "kind": "freshness"
  },
  "routability": {
    "boardable_stops": 127,
    "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 127 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": 132
  },
  "route_map": {
    "drawn_route_count": 5,
    "has_shapes": true,
    "path": "data/artifacts/tahoe-transportation-district/geometry.geojson",
    "route_count": 5,
    "routes": [
      {
        "color": "6BA52B",
        "color_name": "brown",
        "has_shape": true,
        "id": "5376",
        "label": "50",
        "long": "South Shore Daily",
        "short": "50",
        "text_color": "000000",
        "type_label": "Bus"
      },
      {
        "color": "EB3B34",
        "color_name": "red",
        "has_shape": true,
        "id": "5391",
        "label": "55",
        "long": "Neighborhood Connection",
        "short": "55",
        "text_color": "FFFFFF",
        "type_label": "Bus"
      },
      {
        "color": "F0A031",
        "color_name": "yellow",
        "has_shape": true,
        "id": "5671",
        "label": "19X",
        "long": "Valley Express Daily",
        "short": "19X",
        "text_color": "000000",
        "type_label": "Bus"
      },
      {
        "color": "00BEE1",
        "color_name": "teal",
        "has_shape": true,
        "id": "5672",
        "label": "22",
        "long": "South Shore Service and Lake Express Daily",
        "short": "22",
        "text_color": "000000",
        "type_label": "Bus"
      },
      {
        "color": "285294",
        "color_name": "teal",
        "has_shape": true,
        "id": "5853",
        "label": "28",
        "long": "East Shore Express",
        "short": "28",
        "text_color": "FFFFFF",
        "type_label": "Bus"
      }
    ],
    "stop_count": 127,
    "stop_points_capped": false
  },
  "rubric_version": "1.3",
  "schema_version": "1.18",
  "scoring_profile": {
    "id": "gtfs-scorecard-1.3",
    "provenance": "GTFS Scorecard's project-authored weights, deductions, thresholds, grade bands, and fix ranking, informed by the California Transit Data Guidelines and the MobilityData gtfs-validator. It is not a worldwide standard or a compliance determination.",
    "rubric_version": "1.3"
  },
  "shapes_readiness": {
    "detail": "All 132 trips have a shape in shapes.txt.",
    "status": "ready",
    "total_trips": 132,
    "trips_with_shape": 132
  },
  "snapshot_date": "2026-08-23",
  "top_fixes": [
    {
      "code": "scorecard_wheelchair_boarding_unknown",
      "count": 127,
      "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": "127 of 127 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": 132,
      "effort": "A default or per-trip field in your export.",
      "fix": "Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.",
      "owner": "Likely your export tool",
      "points": 15.0,
      "rank": 2,
      "severity": "WARNING",
      "what": "132 of 132 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_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": 3,
      "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."
    }
  ],
  "validator_version": "8.0.1"
}