{
  "agency": {
    "id": "montgomery-county-department-of-transportation-ride-on",
    "name": "Montgomery County Department of Transportation (Ride On)"
  },
  "autofix": {
    "available": true,
    "download_path": "data/artifacts/montgomery-county-department-of-transportation-ride-on/corrected.zip",
    "download_url": "https://d14aimrgrbaz2a.cloudfront.net/data/artifacts/montgomery-county-department-of-transportation-ride-on/corrected.zip",
    "fixes": [
      {
        "code": "autofix_stop_name_case",
        "count": 4576,
        "examples": [
          "AIRPARK RD & CHEMAULT WAY -> Airpark Rd & Chemault Way",
          "AIRPARK RD & WOODFIELD RD -> Airpark Rd & Woodfield Rd",
          "AIRPARK RD & WOODFIELD RD -> Airpark Rd & Woodfield Rd"
        ],
        "label": "Recased shouting stop names"
      }
    ],
    "total": 4576
  },
  "categories": {
    "completeness": {
      "details": {
        "accessibility": {
          "measures": "presence_not_usability",
          "score": 100.0,
          "stops_marked_accessible_pct": 0.0,
          "stops_marked_not_accessible_pct": 100.0,
          "stops_stated_pct": 100.0,
          "trips_stated_pct": 100.0
        },
        "accessibility_measures": "presence_not_usability",
        "components": {
          "contact": 15.0,
          "fares": 0.0,
          "headsigns": 14.9,
          "stop_names": 0.0,
          "wheelchair_stops": 25.0,
          "wheelchair_trips": 15.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": 99.5,
        "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": 4578,
        "trips": 17530,
        "wheelchair_accessible_pct": 100.0,
        "wheelchair_boarding_pct": 100.0,
        "wheelchair_marked_accessible_pct": 0.0,
        "wheelchair_marked_not_accessible_pct": 100.0
      },
      "findings": [
        {
          "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": 4576,
          "effort": "Often a bulk fix in your scheduling software.",
          "fix": "Rename stops to mixed case (e.g. 'Main St & 2nd Ave').",
          "owner": "Likely your export tool",
          "points": 15.0,
          "severity": "INFO",
          "what": "About 4576 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_missing_headsigns",
          "count": 90,
          "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": 0.1,
          "severity": "WARNING",
          "what": "90 of 17530 trips have no headsign.",
          "why": "Riders at the stop can't tell which direction a bus is going."
        }
      ],
      "name": "completeness",
      "score": 69.9,
      "status": "measured",
      "summary": "100% of stops state wheelchair accessibility (0% marked accessible, 100% 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": 11,
        "instances_by_severity": {
          "ERROR": 430,
          "INFO": 0,
          "WARNING": 7643
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "decreasing_or_equal_stop_time_distance",
          "count": 430,
          "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": 24.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": "mixed_case_recommended_field",
          "count": 5518,
          "effort": "Often a bulk fix in your scheduling software.",
          "fix": "Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').",
          "owner": "Likely your export tool",
          "points": 8.0,
          "severity": "WARNING",
          "what": "Some rider-facing names are in ALL CAPS or all lowercase.",
          "why": "ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers."
        },
        {
          "code": "fast_travel_between_consecutive_stops",
          "count": 1738,
          "effort": "A few minutes per flagged trip.",
          "fix": "Check the flagged stop times for transposed minutes.",
          "owner": "",
          "points": 8.0,
          "severity": "WARNING",
          "what": "Some scheduled trips travel implausibly fast between stops.",
          "why": "Usually a typo'd stop time; riders get impossible arrival estimates."
        },
        {
          "code": "stop_too_far_from_shape_using_user_distance",
          "count": 257,
          "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": 8.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": 82,
          "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": 8.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": "route_color_contrast",
          "count": 12,
          "effort": "One field per route.",
          "fix": "Pick a darker/lighter route_text_color for the flagged routes.",
          "owner": "",
          "points": 6.0,
          "severity": "WARNING",
          "what": "Some route colors don't contrast with their text color.",
          "why": "Route badges become unreadable, especially for riders with low vision."
        },
        {
          "code": "stop_too_far_from_shape",
          "count": 12,
          "effort": "A few minutes per flagged stop.",
          "fix": "Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced.",
          "owner": "Likely your export tool",
          "points": 6.0,
          "severity": "WARNING",
          "what": "Some stops sit far from the route line they belong to.",
          "why": "Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner."
        },
        {
          "code": "trip_distance_exceeds_shape_distance_below_threshold",
          "count": 12,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'trip_distance_exceeds_shape_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 6.0,
          "severity": "WARNING",
          "what": "Trip distance exceeds shape distance below threshold (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "stops_match_shape_out_of_order",
          "count": 9,
          "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": 6.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": "service_has_no_active_day_of_the_week",
          "count": 2,
          "effort": "A few minutes in your scheduling software.",
          "fix": "Delete the empty calendars or set their service days.",
          "owner": "Likely your export tool",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Some service calendars have no days of the week switched on.",
          "why": "Trips tied to these calendars never run; they are dead data that can mask real schedule problems."
        },
        {
          "code": "expired_calendar",
          "count": 1,
          "effort": "One setting in most export tools.",
          "fix": "Remove past service periods the next time you export the feed.",
          "owner": "Likely your export tool",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Some service calendars in the feed have already expired.",
          "why": "Expired calendars are dead weight and can hide real schedule problems from your staff and vendors."
        }
      ],
      "name": "correctness",
      "score": 12.0,
      "status": "measured",
      "summary": "The MobilityData validator flagged 11 kinds of issue across 8073 instances (430 error, 7643 warning, 0 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": 58,
        "feed_end_date": "2026-09-05",
        "feed_start_date": "2026-05-03",
        "feed_version": "13-May 3, 2026_20260423",
        "has_feed_info": true,
        "last_service_date": "2026-09-05",
        "seasonal_boundary": false,
        "service_type": "fixed"
      },
      "findings": [],
      "name": "freshness",
      "score": 96.7,
      "status": "measured",
      "summary": "Service data covers the next 58 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 70 days.",
        "key": "current",
        "met": true
      },
      {
        "detail": "States wheelchair access on 100% of stops and 100% of trips.",
        "key": "accessible",
        "met": true
      }
    ],
    "status": "not_yet",
    "summary": "This feed is close to the conformance mark. 1 validator error to resolve."
  },
  "feed": {
    "license_note": "No stated data license in the Mobility Database; verify before publishing.",
    "reachable": true,
    "sha256": "d48ca97096f8f4ef86c7135d19d9bd07f8d5b98ec857887e87594026b9f4e16c",
    "size_bytes": 6450320,
    "static_url": "https://www.montgomerycountymd.gov/DOT-Transit/Resources/Files/GTFS/RideOnGTFS.zip"
  },
  "generated_at": "2026-06-27T00:00:00+00:00",
  "geo": {
    "bbox": [
      -77.41866,
      38.93569,
      -76.9308,
      39.28851
    ],
    "lat": 39.07636,
    "lon": -77.12597,
    "stop_count": 4578
  },
  "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": [
      "MCRO"
    ],
    "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 70 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": 51.3,
    "margin_to_next_band": 8.7,
    "score": 51.3
  },
  "recommendations": [
    {
      "code": "scorecard_route_color_low_contrast",
      "count": 32,
      "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": "32 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 101, 12, 2, 33, and more).",
      "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": 4578,
      "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": "4578 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"AIRPARK RD & CHEMAULT WAY\", \"AIRPARK RD & WOODFIELD RD\", \"AIRPARK RD & WOODFIELD RD\", 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": 4578,
    "findings": [],
    "orphan_stops": 0,
    "single_stop_trips": 0,
    "trips_total": 17530
  },
  "rubric_version": "1.1",
  "schema_version": "1.4",
  "snapshot_date": "2026-07-09",
  "top_fixes": [
    {
      "code": "decreasing_or_equal_stop_time_distance",
      "count": 430,
      "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": 24.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_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": 2,
      "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": "mixed_case_recommended_field",
      "count": 5518,
      "effort": "Often a bulk fix in your scheduling software.",
      "fix": "Use mixed case for stop names and headsigns (e.g. 'Main St & 2nd Ave', not 'MAIN ST & 2ND AVE').",
      "owner": "Likely your export tool",
      "points": 8.0,
      "rank": 3,
      "severity": "WARNING",
      "what": "Some rider-facing names are in ALL CAPS or all lowercase.",
      "why": "ALL-CAPS stop and headsign names are harder to read in apps and are read awkwardly by screen readers."
    }
  ],
  "validator_version": "8.0.1"
}