{ "agency": { "id": "maryland-transit-administration-469", "name": "Light Rail" }, "autofix": { "available": false }, "categories": { "completeness": { "details": { "accessibility": { "measures": "presence_not_usability", "score": 74.0, "stops_marked_accessible_pct": 58.4, "stops_marked_not_accessible_pct": 0.0, "stops_stated_pct": 58.4, "trips_stated_pct": 100.0 }, "accessibility_measures": "presence_not_usability", "cemv": { "declared": false, "supported": false }, "components": { "contact": 7.5, "fares": 15.0, "headsigns": 15.0, "stop_names": 15.0, "wheelchair_stops": 14.6, "wheelchair_trips": 15.0 }, "fare_free": false, "fares": { "applied": true, "has_leg_rules": true, "has_products": true, "has_transfer_rules": true, "model": "v2", "product_count": 11 }, "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": 100.0, "pathways": { "has_entrances": false, "has_levels": false, "has_pathways": false, "has_stations": true, "has_step_free": false, "pathway_count": 0 }, "stops": 161, "trips": 699, "wheelchair_accessible_pct": 100.0, "wheelchair_boarding_pct": 58.4, "wheelchair_marked_accessible_pct": 58.4, "wheelchair_marked_not_accessible_pct": 0.0 }, "findings": [ { "code": "scorecard_wheelchair_boarding_unknown", "count": 67, "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.4, "severity": "WARNING", "what": "67 of 161 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_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": 82.1, "status": "measured", "summary": "58% of stops state wheelchair accessibility (58% 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": 10, "instances_by_severity": { "ERROR": 0, "INFO": 6, "WARNING": 1028 }, "validator_version": "8.0.1" }, "findings": [ { "code": "mixed_case_recommended_field", "count": 700, "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": 165, "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": "trip_distance_exceeds_shape_distance_below_threshold", "count": 100, "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": 60, "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": "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 file GTFS asks for (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": "route_short_name_too_long", "count": 1, "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": 4.0, "severity": "WARNING", "what": "Route short name too long (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "stop_too_far_from_shape", "count": 1, "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": "unknown_column", "count": 3, "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.5, "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": "unknown_file", "count": 2, "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." }, { "code": "unused_station", "count": 1, "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": 54.5, "status": "measured", "summary": "The MobilityData validator flagged 10 kinds of issue across 1034 instances (0 error, 1028 warning, 6 informational).", "weight": 0.35 }, "freshness": { "details": { "days_until_expiry": 175, "feed_end_date": null, "feed_start_date": null, "feed_version": null, "has_feed_info": false, "last_service_date": "2026-12-31", "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": 85.0, "status": "measured", "summary": "Service data covers the next 175 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 } }, "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 agency's own URL." ], "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 175 days.", "key": "current", "met": true }, { "detail": "States wheelchair access on 58% 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 58% 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": "5b02678ddfa192539ea09344b06b7e029f441d0df9b59e94e7da8fb554325884", "size_bytes": 834022, "static_url": "https://mdotmta-gtfs.s3.amazonaws.com/mdotmta_gtfs_lightrail.zip" }, "fetch": { "final_url": "https://mdotmta-gtfs.s3.amazonaws.com/mdotmta_gtfs_lightrail.zip", "max_attempts": 4, "source": "origin", "user_agent": "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/125.0.0.0 Safari/537.36" }, "generated_at": "2026-07-09T00:00:00+00:00", "geo": { "bbox": [ -76.67371, 39.17169, -76.61609, 39.4964 ], "lat": 39.29688, "lon": -76.63493, "stop_count": 161 }, "ntd_id_alignment": { "detail": "Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.", "feed_agency_ids": [ "30034" ], "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 175 days.", "key": "current", "status": "ready" } ], "status": "ready", "summary": "Published at a public URL, valid, and current: the three things the NTD GTFS requirement asks of a feed all hold here. Only your own D-10 certification makes that official; this is a heads-up, not a determination." }, "overall": { "grade": "C", "margin_to_lower_band": 0.7, "margin_to_next_band": 9.3, "score": 70.7 }, "recommendations": [ { "category": "fares", "code": "scorecard_fares_v2_no_fare_media", "count": 0, "effort": "A short file; one row per payment method you accept.", "fix": "Add fare_media.txt listing your accepted payment methods, including contactless EMV if riders can tap to pay.", "owner": "", "points": 0.0, "severity": "INFO", "what": "The feed publishes fare products but no fare_media.txt declaring how riders can pay.", "why": "Riders can't tell from the feed which payment methods you accept, such as a transit card, a mobile app, or tap-to-pay with a contactless bank card." }, { "category": "accessibility", "code": "scorecard_route_color_low_contrast", "count": 1, "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": "1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (LIGHT RAILLINK).", "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." }, { "category": "accessibility", "code": "scorecard_stop_name_needs_tts", "count": 14, "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": "14 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"Camden Station / Camden Yards (Northbound)\", \"Cultural Center / State Center (Northbound)\", \"Mt. Royal / MICA (Northbound)\", 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." }, { "category": "accessibility", "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." } ], "routability": { "boardable_stops": 127, "findings": [ { "code": "scorecard_orphan_stops", "count": 60, "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": "60 of 127 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": 60, "single_stop_trips": 0, "trips_total": 699 }, "route_map": { "drawn_route_count": 1, "has_shapes": true, "path": "data/artifacts/maryland-transit-administration-469/geometry.geojson", "route_count": 1, "routes": [ { "color": "007499", "color_name": "teal", "has_shape": true, "id": "11693", "label": "LIGHT RAILLINK", "long": "BWI Airport / Glen Burnie - Hunt Valley", "short": "LIGHT RAILLINK", "text_color": "000000", "type_label": "Tram / light rail" } ], "stop_count": 161, "stop_points_capped": false }, "rubric_version": "1.1", "schema_version": "1.7", "shapes_readiness": { "detail": "All 699 trips have a shape in shapes.txt.", "status": "ready", "total_trips": 699, "trips_with_shape": 699 }, "snapshot_date": "2026-07-09", "top_fixes": [ { "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, "rank": 1, "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." }, { "code": "scorecard_wheelchair_boarding_unknown", "count": 67, "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.4, "rank": 2, "severity": "WARNING", "what": "67 of 161 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": "mixed_case_recommended_field", "count": 700, "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, "rank": 3, "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." } ], "validator_version": "8.0.1" }