2026-07-07.json

{
  "agency": {
    "id": "adams-county",
    "name": "Flex"
  },
  "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": 15.0,
          "headsigns": 0.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": true,
          "booking_rule_count": 1,
          "has_booking_rules": true,
          "has_flex": true
        },
        "has_fares": true,
        "headsign_pct": 0.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": 1,
        "trips": 1,
        "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": 1,
          "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": "1 of 1 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": 1,
          "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": "1 of 1 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_headsigns",
          "count": 1,
          "effort": "Usually a bulk edit in your scheduling software.",
          "fix": "Populate trip_headsign to match what the bus displays.",
          "owner": "Likely your export tool",
          "points": 15.0,
          "severity": "WARNING",
          "what": "1 of 1 trips have no headsign.",
          "why": "Riders at the stop can't tell which direction a bus is going."
        },
        {
          "code": "scorecard_flex_service",
          "count": 1,
          "effort": "None.",
          "fix": "No action needed.",
          "owner": "",
          "points": 0.0,
          "severity": "INFO",
          "what": "This feed includes flexible (demand-responsive) service, and riders are told how to book it.",
          "why": "Dial-a-ride and zone service are described for trip planners, not just fixed routes."
        }
      ],
      "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 published.",
      "weight": 0.25
    },
    "correctness": {
      "details": {
        "distinct_codes": 4,
        "instances_by_severity": {
          "ERROR": 0,
          "INFO": 30,
          "WARNING": 1
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "stop_without_stop_time",
          "count": 1,
          "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": "unknown_column",
          "count": 21,
          "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": 8,
          "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.8,
          "severity": "INFO",
          "what": "Unknown file (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "service_window_outside_feed_period",
          "count": 1,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'service_window_outside_feed_period' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 0.5,
          "severity": "INFO",
          "what": "Service window outside feed period (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        }
      ],
      "name": "correctness",
      "score": 94.0,
      "status": "measured",
      "summary": "The MobilityData validator flagged 4 kinds of issue across 31 instances (0 error, 1 warning, 30 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": 25,
        "feed_end_date": "2026-08-01",
        "feed_start_date": "2025-07-29",
        "feed_version": "UTC: 29-Jul-2025 20:35",
        "has_feed_info": true,
        "last_service_date": "2026-08-01",
        "seasonal_boundary": false,
        "service_type": "fixed"
      },
      "findings": [
        {
          "code": "scorecard_feed_expiring_soon",
          "count": 1,
          "effort": "One export setting.",
          "fix": "Re-export with a validity window that reaches at least 60 days out.",
          "owner": "Likely your export tool",
          "points": 55.0,
          "severity": "WARNING",
          "what": "Service data runs out in 25 day(s).",
          "why": "When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice."
        }
      ],
      "name": "freshness",
      "score": 41.7,
      "status": "measured",
      "summary": "Service data runs out in 25 day(s). Publish an updated feed soon or 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
    }
  },
  "conformance": {
    "awarded": false,
    "criteria": [
      {
        "detail": "Passes validation with no errors.",
        "key": "valid",
        "met": true
      },
      {
        "detail": "Service data covers the next 35 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": "09f185aac1f8a7b0208dd63db8fbd5569e7d2c0280a9fe216be6dd955b8c83ec",
    "size_bytes": 16096,
    "static_url": "https://data.trilliumtransit.com/gtfs/adamscounty-co-us/adamscounty-co-us--flex-v2.zip"
  },
  "generated_at": "2026-06-27T00:00:00+00:00",
  "geo": {
    "bbox": [
      -104.33786,
      39.86959,
      -104.33786,
      39.86959
    ],
    "lat": 39.86959,
    "lon": -104.33786,
    "stop_count": 1
  },
  "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": [
      "1723"
    ],
    "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 35 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": "D",
    "margin_to_lower_band": 5.6,
    "margin_to_next_band": 4.4,
    "score": 65.6
  },
  "recommendations": [],
  "recompute": {
    "as_of": "2026-07-07",
    "feed_fetched_date": "2026-07-06",
    "kind": "freshness"
  },
  "routability": {
    "boardable_stops": 1,
    "findings": [
      {
        "code": "scorecard_orphan_stops",
        "count": 1,
        "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": "1 of 1 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": 1,
    "single_stop_trips": 0,
    "trips_total": 1
  },
  "rubric_version": "1.1",
  "schema_version": "1.4",
  "snapshot_date": "2026-07-07",
  "top_fixes": [
    {
      "code": "scorecard_feed_expiring_soon",
      "count": 1,
      "effort": "One export setting.",
      "fix": "Re-export with a validity window that reaches at least 60 days out.",
      "owner": "Likely your export tool",
      "points": 55.0,
      "rank": 1,
      "severity": "WARNING",
      "what": "Service data runs out in 25 day(s).",
      "why": "When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice."
    },
    {
      "code": "scorecard_wheelchair_boarding_unknown",
      "count": 1,
      "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": "1 of 1 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": 1,
      "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": "1 of 1 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"
}