{
  "agency": {
    "id": "adirondack-trailways-pine-hill-trailways",
    "name": "Adirondack Trailways Pine Hill Trailways"
  },
  "autofix": {
    "available": true,
    "download_path": "data/artifacts/adirondack-trailways-pine-hill-trailways/corrected.zip",
    "download_url": "https://d14aimrgrbaz2a.cloudfront.net/data/artifacts/adirondack-trailways-pine-hill-trailways/corrected.zip",
    "fixes": [
      {
        "code": "autofix_stop_name_case",
        "count": 41,
        "examples": [
          "WOODSTOCK, NY -> Woodstock, Ny",
          "NEW YORK, NY -> New York, Ny",
          "PHOENICIA, NY -> Phoenicia, Ny"
        ],
        "label": "Recased shouting stop names"
      },
      {
        "code": "autofix_route_name_case",
        "count": 31,
        "examples": [
          "KINGSTON -> NEW YORK -> Kingston -> New York",
          "NEW YORK -> KINGSTON -> New York -> Kingston",
          "KINGSTON -> NEW YORK -> Kingston -> New York"
        ],
        "label": "Recased shouting route names"
      }
    ],
    "total": 72
  },
  "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": 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_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": 41,
        "trips": 31,
        "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": 31,
          "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": "31 of 31 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_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": 41,
          "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 41 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": 31,
          "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": "31 of 31 trips have no headsign.",
          "why": "Riders at the stop can't tell which direction a bus is going."
        },
        {
          "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": 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": 13,
        "instances_by_severity": {
          "ERROR": 31,
          "INFO": 0,
          "WARNING": 3543
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "trip_distance_exceeds_shape_distance",
          "count": 16,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 18.0,
          "severity": "ERROR",
          "what": "Trip distance exceeds shape distance (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "decreasing_or_equal_stop_time_distance",
          "count": 15,
          "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": 18.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": "equal_shape_distance_same_coordinates",
          "count": 3163,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'equal_shape_distance_same_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 8.0,
          "severity": "WARNING",
          "what": "Equal shape distance same coordinates (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "mixed_case_recommended_field",
          "count": 103,
          "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": "stop_too_far_from_shape_using_user_distance",
          "count": 96,
          "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": "stop_too_far_from_shape",
          "count": 59,
          "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": 8.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": "fast_travel_between_consecutive_stops",
          "count": 33,
          "effort": "A few minutes per flagged trip.",
          "fix": "Check the flagged stop times for transposed minutes.",
          "owner": "",
          "points": 6.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": "missing_recommended_field",
          "count": 32,
          "effort": "A field at a time; not urgent.",
          "fix": "Review the flagged fields and fill in the ones your riders would use.",
          "owner": "",
          "points": 6.0,
          "severity": "WARNING",
          "what": "Some files are missing recommended (not required) fields.",
          "why": "Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners."
        },
        {
          "code": "expired_calendar",
          "count": 31,
          "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": 6.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."
        },
        {
          "code": "trip_distance_exceeds_shape_distance_below_threshold",
          "count": 15,
          "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": "fast_travel_between_far_stops",
          "count": 9,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'fast_travel_between_far_stops' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 6.0,
          "severity": "WARNING",
          "what": "Fast travel between far stops (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": "trip_coverage_not_active_for_next7_days",
          "count": 1,
          "effort": "One setting in most export tools.",
          "fix": "Trim past service periods the next time you export.",
          "owner": "Likely your export tool",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Many of the feed's trips don't run at all in the next 7 days.",
          "why": "It usually means old service periods are still in the export, making the feed bigger and harder to check."
        }
      ],
      "name": "correctness",
      "score": 0.0,
      "status": "measured",
      "summary": "The MobilityData validator flagged 13 kinds of issue across 3574 instances (31 error, 3543 warning, 0 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": -1651,
        "feed_end_date": null,
        "feed_start_date": null,
        "feed_version": null,
        "has_feed_info": false,
        "last_service_date": "2021-12-31",
        "seasonal_boundary": false,
        "service_type": "fixed"
      },
      "findings": [
        {
          "code": "scorecard_feed_expired",
          "count": 1,
          "effort": "Usually one export setting; export on a schedule so it never lapses again.",
          "fix": "Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.",
          "owner": "Likely your export tool",
          "points": 100.0,
          "severity": "ERROR",
          "what": "Service data ended 1651 day(s) ago.",
          "why": "When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist."
        },
        {
          "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": 0.0,
      "status": "measured",
      "summary": "Service data ended 1651 day(s) ago. Trip planners have likely already dropped this feed.",
      "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": "2 validator errors to resolve.",
        "key": "valid",
        "met": false
      },
      {
        "detail": "Service data expired 1639 days ago.",
        "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. 2 validator errors to resolve. Service data expired 1639 days ago. 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": "93808bc5e9a2e6aeca1cd3798039824c1a20c8de3a7e7be86417156d67053afc",
    "size_bytes": 1897887,
    "static_url": "https://s3.amazonaws.com/datatools-511ny/public/Trailways-PHK.zip"
  },
  "generated_at": "2026-06-27T00:00:00+00:00",
  "geo": {
    "bbox": [
      -75.22385,
      40.75695,
      -73.72466,
      43.10408
    ],
    "lat": 42.105,
    "lon": -74.209,
    "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": [],
    "status": "unknown"
  },
  "ntd_readiness": {
    "pillars": [
      {
        "detail": "Published at a public URL.",
        "key": "published",
        "status": "ready"
      },
      {
        "detail": "2 validator errors to resolve.",
        "key": "valid",
        "status": "at_risk"
      },
      {
        "detail": "Service data expired 1639 days ago, so FTA would find the link out of date.",
        "key": "current",
        "status": "not_ready"
      }
    ],
    "status": "not_ready",
    "summary": "Resolve this before you certify on the D-10. 2 validator errors to resolve. Service data expired 1639 days ago, so FTA would find the link out of date."
  },
  "overall": {
    "grade": "F",
    "margin_to_lower_band": 2.3,
    "margin_to_next_band": 57.7,
    "score": 2.3
  },
  "recommendations": [
    {
      "code": "scorecard_stop_name_needs_tts",
      "count": 2,
      "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": "2 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"NEW PALTZ PK & RD, NY\", \"MAVERICK RD, NY\").",
      "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": 31
  },
  "rubric_version": "1.1",
  "schema_version": "1.4",
  "snapshot_date": "2026-07-09",
  "top_fixes": [
    {
      "code": "scorecard_feed_expired",
      "count": 1,
      "effort": "Usually one export setting; export on a schedule so it never lapses again.",
      "fix": "Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.",
      "owner": "Likely your export tool",
      "points": 100.0,
      "rank": 1,
      "severity": "ERROR",
      "what": "Service data ended 1651 day(s) ago.",
      "why": "When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist."
    },
    {
      "code": "trip_distance_exceeds_shape_distance",
      "count": 16,
      "effort": "Varies.",
      "fix": "Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
      "owner": "",
      "points": 18.0,
      "rank": 2,
      "severity": "ERROR",
      "what": "Trip distance exceeds shape distance (flagged by the MobilityData validator).",
      "why": "See the linked rule for what this affects."
    },
    {
      "code": "decreasing_or_equal_stop_time_distance",
      "count": 15,
      "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": 18.0,
      "rank": 3,
      "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."
    }
  ],
  "validator_version": "8.0.1"
}
