{ "agency": { "id": "metro-transit-intercity-transit-city-of-seattle-community-transit-pierce-transit-sound-transit-washington-state-ferries-seattlecentermonorail-everett-transit-seattle-children-s-hospital", "name": "Puget Sound Consolidated GTFS" }, "autofix": { "available": true, "download_path": "data/artifacts/metro-transit-intercity-transit-city-of-seattle-community-transit-pierce-transit-sound-transit-washington-state-ferries-seattlecentermonorail-everett-transit-seattle-children-s-hospital/corrected.zip", "download_url": "https://d14aimrgrbaz2a.cloudfront.net/data/artifacts/metro-transit-intercity-transit-city-of-seattle-community-transit-pierce-transit-sound-transit-washington-state-ferries-seattlecentermonorail-everett-transit-seattle-children-s-hospital/corrected.zip", "fixes": [ { "code": "autofix_stop_name_case", "count": 413, "examples": [ "SODO -> Sodo", "SODO -> Sodo", "SODO -> Sodo" ], "label": "Recased shouting stop names" } ], "total": 413 }, "categories": { "completeness": { "details": { "accessibility": { "measures": "presence_not_usability", "score": 61.9, "stops_marked_accessible_pct": 62.7, "stops_marked_not_accessible_pct": 5.3, "stops_stated_pct": 68.1, "trips_stated_pct": 51.5 }, "accessibility_measures": "presence_not_usability", "components": { "contact": 7.5, "fares": 15.0, "headsigns": 14.9, "stop_names": 14.5, "wheelchair_stops": 17.0, "wheelchair_trips": 7.7 }, "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_pct": 99.3, "mixed_case_stop_name_pct": 96.9, "pathways": { "has_entrances": true, "has_levels": false, "has_pathways": false, "has_stations": true, "has_step_free": false, "pathway_count": 0 }, "stops": 13454, "trips": 153396, "wheelchair_accessible_pct": 51.5, "wheelchair_boarding_pct": 68.1, "wheelchair_marked_accessible_pct": 62.7, "wheelchair_marked_not_accessible_pct": 5.3 }, "findings": [ { "code": "scorecard_wheelchair_boarding_unknown", "count": 4297, "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": 8.0, "severity": "WARNING", "what": "4297 of 13454 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", "count": 74356, "effort": "Often one default setting in your export.", "fix": "Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).", "owner": "Likely your export tool", "points": 7.3, "severity": "WARNING", "what": "74356 of 153396 trips don't say whether the vehicle is wheelchair accessible.", "why": "Even with accessible stops, riders need to know the bus itself can take them." }, { "code": "scorecard_missing_headsigns", "count": 1098, "effort": "Usually a bulk edit in your scheduling software.", "fix": "Populate trip_headsign to match what the bus displays.", "owner": "Likely your export tool", "points": 0.1, "severity": "WARNING", "what": "1098 of 153396 trips have no headsign.", "why": "Riders at the stop can't tell which direction a bus is going." }, { "code": "scorecard_no_feed_contact", "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 with your feed, so problems linger." }, { "code": "scorecard_station_no_pathways", "count": 1, "effort": "Worth it for multi-level or large stations; flat stops don't need it.", "fix": "Add pathways.txt connecting entrances, platforms, and any elevators, with a level for each.", "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": 76.7, "status": "measured", "summary": "68% of stops state wheelchair accessibility (63% marked accessible, 5% marked not accessible). This measures what the feed publishes, not whether a stop is physically usable. Fare data is published.", "weight": 0.25 }, "correctness": { "details": { "distinct_codes": 26, "instances_by_severity": { "ERROR": 14411, "INFO": 109, "WARNING": 87157 }, "validator_version": "8.0.1" }, "findings": [ { "code": "block_trips_with_overlapping_stop_times", "count": 14408, "effort": "Varies.", "fix": "Review the rule documentation for 'block_trips_with_overlapping_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 24.0, "severity": "ERROR", "what": "Block trips with overlapping stop times (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "missing_required_agency_id", "count": 3, "effort": "Varies.", "fix": "Review the rule documentation for 'missing_required_agency_id' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 12.0, "severity": "ERROR", "what": "Missing required agency id (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "missing_timepoint_value", "count": 57522, "effort": "Varies.", "fix": "Review the rule documentation for 'missing_timepoint_value' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 8.0, "severity": "WARNING", "what": "Missing timepoint value (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "missing_bike_allowance", "count": 28761, "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": "mixed_case_recommended_field", "count": 495, "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": 8.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": "trip_distance_exceeds_shape_distance_below_threshold", "count": 142, "effort": "Varies.", "fix": "Review the rule documentation for 'trip_distance_exceeds_shape_distance_below_threshold' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 8.0, "severity": "WARNING", "what": "Trip distance exceeds shape distance below threshold (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "stop_without_stop_time", "count": 85, "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": 8.0, "severity": "WARNING", "what": "Some stops exist in the feed but no trip ever stops at them.", "why": "Riders may walk to a stop where no bus is scheduled to arrive." }, { "code": "expired_calendar", "count": 71, "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": 8.0, "severity": "WARNING", "what": "Some service calendars in the feed have already expired.", "why": "Expired calendars are dead weight and can hide real schedule problems from your staff and vendors." }, { "code": "stop_too_far_from_shape", "count": 17, "effort": "A few minutes per flagged stop.", "fix": "Check the flagged stops' coordinates and the route shape in your scheduling software; re-snap whichever is misplaced.", "owner": "Likely your export tool", "points": 6.0, "severity": "WARNING", "what": "Some stops sit far from the route line they belong to.", "why": "Trip planners may draw the bus route through the wrong streets or point riders to the wrong corner." }, { "code": "fast_travel_between_consecutive_stops", "count": 14, "effort": "A few minutes per flagged trip.", "fix": "Check the flagged stop times for transposed minutes.", "owner": "", "points": 6.0, "severity": "WARNING", "what": "Some scheduled trips travel implausibly fast between stops.", "why": "Usually a typo'd stop time; riders get impossible arrival estimates." }, { "code": "stop_too_far_from_shape_using_user_distance", "count": 10, "effort": "Varies.", "fix": "Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 6.0, "severity": "WARNING", "what": "Stop too far from shape using user distance (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "route_short_name_too_long", "count": 8, "effort": "Varies.", "fix": "Review the rule documentation for 'route_short_name_too_long' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 6.0, "severity": "WARNING", "what": "Route short name too long (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "unusable_trip", "count": 6, "effort": "Worth a vendor question if it appears often.", "fix": "Check the flagged trips in your scheduling software; remove them or restore their missing stops.", "owner": "Likely your export tool", "points": 6.0, "severity": "WARNING", "what": "Some trips serve fewer than two stops.", "why": "A trip with one stop can't be ridden; planners ignore it and it may signal an export problem." }, { "code": "unused_shape", "count": 6, "effort": "One setting.", "fix": "Enable 'remove unused shapes' (or similar) in your export tool.", "owner": "Likely your export tool", "points": 6.0, "severity": "WARNING", "what": "The feed contains route shapes no trip uses.", "why": "Harmless to riders, but it bloats the feed and suggests stale export data." }, { "code": "service_has_no_active_day_of_the_week", "count": 5, "effort": "A few minutes in your scheduling software.", "fix": "Delete the empty calendars or set their service days.", "owner": "Likely your export tool", "points": 4.0, "severity": "WARNING", "what": "Some service calendars have no days of the week switched on.", "why": "Trips tied to these calendars never run; they are dead data that can mask real schedule problems." }, { "code": "missing_feed_contact_email_and_url", "count": 4, "effort": "Varies.", "fix": "Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 4.0, "severity": "WARNING", "what": "Missing feed contact email and url (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "same_name_and_description_for_route", "count": 4, "effort": "Varies.", "fix": "Review the rule documentation for 'same_name_and_description_for_route' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 4.0, "severity": "WARNING", "what": "Same name and description for route (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "duplicate_route_name", "count": 2, "effort": "One field per route.", "fix": "Give each route a distinct short or long name.", "owner": "", "points": 4.0, "severity": "WARNING", "what": "Two or more routes share the same name.", "why": "Riders can't tell the routes apart in apps." }, { "code": "equal_shape_distance_same_coordinates", "count": 2, "effort": "Varies.", "fix": "Review the rule documentation for 'equal_shape_distance_same_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 4.0, "severity": "WARNING", "what": "Equal shape distance same coordinates (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "missing_recommended_field", "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 are missing recommended (not required) fields.", "why": "Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners." }, { "code": "more_than_one_entity", "count": 1, "effort": "Varies.", "fix": "Review the rule documentation for 'more_than_one_entity' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 4.0, "severity": "WARNING", "what": "More than one entity (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "service_window_outside_feed_period", "count": 62, "effort": "Varies.", "fix": "Review the rule documentation for 'service_window_outside_feed_period' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 1.0, "severity": "INFO", "what": "Service window outside feed period (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "platform_without_parent_station", "count": 30, "effort": "Varies.", "fix": "Review the rule documentation for 'platform_without_parent_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 0.8, "severity": "INFO", "what": "Platform without parent station (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "unknown_column", "count": 9, "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": "big_gap_in_service", "count": 7, "effort": "Varies.", "fix": "Review the rule documentation for 'big_gap_in_service' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 0.8, "severity": "INFO", "what": "Big gap in service (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "unknown_file", "count": 1, "effort": "Varies.", "fix": "Review the rule documentation for 'unknown_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 0.5, "severity": "INFO", "what": "Unknown file (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." } ], "name": "correctness", "score": 0.0, "status": "measured", "summary": "The MobilityData validator flagged 26 kinds of issue across 101677 instances (14411 error, 87157 warning, 109 informational).", "weight": 0.35 }, "freshness": { "details": { "days_until_expiry": 50, "feed_end_date": "2026-08-28", "feed_start_date": "2026-05-19", "feed_version": "SPR26-160.3-Farev2Correction", "has_feed_info": true, "last_service_date": "2027-05-30", "seasonal_boundary": false, "service_type": "fixed" }, "findings": [], "name": "freshness", "score": 83.3, "status": "measured", "summary": "Service data covers the next 50 days.", "weight": 0.2 }, "realtime": { "name": "realtime", "status": "not_yet_measured", "summary": "This agency publishes realtime, but the feed needs an access key we don't have yet. Nothing here counts against the grade.", "weight": 0.2 } }, "conformance": { "awarded": false, "criteria": [ { "detail": "2 validator errors to resolve.", "key": "valid", "met": false }, { "detail": "Service data covers the next 62 days.", "key": "current", "met": true }, { "detail": "States wheelchair access on 68% of stops and 52% of trips; the mark needs 90% of each.", "key": "accessible", "met": false } ], "status": "not_yet", "summary": "This feed is close to the conformance mark. 2 validator errors to resolve. States wheelchair access on 68% of stops and 52% of trips; the mark needs 90% of each." }, "feed": { "license_note": "No stated data license in the Mobility Database; verify before publishing.", "reachable": true, "sha256": "a0f570b8580d3dc9571efa0fff286c9444f0ff48a9b93dd7139634a3508c0010", "size_bytes": 45622165, "static_url": "https://gtfs.sound.obaweb.org/prod/gtfs_puget_sound_consolidated.zip" }, "generated_at": "2026-06-27T00:00:00+00:00", "geo": { "bbox": [ -123.01475, 46.93304, -121.601, 48.59793 ], "lat": 47.57593, "lon": -122.32204, "stop_count": 13454 }, "ntd_id_alignment": { "detail": "If you report to the National Transit Database, your GTFS agency_id should be your five-digit NTD ID by report year 2026 (2025 for full reporters). We don't have your NTD ID on file, so this one is not checked yet.", "feed_agency_ids": [ "1", "19", "20", "23", "29", "3", "40", "51", "95", "96", "97" ], "status": "unknown" }, "ntd_readiness": { "pillars": [ { "detail": "Published at a public URL.", "key": "published", "status": "ready" }, { "detail": "2 validator errors to resolve.", "key": "valid", "status": "at_risk" }, { "detail": "Service data covers the next 62 days.", "key": "current", "status": "ready" } ], "status": "at_risk", "summary": "This feed is close to NTD-ready. 2 validator errors to resolve." }, "overall": { "grade": "F", "margin_to_lower_band": 44.8, "margin_to_next_band": 15.2, "score": 44.8 }, "recommendations": [ { "code": "scorecard_route_color_low_contrast", "count": 27, "effort": "A per-route color setting in your scheduling software.", "fix": "Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.", "owner": "Likely your export tool", "points": 0.0, "severity": "WARNING", "what": "27 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (973, 975, 34, 35, 77, and more).", "why": "Low-contrast route badges are hard to read for riders with low vision and wash out on a phone screen in sunlight at the stop." }, { "code": "scorecard_stop_name_needs_tts", "count": 5688, "effort": "A short text field per affected stop; start with the busiest.", "fix": "Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.", "owner": "", "points": 0.0, "severity": "INFO", "what": "5688 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"Howell St & Yale Ave\", \"Lilly Rd at 23rd Ave\", \"26th Ave at Village St\", and more).", "why": "Riders who use a screen reader hear the raw name, so 'Main St & 2nd Ave' can come out as 'Main saint' or drop the ampersand." }, { "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 whether a step-free route exists inside the station, and trip planners can't route anyone through it." } ], "recompute": { "as_of": "2026-07-09", "feed_fetched_date": "2026-07-08", "kind": "freshness" }, "routability": { "boardable_stops": 13232, "findings": [ { "code": "scorecard_single_stop_trips", "count": 6, "effort": "Usually an export setting or a stop_times mapping in your software.", "fix": "Check your scheduling export: every trip should list each stop it calls at, in order, with times.", "owner": "Likely your export tool", "points": 0.0, "severity": "WARNING", "what": "6 of 153396 trips list fewer than two stops.", "why": "A trip with one stop has no leg a rider can ride; trip planners can't route anyone on it, so the service effectively does not exist." }, { "code": "scorecard_orphan_stops", "count": 85, "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": "85 of 13232 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": 85, "single_stop_trips": 6, "trips_total": 153396 }, "rubric_version": "1.1", "schema_version": "1.4", "snapshot_date": "2026-07-09", "top_fixes": [ { "code": "block_trips_with_overlapping_stop_times", "count": 14408, "effort": "Varies.", "fix": "Review the rule documentation for 'block_trips_with_overlapping_stop_times' 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": "Block trips with overlapping stop times (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "missing_required_agency_id", "count": 3, "effort": "Varies.", "fix": "Review the rule documentation for 'missing_required_agency_id' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 12.0, "rank": 2, "severity": "ERROR", "what": "Missing required agency id (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "missing_timepoint_value", "count": 57522, "effort": "Varies.", "fix": "Review the rule documentation for 'missing_timepoint_value' 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 timepoint value (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." } ], "validator_version": "8.0.1" }