{
  "agency": {
    "id": "beloit-transit",
    "name": "Beloit Transit",
    "subdivision_code": "US-WI",
    "subdivision_name": "Wisconsin"
  },
  "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": 0.0,
          "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": true
        },
        "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": null,
          "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."
        },
        {
          "code": "scorecard_bad_agency_url",
          "count": 1,
          "effort": "One field.",
          "fix": "Set agency_url to your agency's website, starting with https://.",
          "owner": "",
          "points": 7.5,
          "severity": "WARNING",
          "what": "agency.txt has no working website URL.",
          "why": "Trip planners link riders to this URL for schedules and fares."
        },
        {
          "code": "scorecard_flex_no_booking_rules",
          "count": 1,
          "effort": "A small file; one rule often covers the whole service.",
          "fix": "Add booking_rules.txt saying how far ahead and how to book (phone, app, or web).",
          "owner": "",
          "points": 0.0,
          "severity": "WARNING",
          "what": "This feed describes flexible (demand-responsive) service but has no booking_rules.txt.",
          "why": "Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service."
        }
      ],
      "name": "completeness",
      "score": 0.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": 3,
        "instances_by_severity": {
          "ERROR": 2,
          "INFO": 46,
          "WARNING": 0
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "missing_required_column",
          "count": 2,
          "effort": "Often an export setting; ask your vendor if it recurs.",
          "fix": "Add the required column named in the finding to the flagged file.",
          "owner": "Likely your export tool",
          "points": 12.0,
          "severity": "ERROR",
          "what": "A file is missing a column that GTFS requires.",
          "why": "Apps may reject the whole file, so riders could lose the affected routes or stops."
        },
        {
          "code": "unknown_column",
          "count": 37,
          "effort": "A quick look at the flagged files.",
          "fix": "Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras.",
          "owner": "",
          "points": 0.8,
          "severity": "INFO",
          "what": "Some files contain columns that are not part of the GTFS spec.",
          "why": "Harmless to riders, but apps ignore these columns and they can hide typos in real column names."
        },
        {
          "code": "unknown_file",
          "count": 9,
          "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.8,
          "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."
        }
      ],
      "name": "correctness",
      "score": 86.5,
      "status": "measured",
      "summary": "The MobilityData validator flagged 3 kinds of issue across 48 instances (2 error, 0 warning, 46 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": false,
        "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": "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": "1 validator error to resolve.",
        "key": "valid",
        "met": false
      },
      {
        "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 does not meet the conformance requirements yet. Here is what the mark needs: 1 validator error to resolve. No service end date could be read. 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": "2f047947b9b64e479c96d384f0d68819294658c727b61ca7e1fc363d2889241c",
    "size_bytes": 5878,
    "source_provenance": "unverified",
    "static_url": "https://data.trilliumtransit.com/gtfs/beloittransit-wi-us/beloittransit-wi-us.zip"
  },
  "fetch": {
    "final_url": "https://data.trilliumtransit.com/gtfs/beloittransit-wi-us/beloittransit-wi-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",
  "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": "Your agency.txt sets no nonblank agency_id. Every RY2026 NTD GTFS submission needs a stable value unique among the reporters represented in the feed, crosswalked on the P-50 form.",
    "feed_agency_ids": [],
    "fix": "Add agency_id to agency.txt and use the same value wherever routes.txt identifies that agency. Keep it stable, and enter its crosswalk to the reporter's NTD ID on P-50. It does not need to equal the five-digit NTD ID.",
    "status": "missing"
  },
  "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": "No service end date could be read, so currency is unknown.",
        "key": "current",
        "status": "not_ready"
      },
      {
        "detail": "agency.txt has no nonblank agency_id. Every RY2026 NTD GTFS submission needs a stable value unique among the reporters represented in the feed, crosswalked to each reporter's NTD ID on the P-50 form.",
        "key": "agency_id",
        "status": "not_ready"
      }
    ],
    "status": "not_ready",
    "summary": "Resolve this before you certify on the D-10. 1 validator error to resolve. No service end date could be read, so currency is unknown. agency.txt has no nonblank agency_id. Every RY2026 NTD GTFS submission needs a stable value unique among the reporters represented in the feed, crosswalked to each reporter's NTD ID on the P-50 form."
  },
  "overall": {
    "grade": "F",
    "margin_to_lower_band": 37.8,
    "margin_to_next_band": 22.2,
    "score": 37.8
  },
  "recommendations": [
    {
      "category": "flex",
      "code": "scorecard_flex_completeness_no_booking_rules",
      "count": 1,
      "effort": "A small file; one rule often covers the whole service.",
      "fix": "Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).",
      "owner": "",
      "points": 0.0,
      "severity": "WARNING",
      "what": "Flex zones are published but no booking_rules.txt is present.",
      "why": "Riders can see the service area but not how to book, so they can't complete a trip."
    }
  ],
  "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.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": "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-10",
  "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": "missing_required_column",
      "count": 2,
      "effort": "Often an export setting; ask your vendor if it recurs.",
      "fix": "Add the required column named in the finding to the flagged file.",
      "owner": "Likely your export tool",
      "points": 12.0,
      "rank": 2,
      "severity": "ERROR",
      "what": "A file is missing a column that GTFS requires.",
      "why": "Apps may reject the whole file, so riders could lose the affected routes or stops."
    },
    {
      "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": 3,
      "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."
    }
  ],
  "validator_version": "8.0.1"
}