{
  "agency": {
    "id": "anaheim-resort-transportation-art",
    "name": "Anaheim Resort Transportation (ART)",
    "subdivision_code": "US-CA",
    "subdivision_name": "California"
  },
  "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": 7.5,
          "fares": 0.0,
          "headsigns": 0.0,
          "stop_names": 0.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": 0,
        "headsign_loop_exempt_trips": 0,
        "headsign_pct": 0.0,
        "headsign_scored_pct": 0.0,
        "mixed_case_stop_name_pct": 0.0,
        "pathways": {
          "has_entrances": false,
          "has_levels": false,
          "has_pathways": false,
          "has_stations": false,
          "has_step_free": false,
          "pathway_count": 0
        },
        "stops": 0,
        "translations": {
          "feed_lang": "en",
          "has_translations": false,
          "languages": [],
          "translated_tables": [],
          "translation_count": 0
        },
        "trips": 0,
        "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": 0,
          "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": "0 of 0 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": 0,
          "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": "0 of 0 trips don't say whether the vehicle is wheelchair accessible.",
          "why": "Even with accessible stops, riders need to know the transit vehicle 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."
        },
        {
          "code": "scorecard_stop_names_all_caps",
          "count": 0,
          "effort": "Often a bulk fix in your scheduling software.",
          "fix": "Rename stops to mixed case where the language has letter case (for example, 'Central Station').",
          "owner": "Likely your export tool",
          "points": 15.0,
          "severity": "INFO",
          "what": "About 0 stop names are written in ALL CAPS.",
          "why": "Mixed-case names are easier to read in apps and are read more naturally by screen readers."
        },
        {
          "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": "Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger."
        }
      ],
      "name": "completeness",
      "score": 7.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 not published.",
      "weight": 0.25
    },
    "correctness": {
      "details": {
        "distinct_codes": 2,
        "instances_by_severity": {
          "ERROR": 0,
          "INFO": 0,
          "WARNING": 4
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "missing_recommended_field",
          "count": 3,
          "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": "missing_feed_contact_email_and_url",
          "count": 1,
          "effort": "One field, set once in export settings.",
          "fix": "Add feed_contact_email or feed_contact_url to feed_info.txt.",
          "owner": "Likely your export tool",
          "points": 4.0,
          "severity": "WARNING",
          "what": "feed_info.txt lists no contact email and no contact URL.",
          "why": "Without a contact, apps like Google Maps can't reach you when they find a problem in the feed."
        }
      ],
      "name": "correctness",
      "score": 92.0,
      "status": "measured",
      "summary": "The MobilityData validator flagged 2 kinds of issue across 4 instances (0 error, 4 warning, 0 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": null,
        "effective_expiry_date": null,
        "feed_end_date": null,
        "feed_start_date": null,
        "feed_version": null,
        "has_feed_info": true,
        "last_service_date": null,
        "seasonal_boundary": false,
        "service_horizon_review_years": 10,
        "service_horizon_status": "unknown",
        "service_type": "fixed"
      },
      "findings": [
        {
          "code": "scorecard_no_expiry_date",
          "count": 1,
          "effort": "Likely a one-time export setting.",
          "fix": "Add feed_start_date and feed_end_date to feed_info.txt and include calendar end dates in your export.",
          "owner": "Likely your export tool",
          "points": 100.0,
          "severity": "ERROR",
          "what": "Neither feed_info.txt nor the calendars state when service ends.",
          "why": "Nobody can tell when this feed will go stale."
        }
      ],
      "name": "freshness",
      "score": 0.0,
      "status": "measured",
      "summary": "No service end date could be found in this feed, so there is no way to know when riders will lose trip planning.",
      "weight": 0.2
    },
    "realtime": {
      "name": "realtime",
      "status": "not_yet_measured",
      "summary": "Not scored yet. Nothing here counts against the grade.",
      "weight": 0.2
    }
  },
  "confidence": {
    "feed_age_days": 0,
    "fetch_source": "mirror",
    "level": "provisional",
    "measured_categories": 3,
    "notes": [
      "Realtime quality was not measured this run. It does not count against the grade.",
      "The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead."
    ],
    "rt_windows": 0,
    "total_categories": 4
  },
  "conformance": {
    "awarded": false,
    "criteria": [
      {
        "detail": "Passes validation with no errors.",
        "key": "valid",
        "met": true
      },
      {
        "detail": "No service end date could be read.",
        "key": "current",
        "met": false
      },
      {
        "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. No service end date could be read. 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": "22991fdc232dcb4952a745a3ff97da85e230e391f1417639c14f3712e671f770",
    "size_bytes": 1735,
    "static_url": "https://art.tripshot.com/v1/gtfs.zip?regionId=CA558DDC-D7F2-4B48-9CAC-DEEA1134F820"
  },
  "fetch": {
    "final_url": "https://storage.googleapis.com/storage/v1/b/mdb-latest/o/us-california-anaheim-resort-transportation-art-gtfs-100.zip?alt=media",
    "max_attempts": 1,
    "origin_error": "HTTPError",
    "reader_archive_profile": "raw-v1",
    "source": "mirror",
    "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-01T00:00:00+00:00",
  "mode_profile": {
    "ferry_only": false,
    "graded": false,
    "has_ferry": false,
    "is_multimodal": false,
    "measured": true,
    "modes": [],
    "primary_mode": null,
    "primary_mode_label": null,
    "route_count": 0,
    "trip_count": 0
  },
  "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": [
      "7c90e53b-361e-4a3b-938a-135390adcc43"
    ],
    "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": "No service end date could be read, so currency is unknown.",
        "key": "current",
        "status": "not_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": "not_ready",
    "summary": "Resolve this before you certify on the D-10. No service end date could be read, so currency is unknown."
  },
  "overall": {
    "grade": "F",
    "margin_to_lower_band": 42.6,
    "margin_to_next_band": 17.4,
    "score": 42.6
  },
  "recommendations": [],
  "routability": {
    "boardable_stops": 0,
    "findings": [],
    "orphan_stops": 0,
    "single_stop_trips": 0,
    "trips_total": 0
  },
  "route_map": {
    "drawn_route_count": 0,
    "has_shapes": false,
    "route_count": 0,
    "routes": [],
    "stop_count": 0,
    "stop_points_capped": false
  },
  "rubric_version": "1.3",
  "schema_version": "1.17",
  "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": "trips.txt has no rows, so shape coverage can't be checked.",
    "status": "not_ready",
    "total_trips": 0,
    "trips_with_shape": 0
  },
  "snapshot_date": "2026-08-01",
  "top_fixes": [
    {
      "code": "scorecard_no_expiry_date",
      "count": 1,
      "effort": "Likely a one-time export setting.",
      "fix": "Add feed_start_date and feed_end_date to feed_info.txt and include calendar end dates in your export.",
      "owner": "Likely your export tool",
      "points": 100.0,
      "rank": 1,
      "severity": "ERROR",
      "what": "Neither feed_info.txt nor the calendars state when service ends.",
      "why": "Nobody can tell when this feed will go stale."
    },
    {
      "code": "scorecard_wheelchair_boarding_unknown",
      "count": 0,
      "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": "0 of 0 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_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"
}