{"agency":{"id":"connecticut-transit-2840","name":"Hartford Line - Rail","subdivision_code":"US-CT","subdivision_name":"Connecticut"},"categories":{"completeness":{"details":{"accessibility":{"measures":"presence_not_usability","score":33.2,"stops_marked_accessible_pct":0.0,"stops_marked_not_accessible_pct":0.0,"stops_stated_pct":0.0,"trips_stated_pct":88.6},"accessibility_measures":"presence_not_usability","cemv":{"declared":false,"supported":false},"components":{"contact":7.5,"fares":0.0,"headsigns":15.0,"stop_names":0.0,"wheelchair_stops":0.0,"wheelchair_trips":13.3},"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":35,"headsign_loop_exempt_trips":0,"headsign_pct":100.0,"headsign_scored_pct":100.0,"headsign_stop_headsign_trips":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":9,"translations":{"feed_lang":"en","has_translations":false,"languages":[],"translated_tables":[],"translation_count":0},"trips":35,"unmeasured_components":[],"wheelchair_accessible_pct":88.6,"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":["More than one feed record claims this National Transit Database reporter, so its rider-trips are held back rather than counted against any single feed.","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 9 stops in the feed.","reach":{"affected":9,"basis":"stops","basis_label":"stops","reason":"","share":1.0,"total":9,"total_source":"geo.stop_count"},"ridership":{"annual_rider_trips":null,"ntd_id":"10048","reason":"duplicate_ntd_reporter"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":9,"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":"9 of 9 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","consequence":{"absences":["More than one feed record claims this National Transit Database reporter, so its rider-trips are held back rather than counted against any single feed.","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 35 trips, about 11% of them.","reach":{"affected":4,"basis":"trips","basis_label":"trips","reason":"","share":0.1143,"total":35,"total_source":"routability.trips_total"},"ridership":{"annual_rider_trips":null,"ntd_id":"10048","reason":"duplicate_ntd_reporter"},"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":1.7,"severity":"WARNING","what":"4 of 35 trips don't say whether the vehicle is wheelchair accessible.","why":"Even with accessible stops, riders need to know the transit vehicle itself can take them."},{"code":"scorecard_no_fare_data","consequence":{"absences":["More than one feed record claims this National Transit Database reporter, so its rider-trips are held back rather than counted against any single feed.","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":"10048","reason":"duplicate_ntd_reporter"},"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_stop_names_all_caps","consequence":{"absences":["More than one feed record claims this National Transit Database reporter, so its rider-trips are held back rather than counted against any single feed.","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_stop_names_all_caps","line":"Fixing this covers all 9 stops in the feed.","reach":{"affected":9,"basis":"stops","basis_label":"stops","reason":"","share":1.0,"total":9,"total_source":"geo.stop_count"},"ridership":{"annual_rider_trips":null,"ntd_id":"10048","reason":"duplicate_ntd_reporter"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":9,"effort":"Often a bulk fix in your scheduling software.","fix":"Rename stops to mixed case where the language has letter case (for example, 'Central Station').","owner":"Likely your export tool","points":15.0,"severity":"INFO","what":"About 9 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_no_feed_contact","consequence":{"absences":["More than one feed record claims this National Transit Database reporter, so its rider-trips are held back rather than counted against any single feed.","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_feed_contact","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":"10048","reason":"duplicate_ntd_reporter"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"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. Small errors then sit in the feed for months."}],"name":"completeness","score":35.8,"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":3,"instances_by_severity":{"ERROR":0,"INFO":0,"WARNING":235},"validator_version":"8.0.1"},"findings":[{"code":"stop_too_far_from_shape_using_user_distance","consequence":{"absences":["More than one feed record claims this National Transit Database reporter, so its rider-trips are held back rather than counted against any single feed.","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":"10048","reason":"duplicate_ntd_reporter"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":229,"effort":"Usually an export-tool fix, not hand editing.","fix":"Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.","owner":"Likely your export tool","points":8.0,"severity":"WARNING","what":"Some stops 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 boarding location."},{"code":"mixed_case_recommended_field","consequence":{"absences":["More than one feed record claims this National Transit Database reporter, so its rider-trips are held back rather than counted against any single feed.","This record does not store transit need. The agency page and its reports add it from the need overlays and name their date."],"code":"mixed_case_recommended_field","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":"10048","reason":"duplicate_ntd_reporter"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":5,"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":4.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":"missing_feed_contact_email_and_url","consequence":{"absences":["More than one feed record claims this National Transit Database reporter, so its rider-trips are held back rather than counted against any single feed.","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_feed_contact_email_and_url","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":"10048","reason":"duplicate_ntd_reporter"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"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."}],"name":"correctness","score":84.0,"status":"measured","summary":"The MobilityData validator flagged 3 kinds of issue across 235 instances (0 error, 235 warning, 0 informational).","weight":0.35},"freshness":{"details":{"days_until_expiry":317,"effective_expiry_date":"2027-10-04","expiry_limited_by":"both","feed_end_date":"2027-10-04","feed_start_date":"2026-10-05","feed_version":"S1000061","has_feed_info":true,"last_service_date":"2027-10-04","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 317 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 317 days.","key":"current","met":true},{"detail":"States wheelchair access on 0% of stops and 89% 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 stops and 89% of trips; the mark needs 90% of each.","version":2},"feed":{"license_note":"License: https://www.cttransit.com/about/developers/terms-of-use","reachable":true,"sha256":"569aac0a38c1b726059991c566d93412fcc9f9836b1f0b332b3b9b624024c4ba","size_bytes":2800098,"source_provenance":"unverified","static_url":"https://ctrides.com/hlgtfs.zip"},"fetch":{"final_url":"https://ctrides.com/hlgtfs.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":[-72.92559,41.29757,-72.5938,42.10569],"lat":41.63606,"lon":-72.76523,"stop_count":9},"mode_profile":{"ferry_only":false,"graded":false,"has_ferry":false,"is_multimodal":false,"measured":true,"modes":[{"key":"rail","label":"Rail","route_count":1,"trip_count":35,"trip_share_pct":100.0}],"primary_mode":"rail","primary_mode_label":"Rail","route_count":1,"trip_count":35},"ntd_id_alignment":{"detail":"Your feed's agency_id is 1; your National Transit Database ID is 10048. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score.","feed_agency_ids":["1"],"fix":"Confirm that P-50 crosswalks agency_id 1 to NTD ID 10048, and keep the feed value stable. Do not change it solely to make the two values equal.","ntd_id":"10048","status":"mismatch"},"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 317 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":2.9,"margin_to_next_band":7.1,"score":72.9},"recommendations":[],"routability":{"boardable_stops":9,"findings":[],"orphan_stops":0,"single_stop_trips":0,"trips_total":35},"route_map":{"drawn_route_count":1,"has_shapes":true,"path":"data/artifacts/connecticut-transit-2840/geometry.geojson","route_count":1,"routes":[{"color":"FFFFFF","color_name":"white","has_shape":true,"id":"HART","label":"Hartford Line","long":"Hartford Line","short":"","text_color":"000000","type_label":"Rail"}],"stop_count":9,"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 35 trips have a shape in shapes.txt.","status":"ready","total_trips":35,"trips_with_shape":35},"snapshot_date":"2026-11-21","top_fixes":[{"code":"scorecard_wheelchair_boarding_unknown","consequence":{"absences":["More than one feed record claims this National Transit Database reporter, so its rider-trips are held back rather than counted against any single feed.","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 9 stops in the feed.","reach":{"affected":9,"basis":"stops","basis_label":"stops","reason":"","share":1.0,"total":9,"total_source":"geo.stop_count"},"ridership":{"annual_rider_trips":null,"ntd_id":"10048","reason":"duplicate_ntd_reporter"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":9,"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,"rank":1,"severity":"WARNING","what":"9 of 9 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_no_fare_data","consequence":{"absences":["More than one feed record claims this National Transit Database reporter, so its rider-trips are held back rather than counted against any single feed.","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":"10048","reason":"duplicate_ntd_reporter"},"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":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":"stop_too_far_from_shape_using_user_distance","consequence":{"absences":["More than one feed record claims this National Transit Database reporter, so its rider-trips are held back rather than counted against any single feed.","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":"10048","reason":"duplicate_ntd_reporter"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":229,"effort":"Usually an export-tool fix, not hand editing.","fix":"Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.","owner":"Likely your export tool","points":8.0,"rank":3,"severity":"WARNING","what":"Some stops 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 boarding location."}],"validator_version":"8.0.1"}