{"agency":{"id":"casco-bay-lines","name":"Casco Bay Lines","operating_note":"Checked 2026-11-08: the feed URL on file had stopped working, so this record now tracks gtfs.remix.com, the address the Mobility Database lists for the record that replaced this one. The agency name and service area in that file match this record. Grades dated before this change came from an older Mobility Database mirror copy.","subdivision_code":"US-ME","subdivision_name":"Maine"},"categories":{"completeness":{"details":{"accessibility":{"measures":"presence_not_usability","score":93.6,"stops_marked_accessible_pct":90.0,"stops_marked_not_accessible_pct":0.0,"stops_stated_pct":90.0,"trips_stated_pct":99.7},"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":22.5,"wheelchair_trips":15.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":1349,"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":true,"has_step_free":false,"pathway_count":0},"stops":10,"translations":{"feed_lang":"en","has_translations":false,"languages":[],"translated_tables":[],"translation_count":0},"trips":1349,"unmeasured_components":[],"wheelchair_accessible_pct":99.7,"wheelchair_boarding_pct":90.0,"wheelchair_marked_accessible_pct":90.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 1 of 10 stops, about 10% of them.","reach":{"affected":1,"basis":"stops","basis_label":"stops","reason":"","share":0.1,"total":10,"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":1,"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":2.5,"severity":"WARNING","what":"1 of 10 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 4 of 1,349 trips, under 1% of them.","reach":{"affected":4,"basis":"trips","basis_label":"trips","reason":"","share":0.003,"total":1349,"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":4,"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":0.0,"severity":"WARNING","what":"4 of 1349 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_station_no_pathways","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_station_no_pathways","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":"Worth it for multi-level or large stations; flat stops don't need it.","fix":"Add pathways.txt to link entrances, platforms, and elevators. Give each one a level.","owner":"","points":0.0,"severity":"WARNING","what":"This feed models stations or entrances but has no pathways.txt.","why":"Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users."}],"name":"completeness","score":97.5,"status":"measured","summary":"90% of terminals state wheelchair accessibility (90% 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":8,"instances_by_severity":{"ERROR":137,"INFO":1353,"WARNING":133},"validator_version":"8.0.1"},"findings":[{"code":"trip_distance_exceeds_shape_distance","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":"trip_distance_exceeds_shape_distance","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":137,"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":24.0,"severity":"ERROR","what":"Trip distance exceeds shape distance (flagged by the MobilityData validator).","why":"See the linked rule for what this affects."},{"code":"trip_distance_exceeds_shape_distance_below_threshold","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":"trip_distance_exceeds_shape_distance_below_threshold","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":108,"effort":"Usually an export-tool fix, not hand editing.","fix":"Re-generate shape_dist_traveled on export so stop and shape distances use the same units.","owner":"Likely your export tool","points":8.0,"severity":"WARNING","what":"On some trips the stop distances run a little past the end of the route line.","why":"The stop and shape distance values don't quite line up, so any math that uses them can drift."},{"code":"expired_calendar","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":"expired_calendar","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":18,"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":"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":4,"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":4.0,"severity":"WARNING","what":"Missing bike allowance (flagged by the MobilityData validator).","why":"See the linked rule for what this affects."},{"code":"stop_too_far_from_shape_using_user_distance","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_too_far_from_shape_using_user_distance","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":3,"effort":"Usually an export-tool fix, not hand editing.","fix":"Check the flagged terminals' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.","owner":"Likely your export tool","points":4.0,"severity":"WARNING","what":"Some terminals sit far from the route line, going by the feed's own distance values.","why":"Trip planners may draw the route down the wrong path or point riders to the wrong terminal."},{"code":"unsorted_stop_times","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":"unsorted_stop_times","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":1349,"effort":"Varies.","fix":"Review the rule documentation for 'unsorted_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.","owner":"","points":1.0,"severity":"INFO","what":"Unsorted stop times (flagged by the MobilityData validator).","why":"See the linked rule for what this affects."},{"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":2,"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.5,"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":2,"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.5,"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."}],"name":"correctness","score":52.0,"status":"measured","summary":"The MobilityData validator flagged 8 kinds of issue across 1623 instances (137 error, 133 warning, 1353 informational).","weight":0.35},"freshness":{"details":{"days_until_expiry":180,"effective_expiry_date":"2027-05-20","expiry_limited_by":"both","feed_end_date":"2027-05-20","feed_start_date":"2026-05-22","feed_version":"Updated: Oct 16, 2026, 1:39 PM","has_feed_info":true,"last_service_date":"2027-05-20","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 180 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":"1 validator error to resolve.","key":"valid","met":false},{"detail":"Service data covers the next 180 days.","key":"current","met":true},{"detail":"States wheelchair access on 90% of terminals and 100% of trips.","key":"accessible","met":true}],"status":"not_yet","summary":"One requirement remains for this feed to earn the conformance mark. 1 validator error to resolve.","version":2},"feed":{"license_note":"No stated data license in the Mobility Database; verify before publishing.","reachable":true,"sha256":"0c8766f80b170cede2266f013d4d0c572f011d417367672ce6811ee79b535be4","size_bytes":67507,"source_provenance":"unverified","static_url":"https://gtfs.remix.com/Casco_Bay_Lines_Portland_ME_USA.zip"},"ferry_profile":{"accessibility":{"measures":"published_values_not_physical_usability","terminals":{"allowed_count":9,"allowed_pct":100.0,"not_allowed_count":0,"not_allowed_pct":0.0,"stated_count":9,"stated_pct":100.0,"total_count":9},"trips":{"allowed_count":1345,"allowed_pct":99.7,"not_allowed_count":0,"not_allowed_pct":0.0,"stated_count":1345,"stated_pct":99.7,"total_count":1349}},"bikes":{"allowed_count":1345,"allowed_pct":99.7,"not_allowed_count":0,"not_allowed_pct":0.0,"stated_count":1345,"stated_pct":99.7,"total_count":1349},"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":1349},"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":2,"stated_count":0,"stated_pct":0.0,"through_station_count":0},"terminal_hierarchy":{"boarding_location_count":9,"parented_boarding_location_count":2,"parented_boarding_location_pct":22.2,"referenced_station_count":1},"trip_count":1349},"fetch":{"final_url":"https://gtfs.remix.com/Casco_Bay_Lines_Portland_ME_USA.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":[-70.24849,43.65546,-70.10992,43.71632],"lat":43.66677,"lon":-70.1998,"stop_count":10},"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":1349,"trip_share_pct":100.0}],"primary_mode":"ferry","primary_mode_label":"Ferry","route_count":3,"trip_count":1349},"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":["10088"],"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 180 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":"at_risk","summary":"This feed is close to NTD-ready. 1 validator error to resolve."},"overall":{"grade":"C","margin_to_lower_band":8.2,"margin_to_next_band":1.8,"score":78.2},"recommendations":[{"category":"accessibility","code":"scorecard_station_missing_step_free_data","count":2,"effort":"Worth it for multi-level or large stations; flat stops don't need it.","fix":"Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.","owner":"","points":0.0,"severity":"WARNING","what":"This feed models stations or entrances but has no pathways.txt and levels.txt.","why":"Without pathways and levels, a wheelchair user can't tell if a step-free route exists inside the station. Trip planners can't route anyone through it."}],"routability":{"boardable_stops":9,"findings":[],"orphan_stops":0,"single_stop_trips":0,"trips_total":1349},"route_map":{"drawn_route_count":3,"has_shapes":true,"path":"data/artifacts/casco-bay-lines/geometry.geojson","route_count":3,"routes":[{"color":"613FA6","color_name":"purple","has_shape":true,"id":"DB","label":"DB","long":"Down Bay Islands","short":"DB","text_color":"FFFFFF","type_label":"Ferry"},{"color":"007AB8","color_name":"teal","has_shape":true,"id":"IB","label":"IB","long":"Inner Bay Islands","short":"IB","text_color":"FFFFFF","type_label":"Ferry"},{"color":"D6393C","color_name":"red","has_shape":true,"id":"PK","label":"PK","long":"Peaks Island","short":"PK","text_color":"FFFFFF","type_label":"Ferry"}],"stop_count":10,"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 1349 trips have a shape in shapes.txt.","status":"ready","total_trips":1349,"trips_with_shape":1349},"snapshot_date":"2026-11-21","top_fixes":[{"code":"trip_distance_exceeds_shape_distance","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":"trip_distance_exceeds_shape_distance","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":137,"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":24.0,"rank":1,"severity":"ERROR","what":"Trip distance exceeds shape distance (flagged by the MobilityData validator).","why":"See the linked rule for what this affects."},{"code":"trip_distance_exceeds_shape_distance_below_threshold","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":"trip_distance_exceeds_shape_distance_below_threshold","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":108,"effort":"Usually an export-tool fix, not hand editing.","fix":"Re-generate shape_dist_traveled on export so stop and shape distances use the same units.","owner":"Likely your export tool","points":8.0,"rank":2,"severity":"WARNING","what":"On some trips the stop distances run a little past the end of the route line.","why":"The stop and shape distance values don't quite line up, so any math that uses them can drift."},{"code":"expired_calendar","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":"expired_calendar","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":18,"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,"rank":3,"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."}],"validator_version":"8.0.1"}