{ "agency": { "id": "hy-line-cruises", "name": "Hy-Line Cruises", "subdivision_code": "US-MA", "subdivision_name": "Massachusetts" }, "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": 15.0, "fares": 15.0, "headsigns": 15.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": false, "booking_rule_count": 0, "has_booking_rules": false, "has_flex": false }, "has_fares": true, "headsign_applicable_trips": 250, "headsign_loop_exempt_trips": 0, "headsign_pct": 100.0, "headsign_scored_pct": 100.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": 3, "translations": { "feed_lang": "en", "has_translations": false, "languages": [], "translated_tables": [], "translation_count": 0 }, "trips": 250, "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": 3, "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": 25.0, "severity": "WARNING", "what": "3 of 3 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": 250, "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": "250 of 250 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." } ], "name": "completeness", "score": 60.0, "status": "measured", "summary": "0% of terminals state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a terminal is physically usable. Fare data is published.", "weight": 0.25 }, "correctness": { "details": { "distinct_codes": 3, "instances_by_severity": { "ERROR": 0, "INFO": 3, "WARNING": 257 }, "validator_version": "8.0.1" }, "findings": [ { "code": "missing_bike_allowance", "count": 250, "effort": "Varies.", "fix": "Review the rule documentation for 'missing_bike_allowance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 8.0, "severity": "WARNING", "what": "Missing bike allowance (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "expired_calendar", "count": 7, "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 ended.", "why": "Expired calendars are dead weight and can hide real schedule problems from your staff and vendors." }, { "code": "big_gap_in_service", "count": 3, "effort": "A review of your calendar dates.", "fix": "Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar.", "owner": "", "points": 0.5, "severity": "INFO", "what": "The feed has a stretch of two weeks or more with no service running.", "why": "A long gap can mean dates were left out of the calendar. Apps then show no trips on those days." } ], "name": "correctness", "score": 85.5, "status": "measured", "summary": "The MobilityData validator flagged 3 kinds of issue across 260 instances (0 error, 257 warning, 3 informational).", "weight": 0.35 }, "freshness": { "details": { "days_until_expiry": 70, "effective_expiry_date": "2026-11-01", "feed_end_date": "2026-11-01", "feed_start_date": "2026-03-30", "feed_version": "UTC: 22-Apr-2026 21:46", "has_feed_info": true, "last_service_date": "2026-11-01", "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 70 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 70 days.", "key": "current", "met": true }, { "detail": "States wheelchair access on 0% 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 0% 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": "d4ba7f9049d8fe88131f824885ebc87d8affd590c4e12ff0ae77488d2098c1bb", "size_bytes": 14364, "source_provenance": "unverified", "static_url": "https://data.trilliumtransit.com/gtfs/hylinecruises-ma-us/hylinecruises-ma-us.zip" }, "ferry_profile": { "accessibility": { "measures": "published_values_not_physical_usability", "terminals": { "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": 3 }, "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": 250 } }, "bikes": { "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": 250 }, "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": 250 }, "fares": { "applied": true, "fare_free": false, "model": "legacy", "scope": "whole_feed" }, "graded": false, "measured": true, "realtime": { "configured_kinds": [], "kinds_configured": 0, "scope": "whole_feed" }, "route_count": 3, "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": 3, "parented_boarding_location_count": 0, "parented_boarding_location_pct": 0.0, "referenced_station_count": 0 }, "trip_count": 250 }, "fetch": { "final_url": "https://data.trilliumtransit.com/gtfs/hylinecruises-ma-us/hylinecruises-ma-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", "geo": { "bbox": [ -70.5588, 41.28468, -70.0948, 41.6483 ], "lat": 41.45844, "lon": -70.27914, "stop_count": 3 }, "mode_profile": { "ferry_only": true, "graded": false, "has_ferry": true, "is_multimodal": false, "measured": true, "modes": [ { "key": "ferry", "label": "Ferry", "route_count": 3, "trip_count": 250, "trip_share_pct": 100.0 } ], "primary_mode": "ferry", "primary_mode_label": "Ferry", "route_count": 3, "trip_count": 250 }, "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": [ "279" ], "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 83 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": "B", "margin_to_lower_band": 1.2, "margin_to_next_band": 8.8, "score": 81.2 }, "recommendations": [], "recompute": { "as_of": "2026-08-23", "feed_fetched_date": "2026-08-22", "kind": "freshness" }, "routability": { "boardable_stops": 3, "findings": [], "orphan_stops": 0, "single_stop_trips": 0, "trips_total": 250 }, "route_map": { "drawn_route_count": 3, "has_shapes": true, "path": "data/artifacts/hy-line-cruises/geometry.geojson", "route_count": 3, "routes": [ { "color": "1B7FA8", "color_name": "teal", "has_shape": true, "id": "2112", "label": "Inter-Island", "long": "Inter-Island", "short": "", "text_color": "000000", "type_label": "Ferry" }, { "color": "1B7FA8", "color_name": "teal", "has_shape": true, "id": "2113", "label": "Martha's Vineyard High-Speed", "long": "Martha's Vineyard High-Speed", "short": "", "text_color": "000000", "type_label": "Ferry" }, { "color": "1B7FA8", "color_name": "teal", "has_shape": true, "id": "2115", "label": "Nantucket High-Speed", "long": "Nantucket High-Speed", "short": "", "text_color": "000000", "type_label": "Ferry" } ], "stop_count": 3, "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 250 trips have a shape in shapes.txt.", "status": "ready", "total_trips": 250, "trips_with_shape": 250 }, "snapshot_date": "2026-08-23", "top_fixes": [ { "code": "scorecard_wheelchair_boarding_unknown", "count": 3, "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": 25.0, "rank": 1, "severity": "WARNING", "what": "3 of 3 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": 250, "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": 2, "severity": "WARNING", "what": "250 of 250 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": "missing_bike_allowance", "count": 250, "effort": "Varies.", "fix": "Review the rule documentation for 'missing_bike_allowance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 8.0, "rank": 3, "severity": "WARNING", "what": "Missing bike allowance (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." } ], "validator_version": "8.0.1" }