{
  "agency": {
    "id": "burbankbus-2149",
    "name": "BurbankBus"
  },
  "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": 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_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": 47,
        "trips": 99,
        "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": 47,
          "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": "47 of 47 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": 99,
          "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": "99 of 99 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": 9,
        "instances_by_severity": {
          "ERROR": 48,
          "INFO": 4,
          "WARNING": 32
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "decreasing_or_equal_stop_time_distance",
          "count": 48,
          "effort": "Usually an export-tool fix, not hand editing.",
          "fix": "Re-generate shape distances in your export; flag to your vendor if it persists.",
          "owner": "Likely your export tool",
          "points": 18.0,
          "severity": "ERROR",
          "what": "Some trips have stop times whose distances along the route go backwards.",
          "why": "Apps can show buses jumping backwards or mis-order stops."
        },
        {
          "code": "stop_too_far_from_shape_using_user_distance",
          "count": 26,
          "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": "route_long_name_contains_short_name",
          "count": 2,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'route_long_name_contains_short_name' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Route long name contains short name (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "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 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": "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": "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": "unknown_file",
          "count": 3,
          "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."
        },
        {
          "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": 55.0,
      "status": "measured",
      "summary": "The MobilityData validator flagged 9 kinds of issue across 84 instances (48 error, 32 warning, 4 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": 26837,
        "feed_end_date": null,
        "feed_start_date": "2024-01-14",
        "feed_version": "1/12/2024",
        "has_feed_info": true,
        "last_service_date": "2099-12-31",
        "seasonal_boundary": false,
        "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 data covers the next 26837 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": "1 validator error to resolve.",
        "key": "valid",
        "met": false
      },
      {
        "detail": "Service data covers the next 26847 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. 1 validator error to resolve. 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": "6143483b6f28d3872d9887214537f04994bfbcea3e073688f7644e683afd9dcc",
    "size_bytes": 25615,
    "static_url": "https://rideburbankbus.com/gtfs"
  },
  "generated_at": "2026-06-30T00:00:00+00:00",
  "geo": {
    "bbox": [
      -118.3753,
      34.13859,
      -118.3117,
      34.19569
    ],
    "lat": 34.17242,
    "lon": -118.33904,
    "stop_count": 47
  },
  "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": [
      "121"
    ],
    "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 covers the next 26847 days.",
        "key": "current",
        "status": "ready"
      }
    ],
    "status": "at_risk",
    "summary": "This feed is close to NTD-ready. 1 validator error to resolve."
  },
  "overall": {
    "grade": "F",
    "margin_to_lower_band": 59.4,
    "margin_to_next_band": 0.6,
    "score": 59.4
  },
  "recommendations": [
    {
      "code": "scorecard_route_color_low_contrast",
      "count": 2,
      "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": "2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (P, O).",
      "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": 42,
      "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": "42 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"Empire & Ontario\", \"Ontario & Thornton\", \"Olive & Lake SB\", 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": 47,
    "findings": [],
    "orphan_stops": 0,
    "single_stop_trips": 0,
    "trips_total": 99
  },
  "rubric_version": "1.1",
  "schema_version": "1.4",
  "snapshot_date": "2026-07-10",
  "top_fixes": [
    {
      "code": "decreasing_or_equal_stop_time_distance",
      "count": 48,
      "effort": "Usually an export-tool fix, not hand editing.",
      "fix": "Re-generate shape distances in your export; flag to your vendor if it persists.",
      "owner": "Likely your export tool",
      "points": 18.0,
      "rank": 1,
      "severity": "ERROR",
      "what": "Some trips have stop times whose distances along the route go backwards.",
      "why": "Apps can show buses jumping backwards or mis-order stops."
    },
    {
      "code": "scorecard_wheelchair_boarding_unknown",
      "count": 47,
      "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": 2,
      "severity": "WARNING",
      "what": "47 of 47 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": 99,
      "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": 3,
      "severity": "WARNING",
      "what": "99 of 99 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."
    }
  ],
  "validator_version": "8.0.1"
}