{ "agency": { "id": "arlington-transit", "name": "Arlington Transit" }, "autofix": { "available": true, "download_path": "data/artifacts/arlington-transit/corrected.zip", "download_url": "https://d14aimrgrbaz2a.cloudfront.net/data/artifacts/arlington-transit/corrected.zip", "fixes": [ { "code": "autofix_stop_name_case", "count": 557, "examples": [ "S CARLIN SPRINGS RD NB @ COLUMBIA PIKE FS -> S Carlin Springs Rd Nb @ Columbia Pike Fs", "S ARLINGTON MILL DR EB @ S TAYLOR ST NS -> S Arlington Mill Dr Eb @ S Taylor St Ns", "S ARLINGTON MILL DR WB @ S TAYLOR ST FS -> S Arlington Mill Dr Wb @ S Taylor St Fs" ], "label": "Recased shouting stop names" } ], "total": 557 }, "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", "components": { "contact": 7.5, "fares": 15.0, "headsigns": 15.0, "stop_names": 0.4, "wheelchair_stops": 0.0, "wheelchair_trips": 0.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_pct": 100.0, "mixed_case_stop_name_pct": 3.0, "pathways": { "has_entrances": false, "has_levels": false, "has_pathways": false, "has_stations": false, "has_step_free": false, "pathway_count": 0 }, "stops": 574, "trips": 2116, "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", "count": 574, "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": "574 of 574 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": 2116, "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": 15.0, "severity": "WARNING", "what": "2116 of 2116 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_stop_names_all_caps", "count": 557, "effort": "Often a bulk fix in your scheduling software.", "fix": "Rename stops to mixed case (e.g. 'Main St & 2nd Ave').", "owner": "Likely your export tool", "points": 14.6, "severity": "INFO", "what": "About 557 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", "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." } ], "name": "completeness", "score": 37.9, "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 published.", "weight": 0.25 }, "correctness": { "details": { "distinct_codes": 6, "instances_by_severity": { "ERROR": 0, "INFO": 0, "WARNING": 15366 }, "validator_version": "8.0.1" }, "findings": [ { "code": "leading_or_trailing_whitespaces", "count": 13662, "effort": "Varies.", "fix": "Review the rule documentation for 'leading_or_trailing_whitespaces' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 8.0, "severity": "WARNING", "what": "Leading or trailing whitespaces (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "mixed_case_recommended_field", "count": 1699, "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": "unused_shape", "count": 2, "effort": "One setting.", "fix": "Enable 'remove unused shapes' (or similar) in your export tool.", "owner": "Likely your export tool", "points": 4.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": "missing_feed_contact_email_and_url", "count": 1, "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": "missing_recommended_field", "count": 1, "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": "stop_without_stop_time", "count": 1, "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 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." } ], "name": "correctness", "score": 68.0, "status": "measured", "summary": "The MobilityData validator flagged 6 kinds of issue across 15366 instances (0 error, 15366 warning, 0 informational).", "weight": 0.35 }, "freshness": { "details": { "days_until_expiry": 326, "feed_end_date": "2027-05-31", "feed_start_date": "2026-04-12", "feed_version": "S1000054", "has_feed_info": true, "last_service_date": "2027-05-31", "seasonal_boundary": false, "service_type": "fixed" }, "findings": [], "name": "freshness", "score": 100.0, "status": "measured", "summary": "Service data covers the next 326 days.", "weight": 0.2 }, "realtime": { "details": { "coverage_pct": 92.9, "covered_trips": 13, "drift": { "median_seconds": 18, "observations": 446, "on_time_share_pct": 90.4, "p90_abs_seconds": 197 }, "kinds_reachable": 2, "rt_freshness": "fresh", "samples": 6, "scheduled_trips_in_window": 14, "vehicles_checked": 42, "vehicles_on_route_pct": 100.0, "worst_lag_seconds": 22 }, "findings": [ { "code": "scorecard_rt_service_alerts_unreachable", "count": 1, "effort": "Usually a vendor support ticket.", "fix": "Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.", "owner": "", "points": 8.3, "severity": "ERROR", "what": "The service alerts realtime feed failed during sampling.", "why": "When this feed is down, riders see scheduled times presented as if they were live." }, { "code": "scorecard_rt_trip_coverage", "count": 1, "effort": "A vendor data-mapping question.", "fix": "Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs.", "owner": "", "points": 2.5, "severity": "WARNING", "what": "1 of 14 trips scheduled during the sampling window had no live predictions.", "why": "Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates." } ], "name": "realtime", "score": 89.2, "status": "measured", "summary": "Sampled 6 times: 2 of 3 feeds healthy; 92.9% of scheduled trips had live predictions; 100.0% of vehicles on their route; predictions ran a median of 18s behind schedule.", "weight": 0.2 } }, "conformance": { "awarded": false, "criteria": [ { "detail": "Passes validation with no errors.", "key": "valid", "met": true }, { "detail": "Service data covers the next 338 days.", "key": "current", "met": true }, { "detail": "States wheelchair access on 0% of stops and 0% of trips; the mark needs 90% of each.", "key": "accessible", "met": false } ], "status": "not_yet", "summary": "This feed is close to the conformance mark. States wheelchair access on 0% of stops and 0% 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": "911218cf8f9b0a96ab450612bf879514c5a00163ac48e81fca108972e7898518", "size_bytes": 1248041, "static_url": "https://www.arlingtontransit.com/shared/content/gtfs/art/google_transit.zip" }, "generated_at": "2026-06-27T00:00:00+00:00", "geo": { "bbox": [ -77.16228, 38.83937, -77.0491, 38.92515 ], "lat": 38.88001, "lon": -77.10508, "stop_count": 574 }, "ntd_id_alignment": { "detail": "Your feed uses agency_id 1; the NTD asks for your five-digit NTD ID (30080) so the feed lines up with your record.", "feed_agency_ids": [ "1" ], "fix": "Change the agency_id to 30080 in agency.txt and update the matching agency_id in routes.txt.", "ntd_id": "30080", "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 338 days.", "key": "current", "status": "ready" } ], "status": "ready", "summary": "This feed looks ready for your NTD certification: published at a public URL, valid, and current. The official check is still your D-10 certification." }, "overall": { "grade": "C", "margin_to_lower_band": 1.1, "margin_to_next_band": 8.9, "score": 71.1 }, "recommendations": [ { "code": "scorecard_stop_name_needs_tts", "count": 573, "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": "573 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"S CARLIN SPRINGS RD NB @ COLUMBIA PIKE FS\", \"S ARLINGTON MILL DR EB @ S TAYLOR ST NS\", \"S ARLINGTON MILL DR WB @ S TAYLOR ST FS\", 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." } ], "recompute": { "as_of": "2026-07-09", "feed_fetched_date": "2026-07-08", "kind": "freshness" }, "routability": { "boardable_stops": 574, "findings": [ { "code": "scorecard_orphan_stops", "count": 1, "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": "1 of 574 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": 1, "single_stop_trips": 0, "trips_total": 2116 }, "rubric_version": "1.1", "schema_version": "1.4", "snapshot_date": "2026-07-09", "top_fixes": [ { "code": "scorecard_rt_service_alerts_unreachable", "count": 1, "effort": "Usually a vendor support ticket.", "fix": "Check the service alerts endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.", "owner": "", "points": 8.3, "rank": 1, "severity": "ERROR", "what": "The service alerts realtime feed failed during sampling.", "why": "When this feed is down, riders see scheduled times presented as if they were live." }, { "code": "scorecard_wheelchair_boarding_unknown", "count": 574, "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": 2, "severity": "WARNING", "what": "574 of 574 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": 2116, "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": 15.0, "rank": 3, "severity": "WARNING", "what": "2116 of 2116 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." } ], "validator_version": "8.0.1" }