{
  "agency": {
    "id": "emery-go-round-2224",
    "name": "Emery Go-Round"
  },
  "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": 41,
        "trips": 420,
        "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": 41,
          "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": "41 of 41 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": 420,
          "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": "420 of 420 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": 5,
        "instances_by_severity": {
          "ERROR": 0,
          "INFO": 9,
          "WARNING": 4
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "route_short_name_too_long",
          "count": 2,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Route short name too long (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "missing_recommended_file",
          "count": 1,
          "effort": "One small file, set once in export settings.",
          "fix": "Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date.",
          "owner": "Likely your export tool",
          "points": 4.0,
          "severity": "WARNING",
          "what": "A recommended GTFS file (usually feed_info.txt) is missing.",
          "why": "feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale."
        },
        {
          "code": "route_long_name_contains_short_name",
          "count": 1,
          "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": "big_gap_in_service",
          "count": 6,
          "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."
        },
        {
          "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."
        }
      ],
      "name": "correctness",
      "score": 86.8,
      "status": "measured",
      "summary": "The MobilityData validator flagged 5 kinds of issue across 13 instances (0 error, 4 warning, 9 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": 506,
        "feed_end_date": null,
        "feed_start_date": null,
        "feed_version": null,
        "has_feed_info": false,
        "last_service_date": "2027-11-27",
        "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 (the file itself is absent)",
          "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 506 days.",
      "weight": 0.2
    },
    "realtime": {
      "details": {
        "coverage_pct": null,
        "drift": {
          "median_seconds": 0,
          "observations": 1078,
          "on_time_share_pct": 100.0,
          "p90_abs_seconds": 0
        },
        "kinds_reachable": 3,
        "rt_freshness": "fresh",
        "samples": 9,
        "scheduled_trips_in_window": 0,
        "vehicles_checked": 7,
        "vehicles_on_route_pct": 42.9,
        "worst_lag_seconds": 0
      },
      "findings": [
        {
          "code": "scorecard_rt_vehicles_off_route",
          "count": 4,
          "effort": "A vendor support ticket with the trip ids attached.",
          "fix": "Ask your AVL vendor to check vehicle-to-trip assignments for the flagged trips.",
          "owner": "",
          "points": 8.6,
          "severity": "WARNING",
          "what": "4 of 7 sampled vehicle positions were far from their assigned route (worst: 325 m).",
          "why": "A bus shown off its route usually means a wrong trip assignment; riders watch their bus drive the wrong streets."
        }
      ],
      "name": "realtime",
      "score": 86.8,
      "status": "measured",
      "summary": "Sampled 9 times outside service hours: 3 of 3 feeds healthy; 42.9% of vehicles on their route; predictions ran a median of 0s behind schedule.",
      "weight": 0.2
    }
  },
  "conformance": {
    "awarded": false,
    "criteria": [
      {
        "detail": "Passes validation with no errors.",
        "key": "valid",
        "met": true
      },
      {
        "detail": "Service data covers the next 518 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": "0edfb39b71c51ff52b668eb6aa96e4a77a6c2164d123f74839a1e3f17ed38ebf",
    "size_bytes": 231786,
    "static_url": "https://emerygoround.com/data/emerygoround-ca-us.zip"
  },
  "generated_at": "2026-06-27T00:00:00+00:00",
  "geo": {
    "bbox": [
      -122.3134,
      37.82942,
      -122.26698,
      37.85232
    ],
    "lat": 37.83715,
    "lon": -122.28984,
    "stop_count": 41
  },
  "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": [
      "573"
    ],
    "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 518 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": "C",
    "margin_to_lower_band": 7.9,
    "margin_to_next_band": 2.1,
    "score": 77.9
  },
  "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 (Shell/Pow, Shell/Pow Sat).",
      "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": 38,
      "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": "38 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"40th @ San Pablo WB\", \"40th @ San Pablo EB\", \"Stanford Ave @ Horton WB\", 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": 41,
    "findings": [],
    "orphan_stops": 0,
    "single_stop_trips": 0,
    "trips_total": 420
  },
  "rubric_version": "1.1",
  "schema_version": "1.4",
  "snapshot_date": "2026-07-09",
  "top_fixes": [
    {
      "code": "scorecard_wheelchair_boarding_unknown",
      "count": 41,
      "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": "41 of 41 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": 420,
      "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": "420 of 420 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_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,
      "rank": 3,
      "severity": "WARNING",
      "what": "feed_info.txt is missing its start/end dates (the file itself is absent)",
      "why": "Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates."
    }
  ],
  "validator_version": "8.0.1"
}