{"agency":{"id":"boston-express","name":"Boston Express"},"categories":{"completeness":{"details":{"accessibility":{"measures":"presence_not_usability","score":37.5,"stops_marked_accessible_pct":0.0,"stops_marked_not_accessible_pct":0.0,"stops_stated_pct":0.0,"trips_stated_pct":100.0},"accessibility_measures":"presence_not_usability","cemv":{"declared":false,"supported":false},"components":{"contact":15.0,"fares":0.0,"headsigns":0.0,"stop_names":15.0,"wheelchair_stops":0.0,"wheelchair_trips":15.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":74,"headsign_loop_exempt_trips":0,"headsign_pct":0.0,"headsign_scored_pct":0.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":74,"unmeasured_components":[],"wheelchair_accessible_pct":100.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 stop. A field survey can start with the busiest stops.","owner":"Likely your team","points":25.0,"severity":"WARNING","what":"6 of 6 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":["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_missing_headsigns","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_missing_headsigns","line":"Fixing this covers all 74 trips in the feed.","reach":{"affected":74,"basis":"trips","basis_label":"trips","reason":"","share":1.0,"total":74,"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":74,"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":15.0,"severity":"WARNING","what":"74 of 74 trips have no headsign, the text that tells riders where the bus is going. A trip counts when it has trip_headsign or a stop_headsign at every stop.","why":"When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming."}],"name":"completeness","score":45.0,"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":74,"WARNING":281},"validator_version":"8.0.1"},"findings":[{"code":"missing_timepoint_value","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_timepoint_value","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":279,"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":"missing_recommended_field","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_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":null,"reason":"no_ntd_id"},"served_area_need":{"reason":"not_joined_here","scale":"us_acs","tier":null}},"count":2,"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":"service_extends_far_in_the_future","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_extends_far_in_the_future","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":74,"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":1.0,"severity":"INFO","what":"Service extends far in the future (flagged by the MobilityData validator).","why":"See the linked rule for what this affects."}],"name":"correctness","score":87.0,"status":"measured","summary":"The MobilityData validator flagged 3 kinds of issue across 355 instances (0 error, 281 warning, 74 informational).","weight":0.35},"freshness":{"details":{"days_until_expiry":771,"effective_expiry_date":"2028-12-31","expiry_limited_by":"service_calendar","feed_end_date":null,"feed_start_date":null,"feed_version":"1","has_feed_info":true,"last_service_date":"2028-12-31","seasonal_boundary":false,"service_horizon_review_years":10,"service_horizon_status":"within_review_threshold","service_type":"fixed"},"findings":[{"code":"scorecard_missing_feed_info_dates","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_missing_feed_info_dates","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":"Two fields, set once in export settings.","fix":"Add feed_info.txt with feed_start_date and feed_end_date to your export.","owner":"Likely your export tool","points":15.0,"severity":"WARNING","what":"feed_info.txt is missing its start/end dates","why":"Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates."}],"name":"freshness","score":85.0,"status":"measured","summary":"Service data covers the next 771 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 771 days.","key":"current","met":true},{"detail":"States wheelchair access on 0% of stops and 100% 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 100% 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":"a6dbd479525ac1c374beef72507fbe29ae6ceaa3ce3bc5a4a1e21347274881a8","size_bytes":5812,"source_provenance":"unverified","static_url":"https://rapid.nationalrtap.org/GTFSFileManagement/UserUploadFiles/11782/GTFS.zip"},"fetch":{"final_url":"https://rapid.nationalrtap.org/GTFSFileManagement/UserUploadFiles/11782/GTFS.zip","max_attempts":4,"reader_archive_profile":"raw-v1","source":"origin","user_agent":"gtfs-scorecard/1.5.1 (+https://gtfsscorecard.org)"},"generated_at":"2026-11-09T00:00:00+00:00","geo":{"bbox":[-71.50396,42.35232,-71.01646,42.91773],"lat":42.72756,"lon":-71.3083,"stop_count":6},"mode_profile":{"ferry_only":false,"graded":false,"has_ferry":false,"is_multimodal":false,"measured":true,"modes":[{"key":"bus","label":"Bus","route_count":4,"trip_count":74,"trip_share_pct":100.0}],"primary_mode":"bus","primary_mode_label":"Bus","route_count":4,"trip_count":74},"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":["BX"],"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 771 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.4,"margin_to_next_band":6.6,"score":73.4},"recommendations":[],"recompute":{"as_of":"2026-11-21","feed_fetched_date":"2026-11-09","kind":"freshness"},"routability":{"boardable_stops":6,"findings":[],"orphan_stops":0,"single_stop_trips":0,"trips_total":74},"route_map":{"drawn_route_count":0,"has_shapes":false,"path":"data/artifacts/boston-express/geometry.geojson","route_count":4,"routes":[{"color":"005595","color_name":"teal","has_shape":false,"id":"BX3N","label":"Boston Express 3 North","long":"Boston Express 3 North","short":"","text_color":"FFEE00","type_label":"Bus"},{"color":"005595","color_name":"teal","has_shape":false,"id":"BX3S","label":"Boston Express 3 South","long":"Boston Express 3 South","short":"","text_color":"FFEE00","type_label":"Bus"},{"color":"005595","color_name":"teal","has_shape":false,"id":"BX93N","label":"Boston Express 93 North","long":"Boston Express 93 North","short":"","text_color":"FFEE00","type_label":"Bus"},{"color":"005595","color_name":"teal","has_shape":false,"id":"BX93S","label":"Boston Express 93 South","long":"Boston Express 93 South","short":"","text_color":"FFEE00","type_label":"Bus"}],"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":"No trips in this feed have a shape_id linked to a row in shapes.txt.","fix":"Add shapes.txt with a shape_id for each trip's path, and set trips.shape_id to match. Reduced, Rural, and Tribal NTD reporters need this in their published GTFS starting Report Year 2026; Full Reporters needed it in Report Year 2025.","status":"not_ready","total_trips":74,"trips_with_shape":0},"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 stop. A field survey can start with the busiest stops.","owner":"Likely your team","points":25.0,"rank":1,"severity":"WARNING","what":"6 of 6 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_missing_headsigns","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_missing_headsigns","line":"Fixing this covers all 74 trips in the feed.","reach":{"affected":74,"basis":"trips","basis_label":"trips","reason":"","share":1.0,"total":74,"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":74,"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":15.0,"rank":2,"severity":"WARNING","what":"74 of 74 trips have no headsign, the text that tells riders where the bus is going. A trip counts when it has trip_headsign or a stop_headsign at every stop.","why":"When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming."},{"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"}