{ "agency": { "id": "metropolitan-atlanta-rapid-transit-authority-marta", "name": "Metropolitan Atlanta Rapid Transit Authority (MARTA)" }, "autofix": { "available": true, "download_path": "data/artifacts/metropolitan-atlanta-rapid-transit-authority-marta/corrected.zip", "download_url": "https://d14aimrgrbaz2a.cloudfront.net/data/artifacts/metropolitan-atlanta-rapid-transit-authority-marta/corrected.zip", "fixes": [ { "code": "autofix_trim_whitespace", "count": 1, "examples": [ "'stop_desc': '0 ' -> '0'" ], "label": "Trimmed surrounding whitespace" }, { "code": "autofix_stop_name_case", "count": 7033, "examples": [ "HAMILTON E HOLMES STATION -> Hamilton E Holmes Station", "WEST LAKE STATION -> West Lake Station", "WEST LAKE STATION -> West Lake Station" ], "label": "Recased shouting stop names" }, { "code": "autofix_route_name_case", "count": 3, "examples": [ "BLUE -> Blue", "GOLD -> Gold", "GREEN -> Green" ], "label": "Recased shouting route names" } ], "total": 7037 }, "categories": { "completeness": { "details": { "accessibility": { "measures": "presence_not_usability", "score": 74.9, "stops_marked_accessible_pct": 59.8, "stops_marked_not_accessible_pct": 0.0, "stops_stated_pct": 59.8, "trips_stated_pct": 100.0 }, "accessibility_measures": "presence_not_usability", "components": { "contact": 7.5, "fares": 0.0, "headsigns": 14.9, "stop_names": 0.1, "wheelchair_stops": 14.9, "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_pct": 99.3, "mixed_case_stop_name_pct": 0.3, "pathways": { "has_entrances": false, "has_levels": false, "has_pathways": false, "has_stations": true, "has_step_free": false, "pathway_count": 0 }, "stops": 7057, "trips": 52401, "wheelchair_accessible_pct": 100.0, "wheelchair_boarding_pct": 59.8, "wheelchair_marked_accessible_pct": 59.8, "wheelchair_marked_not_accessible_pct": 0.0 }, "findings": [ { "code": "scorecard_wheelchair_boarding_unknown", "count": 2839, "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": 10.1, "severity": "WARNING", "what": "2839 of 7057 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", "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", "count": 7033, "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.9, "severity": "INFO", "what": "About 7033 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_missing_headsigns", "count": 383, "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": "383 of 52401 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": 52.4, "status": "measured", "summary": "60% of stops state wheelchair accessibility (60% 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": 9, "instances_by_severity": { "ERROR": 0, "INFO": 2, "WARNING": 13488 }, "validator_version": "8.0.1" }, "findings": [ { "code": "mixed_case_recommended_field", "count": 12334, "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": "stop_too_far_from_shape_using_user_distance", "count": 1126, "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": 8.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": "service_has_no_active_day_of_the_week", "count": 16, "effort": "A few minutes in your scheduling software.", "fix": "Delete the empty calendars or set their service days.", "owner": "Likely your export tool", "points": 6.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": "route_long_name_contains_short_name", "count": 4, "effort": "Varies.", "fix": "Review the rule documentation for 'route_long_name_contains_short_name' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 4.0, "severity": "WARNING", "what": "Route long name contains short name (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "stop_too_far_from_shape", "count": 4, "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": 4.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": "expired_calendar", "count": 2, "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": 4.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": "missing_recommended_file", "count": 1, "effort": "One small file, set once in export settings.", "fix": "Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date.", "owner": "Likely your export tool", "points": 4.0, "severity": "WARNING", "what": "A recommended GTFS file (usually feed_info.txt) is missing.", "why": "feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale." }, { "code": "stops_match_shape_out_of_order", "count": 1, "effort": "Varies.", "fix": "Review the rule documentation for 'stops_match_shape_out_of_order' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 4.0, "severity": "WARNING", "what": "Stops match shape out of order (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "unused_station", "count": 2, "effort": "Varies.", "fix": "Review the rule documentation for 'unused_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 0.5, "severity": "INFO", "what": "Unused station (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." } ], "name": "correctness", "score": 57.5, "status": "measured", "summary": "The MobilityData validator flagged 9 kinds of issue across 13490 instances (0 error, 13488 warning, 2 informational).", "weight": 0.35 }, "freshness": { "details": { "days_until_expiry": 43, "feed_end_date": null, "feed_start_date": null, "feed_version": null, "has_feed_info": false, "last_service_date": "2026-08-21", "seasonal_boundary": false, "service_type": "fixed" }, "findings": [ { "code": "scorecard_missing_feed_info_dates", "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 (the file itself is absent)", "why": "Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates." } ], "name": "freshness", "score": 56.7, "status": "measured", "summary": "Service data covers the next 43 days.", "weight": 0.2 }, "realtime": { "details": { "coverage_pct": 47.5, "covered_trips": 114, "drift": { "median_seconds": 0, "observations": 13491, "on_time_share_pct": 66.1, "p90_abs_seconds": 391 }, "kinds_reachable": 2, "rt_freshness": "fresh", "samples": 6, "scheduled_trips_in_window": 240, "vehicles_checked": 405, "vehicles_on_route_pct": 98.5, "worst_lag_seconds": 18 }, "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": 126, "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": 18.4, "severity": "WARNING", "what": "126 of 240 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": 73.1, "status": "measured", "summary": "Sampled 6 times: 2 of 3 feeds healthy; 47.5% of scheduled trips had live predictions; 98.5% of vehicles on their route; predictions ran a median of 0s 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 55 days.", "key": "current", "met": true }, { "detail": "States wheelchair access on 60% of stops and 100% 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 60% of stops and 100% 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": "9f6554cafaa7903fe39ec60aaed448a0d1574c3d8c67fcc3917c40cd7afb6fce", "size_bytes": 20909973, "static_url": "https://www.itsmarta.com/google_transit_feed/google_transit.zip" }, "generated_at": "2026-06-27T00:00:00+00:00", "geo": { "bbox": [ -84.6698, 33.43237, -84.0834, 34.10557 ], "lat": 33.74699, "lon": -84.36327, "stop_count": 7057 }, "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": [ "MARTA" ], "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 55 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": "F", "margin_to_lower_band": 59.2, "margin_to_next_band": 0.8, "score": 59.2 }, "recommendations": [ { "code": "scorecard_route_color_low_contrast", "count": 25, "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": "25 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 2, 5, 15, 20, 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": 6790, "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": "6790 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"HOWELL MILL RD @ KIPLING DR\", \"N MAIN ST @ WINTHROPE PARK DR\", \"N MAIN ST @ 379\", 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": 7013, "findings": [], "orphan_stops": 0, "single_stop_trips": 0, "trips_total": 52401 }, "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_rt_trip_coverage", "count": 126, "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": 18.4, "rank": 2, "severity": "WARNING", "what": "126 of 240 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." }, { "code": "scorecard_no_fare_data", "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" }