{"agency":{"id":"lake-champlain-ferries","name":"Lake Champlain Ferries","subdivision_code":"US-VT","subdivision_name":"Vermont"},"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":0.0,"headsigns":15.0,"stop_names":15.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":true},"has_fares":false,"headsign_applicable_trips":369,"headsign_loop_exempt_trips":0,"headsign_pct":100.0,"headsign_scored_pct":100.0,"headsign_stop_headsign_trips":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":6,"translations":{"feed_lang":"en","has_translations":false,"languages":[],"translated_tables":[],"translation_count":0},"trips":369,"unmeasured_components":[],"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","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"scorecard_wheelchair_boarding_unknown","line":"Fixing this covers all 6 stops in the feed.","reach":{"affected":6,"basis":"stops","basis_label":"stops","reason":"","share":1.0,"total":6,"total_source":"geo.stop_count"},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":6,"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":"6 of 6 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","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"scorecard_wheelchair_accessible_unknown","line":"Fixing this covers all 369 trips in the feed.","reach":{"affected":369,"basis":"trips","basis_label":"trips","reason":"","share":1.0,"total":369,"total_source":"routability.trips_total"},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":369,"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":"369 of 369 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","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"scorecard_no_fare_data","line":"This one is about the feed as a whole, so there is no share of it to count.","reach":{"affected":null,"basis":"none","basis_label":null,"reason":"feed_level","share":null,"total":null,"total_source":null},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"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_flex_no_booking_rules","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"scorecard_flex_no_booking_rules","line":"What this one counts is not stops, routes, or trips, so there is no network share.","reach":{"affected":null,"basis":"none","basis_label":null,"reason":"not_network_countable","share":null,"total":null,"total_source":null},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":1,"effort":"A small file; one rule often covers the whole service.","fix":"Add booking_rules.txt saying how far ahead and how to book (phone, app, or web).","owner":"","points":0.0,"severity":"WARNING","what":"This feed offers flexible service that riders book ahead, but it has no booking_rules.txt.","why":"Riders can see the service area but not how or when to book a trip. Without that, they can't use the service."}],"name":"completeness","score":45.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 not published.","weight":0.25},"correctness":{"details":{"distinct_codes":5,"instances_by_severity":{"ERROR":0,"INFO":46,"WARNING":371},"validator_version":"8.0.1"},"findings":[{"code":"missing_bike_allowance","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"missing_bike_allowance","line":"This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.","reach":{"affected":null,"basis":"none","basis_label":null,"reason":"validator_notice","share":null,"total":null,"total_source":null},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":369,"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":"stop_without_stop_time","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"stop_without_stop_time","line":"This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.","reach":{"affected":null,"basis":"none","basis_label":null,"reason":"validator_notice","share":null,"total":null,"total_source":null},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":2,"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 terminals exist in the feed but no trip serves them.","why":"Riders may go to a terminal where no vessel is scheduled to arrive."},{"code":"unknown_column","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"unknown_column","line":"This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.","reach":{"affected":null,"basis":"none","basis_label":null,"reason":"validator_notice","share":null,"total":null,"total_source":null},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":34,"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","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"unknown_file","line":"This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.","reach":{"affected":null,"basis":"none","basis_label":null,"reason":"validator_notice","share":null,"total":null,"total_source":null},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":8,"effort":"A quick look at the flagged file.","fix":"Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra.","owner":"","points":0.8,"severity":"INFO","what":"The feed includes a file that is not part of the GTFS spec.","why":"Apps ignore files they don't know, and a stray file can hide a misspelled standard file name."},{"code":"service_window_outside_feed_period","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"service_window_outside_feed_period","line":"This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.","reach":{"affected":null,"basis":"none","basis_label":null,"reason":"validator_notice","share":null,"total":null,"total_source":null},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"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":86.0,"status":"measured","summary":"The MobilityData validator flagged 5 kinds of issue across 417 instances (0 error, 371 warning, 46 informational).","weight":0.35},"freshness":{"details":{"days_until_expiry":161,"effective_expiry_date":"2027-05-01","expiry_limited_by":"both","feed_end_date":"2027-05-01","feed_start_date":"2026-11-10","feed_version":"UTC: 10-Nov-2026 19:41","has_feed_info":true,"last_service_date":"2027-05-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 161 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 161 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":"b9f5c5d27cf4926b1521417b92d34fb5e416d42589935de2a0884115472d3111","size_bytes":14405,"source_provenance":"unverified","static_url":"https://data.trilliumtransit.com/gtfs/lctferries-vt-us/lctferries-vt-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":4},"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":369}},"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":369},"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":369},"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":2,"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":4,"parented_boarding_location_count":0,"parented_boarding_location_pct":0.0,"referenced_station_count":0},"trip_count":369},"fetch":{"final_url":"https://data.trilliumtransit.com/gtfs/lctferries-vt-us/lctferries-vt-us.zip","max_attempts":4,"reader_archive_profile":"raw-v1","source":"origin","user_agent":"gtfs-scorecard/1.5.1 (+https://gtfsscorecard.org/fetcher/)"},"generated_at":"2026-11-21T00:00:00+00:00","geo":{"bbox":[-73.40337,44.3014,-73.2212,44.69903],"lat":44.50052,"lon":-73.35029,"stop_count":6},"mode_profile":{"ferry_only":true,"graded":false,"has_ferry":true,"is_multimodal":false,"measured":true,"modes":[{"key":"ferry","label":"Ferry","route_count":2,"trip_count":369,"trip_share_pct":100.0}],"primary_mode":"ferry","primary_mode_label":"Ferry","route_count":2,"trip_count":369},"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":["789"],"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 161 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":6.7,"margin_to_next_band":3.3,"score":76.7},"recommendations":[{"category":"flex","code":"scorecard_flex_completeness_no_booking_rules","count":1,"effort":"A small file; one rule often covers the whole service.","fix":"Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).","owner":"","points":0.0,"severity":"WARNING","what":"Flex zones are published but no booking_rules.txt is present.","why":"Riders can see the service area but not how to book, so they can't complete a trip."}],"routability":{"boardable_stops":6,"findings":[{"code":"scorecard_orphan_stops","count":2,"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":"2 of 6 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":2,"single_stop_trips":0,"trips_total":369},"route_map":{"drawn_route_count":2,"has_shapes":true,"path":"data/artifacts/lake-champlain-ferries/geometry.geojson","route_count":2,"routes":[{"color":"246BB7","color_name":"teal","has_shape":true,"id":"9703","label":"Grand Isle, VT \u2013 Plattsburgh, NY","long":"Grand Isle, VT \u2013 Plattsburgh, NY","short":"","text_color":"FFFFFF","type_label":"Ferry"},{"color":"347009","color_name":"green","has_shape":true,"id":"9704","label":"Charlotte, VT \u2013 Essex, NY","long":"Charlotte, VT \u2013 Essex, NY","short":"","text_color":"FFFFFF","type_label":"Ferry"}],"stop_count":6,"stop_points_capped":false},"rubric_version":"1.5","schema_version":"1.20","scoring_profile":{"id":"gtfs-scorecard-1.5","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.5"},"shapes_readiness":{"detail":"All 369 trips have a shape in shapes.txt.","status":"ready","total_trips":369,"trips_with_shape":369},"snapshot_date":"2026-11-21","top_fixes":[{"code":"scorecard_wheelchair_boarding_unknown","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"scorecard_wheelchair_boarding_unknown","line":"Fixing this covers all 6 stops in the feed.","reach":{"affected":6,"basis":"stops","basis_label":"stops","reason":"","share":1.0,"total":6,"total_source":"geo.stop_count"},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":6,"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":"6 of 6 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","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"scorecard_wheelchair_accessible_unknown","line":"Fixing this covers all 369 trips in the feed.","reach":{"affected":369,"basis":"trips","basis_label":"trips","reason":"","share":1.0,"total":369,"total_source":"routability.trips_total"},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":369,"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":"369 of 369 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","consequence":{"absences":["This feed carries no National Transit Database ID, so annual rider-trips are not known for it.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"scorecard_no_fare_data","line":"This one is about the feed as a whole, so there is no share of it to count.","reach":{"affected":null,"basis":"none","basis_label":null,"reason":"feed_level","share":null,"total":null,"total_source":null},"ridership":{"annual_rider_trips":null,"ntd_id":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"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":3,"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."}],"validator_version":"8.0.1"}