{
  "agency": {
    "id": "seastreak-ferry",
    "name": "Seastreak Ferry",
    "subdivision_code": "US-MA",
    "subdivision_name": "Massachusetts"
  },
  "categories": {
    "completeness": {
      "details": {
        "accessibility": {
          "measures": "presence_not_usability",
          "score": 52.1,
          "stops_marked_accessible_pct": 83.3,
          "stops_marked_not_accessible_pct": 0.0,
          "stops_stated_pct": 83.3,
          "trips_stated_pct": 0.0
        },
        "accessibility_measures": "presence_not_usability",
        "cemv": {
          "declared": false,
          "supported": false
        },
        "components": {
          "contact": 7.5,
          "fares": 0.0,
          "headsigns": 12.5,
          "stop_names": 15.0,
          "wheelchair_stops": 20.8,
          "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": 310,
        "headsign_loop_exempt_trips": 0,
        "headsign_pct": 83.5,
        "headsign_scored_pct": 83.5,
        "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": 12,
        "translations": {
          "feed_lang": "EN",
          "has_translations": false,
          "languages": [],
          "translated_tables": [],
          "translation_count": 0
        },
        "trips": 310,
        "wheelchair_accessible_pct": 0.0,
        "wheelchair_boarding_pct": 83.3,
        "wheelchair_marked_accessible_pct": 83.3,
        "wheelchair_marked_not_accessible_pct": 0.0
      },
      "findings": [
        {
          "code": "scorecard_wheelchair_boarding_unknown",
          "count": 2,
          "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 terminal. A field survey can start with the busiest terminals.",
          "owner": "Likely your team",
          "points": 4.2,
          "severity": "WARNING",
          "what": "2 of 12 terminals 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": 310,
          "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": "310 of 310 trips don't say whether the vehicle is wheelchair accessible.",
          "why": "Even with accessible terminals, riders need to know the vessel 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_missing_headsigns",
          "count": 51,
          "effort": "Usually one value per route pattern in your scheduling source.",
          "fix": "Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign.",
          "owner": "",
          "points": 2.5,
          "severity": "WARNING",
          "what": "51 of 310 trips lack rider-facing destination or direction text.",
          "why": "When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming."
        },
        {
          "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": 55.9,
      "status": "measured",
      "summary": "83% of terminals state wheelchair accessibility (83% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a terminal is physically usable. Fare data is not published.",
      "weight": 0.25
    },
    "correctness": {
      "details": {
        "distinct_codes": 8,
        "instances_by_severity": {
          "ERROR": 0,
          "INFO": 8,
          "WARNING": 914
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "missing_timepoint_value",
          "count": 905,
          "effort": "Usually one export setting.",
          "fix": "Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1.",
          "owner": "Likely your export tool",
          "points": 8.0,
          "severity": "WARNING",
          "what": "Some rows in stop_times.txt leave the timepoint column blank.",
          "why": "That column says whether a time is a real checkpoint or an estimate. Blank leaves apps guessing, and they may show your estimates as promises."
        },
        {
          "code": "stops_match_shape_out_of_order",
          "count": 4,
          "effort": "A few minutes per flagged trip.",
          "fix": "Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards.",
          "owner": "Likely your export tool",
          "points": 4.0,
          "severity": "WARNING",
          "what": "On some trips the stops fall along the route line in a different order than the schedule lists.",
          "why": "Trip planners can draw the vessel doubling back or skipping ahead, which confuses riders reading the map."
        },
        {
          "code": "stop_too_far_from_shape",
          "count": 2,
          "effort": "A few minutes per flagged terminal.",
          "fix": "Check the flagged terminals' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced.",
          "owner": "Likely your export tool",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Some terminals sit far from the route line they belong to.",
          "why": "Trip planners may draw the vessel route through the wrong path or point riders to the wrong terminal."
        },
        {
          "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."
        },
        {
          "code": "missing_recommended_field",
          "count": 1,
          "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": "same_name_and_description_for_stop",
          "count": 1,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'same_name_and_description_for_stop' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Same name and description for stop (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "service_extends_far_in_the_future",
          "count": 4,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 0.5,
          "severity": "INFO",
          "what": "Service extends far in the future (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "service_window_outside_feed_period",
          "count": 4,
          "effort": "Two fields in feed_info.txt, or one export setting.",
          "fix": "Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside.",
          "owner": "Likely your export tool",
          "points": 0.5,
          "severity": "INFO",
          "what": "Some service dates fall outside the date window set in feed_info.txt.",
          "why": "feed_info.txt should span every day your service runs, so apps know when the data applies."
        }
      ],
      "name": "correctness",
      "score": 71.0,
      "status": "measured",
      "summary": "The MobilityData validator flagged 8 kinds of issue across 922 instances (0 error, 914 warning, 8 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": 1306,
        "effective_expiry_date": "2030-03-21",
        "feed_end_date": "2030-03-21",
        "feed_start_date": "2020-09-20",
        "feed_version": null,
        "has_feed_info": true,
        "last_service_date": "2030-06-15",
        "seasonal_boundary": false,
        "service_horizon_review_years": 10,
        "service_horizon_status": "within_review_threshold",
        "service_type": "fixed"
      },
      "findings": [],
      "name": "freshness",
      "score": 100.0,
      "status": "measured",
      "summary": "Service data covers the next 1306 days.",
      "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": "Passes validation with no errors.",
        "key": "valid",
        "met": true
      },
      {
        "detail": "Service data covers the next 1306 days.",
        "key": "current",
        "met": true
      },
      {
        "detail": "States wheelchair access on 83% of terminals and 0% of trips; the mark needs 90% of each.",
        "key": "accessible",
        "met": false
      }
    ],
    "status": "not_yet",
    "summary": "One requirement remains for this feed to earn the conformance mark. States wheelchair access on 83% of terminals 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": "eb88ac9bcd760708cafec5cffb0209218cbc980364a8ad609d4bdffa1e06e72c",
    "size_bytes": 13791,
    "source_provenance": "unverified",
    "static_url": "http://seastreak.com/api/transit/google_transit.zip"
  },
  "ferry_profile": {
    "accessibility": {
      "measures": "published_values_not_physical_usability",
      "terminals": {
        "allowed_count": 10,
        "allowed_pct": 83.3,
        "not_allowed_count": 0,
        "not_allowed_pct": 0.0,
        "stated_count": 10,
        "stated_pct": 83.3,
        "total_count": 12
      },
      "trips": {
        "allowed_count": 0,
        "allowed_pct": 0.0,
        "not_allowed_count": 0,
        "not_allowed_pct": 0.0,
        "stated_count": 0,
        "stated_pct": 0.0,
        "total_count": 310
      }
    },
    "bikes": {
      "allowed_count": 310,
      "allowed_pct": 100.0,
      "not_allowed_count": 0,
      "not_allowed_pct": 0.0,
      "stated_count": 310,
      "stated_pct": 100.0,
      "total_count": 310
    },
    "cars": {
      "allowed_count": 0,
      "allowed_pct": 0.0,
      "not_allowed_count": 0,
      "not_allowed_pct": 0.0,
      "stated_count": 0,
      "stated_pct": 0.0,
      "total_count": 310
    },
    "fares": {
      "applied": false,
      "fare_free": false,
      "model": "none",
      "scope": "whole_feed"
    },
    "graded": false,
    "measured": true,
    "realtime": {
      "configured_kinds": [],
      "kinds_configured": 0,
      "scope": "whole_feed"
    },
    "route_count": 4,
    "scope": "ferry_routes_and_trips",
    "stop_access": {
      "direct_count": 0,
      "eligible_terminal_count": 0,
      "stated_count": 0,
      "stated_pct": null,
      "through_station_count": 0
    },
    "terminal_hierarchy": {
      "boarding_location_count": 12,
      "parented_boarding_location_count": 0,
      "parented_boarding_location_pct": 0.0,
      "referenced_station_count": 0
    },
    "trip_count": 310
  },
  "fetch": {
    "final_url": "https://seastreak.com:443/api/transit/google_transit.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",
  "geo": {
    "bbox": [
      -74.07882,
      40.4094,
      -70.09632,
      41.63553
    ],
    "lat": 40.72952,
    "lon": -73.99991,
    "stop_count": 12
  },
  "mode_profile": {
    "ferry_only": true,
    "graded": false,
    "has_ferry": true,
    "is_multimodal": false,
    "measured": true,
    "modes": [
      {
        "key": "ferry",
        "label": "Ferry",
        "route_count": 4,
        "trip_count": 310,
        "trip_share_pct": 100.0
      }
    ],
    "primary_mode": "ferry",
    "primary_mode_label": "Ferry",
    "route_count": 4,
    "trip_count": 310
  },
  "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": [
      "20226"
    ],
    "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 1319 days.",
        "key": "current",
        "status": "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": "ready",
    "summary": "Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination."
  },
  "overall": {
    "grade": "C",
    "margin_to_lower_band": 3.5,
    "margin_to_next_band": 6.5,
    "score": 73.5
  },
  "recommendations": [
    {
      "category": "accessibility",
      "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 (\"West 39th St., NYC\", \"East 35th St., NYC\").",
      "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-08-23",
    "feed_fetched_date": "2026-08-22",
    "kind": "freshness"
  },
  "routability": {
    "boardable_stops": 12,
    "findings": [],
    "orphan_stops": 0,
    "single_stop_trips": 0,
    "trips_total": 310
  },
  "route_map": {
    "drawn_route_count": 4,
    "has_shapes": true,
    "path": "data/artifacts/seastreak-ferry/geometry.geojson",
    "route_count": 4,
    "routes": [
      {
        "color": "013067",
        "color_name": "green",
        "has_shape": true,
        "id": "211",
        "label": "Seastreak",
        "long": "New York City / New Jersey",
        "short": "Seastreak",
        "text_color": "FFFFFF",
        "type_label": "Ferry"
      },
      {
        "color": "013067",
        "color_name": "green",
        "has_shape": true,
        "id": "270",
        "label": "Seastreak",
        "long": "Martha\u2019s Vineyard / New Bedford",
        "short": "Seastreak",
        "text_color": "FFFFFF",
        "type_label": "Ferry"
      },
      {
        "color": "013067",
        "color_name": "green",
        "has_shape": true,
        "id": "272",
        "label": "Seastreak",
        "long": "Nantucket / New Bedford",
        "short": "Seastreak",
        "text_color": "FFFFFF",
        "type_label": "Ferry"
      },
      {
        "color": "013067",
        "color_name": "green",
        "has_shape": true,
        "id": "9220",
        "label": "Seastreak",
        "long": "Nantucket / Martha's Vineyard",
        "short": "Seastreak",
        "text_color": "FFFFFF",
        "type_label": "Ferry"
      }
    ],
    "stop_count": 12,
    "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": "All 310 trips have a shape in shapes.txt.",
    "status": "ready",
    "total_trips": 310,
    "trips_with_shape": 310
  },
  "snapshot_date": "2026-08-23",
  "top_fixes": [
    {
      "code": "scorecard_wheelchair_accessible_unknown",
      "count": 310,
      "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,
      "rank": 1,
      "severity": "WARNING",
      "what": "310 of 310 trips don't say whether the vehicle is wheelchair accessible.",
      "why": "Even with accessible terminals, riders need to know the vessel 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,
      "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": "missing_timepoint_value",
      "count": 905,
      "effort": "Usually one export setting.",
      "fix": "Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1.",
      "owner": "Likely your export tool",
      "points": 8.0,
      "rank": 3,
      "severity": "WARNING",
      "what": "Some rows in stop_times.txt leave the timepoint column blank.",
      "why": "That column says whether a time is a real checkpoint or an estimate. Blank leaves apps guessing, and they may show your estimates as promises."
    }
  ],
  "validator_version": "8.0.1"
}
