{ "agency": { "id": "washington-metropolitan-area-transit-authority-wmata-1847", "name": "Washington Metropolitan Area Transit Authority (WMATA) Rail", "subdivision_code": "US-DC", "subdivision_name": "District of Columbia" }, "categories": { "completeness": { "details": { "accessibility": { "measures": "presence_not_usability", "score": 62.5, "stops_marked_accessible_pct": 94.4, "stops_marked_not_accessible_pct": 5.6, "stops_stated_pct": 100.0, "trips_stated_pct": 0.0 }, "accessibility_measures": "presence_not_usability", "cemv": { "declared": false, "supported": false }, "components": { "contact": 7.5, "fares": 0.0, "headsigns": 15.0, "stop_names": 0.2, "wheelchair_stops": 25.0, "wheelchair_trips": 0.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": 9955, "headsign_loop_exempt_trips": 0, "headsign_pct": 100.0, "headsign_scored_pct": 100.0, "mixed_case_stop_name_pct": 1.2, "pathways": { "has_entrances": true, "has_levels": true, "has_pathways": true, "has_stations": true, "has_step_free": true, "pathway_count": 2738 }, "stops": 2050, "translations": { "feed_lang": "en", "has_translations": false, "languages": [], "translated_tables": [], "translation_count": 0 }, "trips": 9955, "wheelchair_accessible_pct": 0.0, "wheelchair_boarding_pct": 100.0, "wheelchair_marked_accessible_pct": 94.4, "wheelchair_marked_not_accessible_pct": 5.6 }, "findings": [ { "code": "scorecard_wheelchair_accessible_unknown", "count": 9955, "effort": "A default or per-trip field in your export.", "fix": "Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.", "owner": "Likely your export tool", "points": 15.0, "severity": "WARNING", "what": "9955 of 9955 trips don't say whether the vehicle is wheelchair accessible.", "why": "Even with accessible stops, riders need to know the transit vehicle itself can take them." }, { "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": 2026, "effort": "Often a bulk fix in your scheduling software.", "fix": "Rename stops to mixed case where the language has letter case (for example, 'Central Station').", "owner": "Likely your export tool", "points": 14.8, "severity": "INFO", "what": "About 2026 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": "Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger." }, { "code": "scorecard_station_pathways", "count": 2738, "effort": "None.", "fix": "No action needed.", "owner": "", "points": 0.0, "severity": "INFO", "what": "This feed describes station pathways, including step-free (elevator) routes.", "why": "Riders can be routed through the station, and wheelchair users can see whether a step-free route exists." } ], "name": "completeness", "score": 47.7, "status": "measured", "summary": "100% of stops state wheelchair accessibility (94% marked accessible, 6% 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": 13, "instances_by_severity": { "ERROR": 5, "INFO": 8, "WARNING": 8028 }, "validator_version": "8.0.1" }, "findings": [ { "code": "number_out_of_range", "count": 4, "effort": "Varies.", "fix": "Review the rule documentation for 'number_out_of_range' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 12.0, "severity": "ERROR", "what": "Number out of range (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "bidirectional_exit_gate", "count": 1, "effort": "Varies.", "fix": "Review the rule documentation for 'bidirectional_exit_gate' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 12.0, "severity": "ERROR", "what": "Bidirectional exit gate (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "mixed_case_recommended_field", "count": 6667, "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": 1322, "effort": "Usually an export-tool fix, not hand editing.", "fix": "Check the flagged stops' shape_dist_traveled against the route shape, and re-generate it on export if they disagree.", "owner": "Likely your export tool", "points": 8.0, "severity": "WARNING", "what": "Some stops sit far from the route line, going by the feed's own distance values.", "why": "Trip planners may draw the route down the wrong path or point riders to the wrong boarding location." }, { "code": "stop_too_far_from_shape", "count": 21, "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 transit vehicle route through the wrong path or point riders to the wrong boarding location." }, { "code": "expired_calendar", "count": 9, "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": 6.0, "severity": "WARNING", "what": "Some service calendars in the feed have already ended.", "why": "Expired calendars are dead weight and can hide real schedule problems from your staff and vendors." }, { "code": "same_name_and_description_for_stop", "count": 5, "effort": "Varies.", "fix": "Review the rule documentation for 'same_name_and_description_for_stop' 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 stop (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "feed_expiration_date7_days", "count": 1, "effort": "Usually a re-export from your scheduling software.", "fix": "Export and publish an updated GTFS feed that covers at least the next 30 days of service.", "owner": "Likely your export tool", "points": 4.0, "severity": "WARNING", "what": "This feed's service calendar runs out within the next 7 days.", "why": "When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all." }, { "code": "missing_feed_contact_email_and_url", "count": 1, "effort": "One field, set once in export settings.", "fix": "Add feed_contact_email or feed_contact_url to feed_info.txt.", "owner": "Likely your export tool", "points": 4.0, "severity": "WARNING", "what": "feed_info.txt lists no contact email and no contact URL.", "why": "Without a contact, apps like Google Maps can't reach you when they find a problem in the feed." }, { "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 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": "trip_coverage_not_active_for_next7_days", "count": 1, "effort": "One setting in most export tools.", "fix": "Trim past service periods the next time you export.", "owner": "Likely your export tool", "points": 4.0, "severity": "WARNING", "what": "Many of the feed's trips don't run at all in the next 7 days.", "why": "It usually means old service periods are still in the export, making the feed bigger and harder to check." }, { "code": "service_window_outside_feed_period", "count": 5, "effort": "Two fields in feed_info.txt, or one export setting.", "fix": "Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside.", "owner": "Likely your export tool", "points": 0.5, "severity": "INFO", "what": "Some service dates fall outside the date window set in feed_info.txt.", "why": "feed_info.txt should span every day your service runs, so apps know when the data applies." }, { "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." } ], "name": "correctness", "score": 27.0, "status": "measured", "summary": "The MobilityData validator flagged 13 kinds of issue across 8041 instances (5 error, 8028 warning, 8 informational).", "weight": 0.35 }, "freshness": { "details": { "days_until_expiry": -659, "effective_expiry_date": "2024-10-11", "feed_end_date": "2024-10-11", "feed_start_date": "2024-10-01", "feed_version": null, "has_feed_info": true, "last_service_date": "2024-12-14", "seasonal_boundary": false, "service_horizon_review_years": 10, "service_horizon_status": "within_review_threshold", "service_type": "fixed" }, "findings": [ { "code": "scorecard_feed_expired", "count": 1, "effort": "Usually one export setting; export on a schedule so it never lapses again.", "fix": "Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.", "owner": "Likely your export tool", "points": 100.0, "severity": "ERROR", "what": "Service data ended 659 day(s) ago.", "why": "When the calendar runs out, trip planners stop showing this agency even though the transit vehicles are still running. Riders are told the service does not exist." } ], "name": "freshness", "score": 0.0, "status": "measured", "summary": "Service data ended 659 day(s) ago. Trip planners have likely already dropped this feed.", "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": "mirror", "level": "provisional", "measured_categories": 3, "notes": [ "Realtime quality was not measured this run. It does not count against the grade.", "The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead." ], "rt_windows": 0, "total_categories": 4 }, "conformance": { "awarded": false, "criteria": [ { "detail": "2 validator errors to resolve.", "key": "valid", "met": false }, { "detail": "Service data expired 659 days ago.", "key": "current", "met": false }, { "detail": "States wheelchair access on 100% 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. 2 validator errors to resolve. Service data expired 659 days ago. States wheelchair access on 100% of stops and 0% of trips; the mark needs 90% of each." }, "feed": { "license_note": "License: https://developer.wmata.com/license", "reachable": true, "sha256": "9f61fb198761766a7f59996fd913723f6ef5684b320a2d97702d84e9e2db3e69", "size_bytes": 2273712, "static_url": "https://api.wmata.com/gtfs/rail-gtfs-static.zip" }, "fetch": { "final_url": "https://storage.googleapis.com/storage/v1/b/mdb-latest/o/us-district-of-columbia-washington-wmata-gtfs-1847.zip?alt=media", "max_attempts": 1, "origin_error": "HTTPError", "reader_archive_profile": "raw-v1", "source": "mirror", "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-08-01T00:00:00+00:00", "geo": { "bbox": [ -77.49194, 38.7662, -76.8442, 39.12042 ], "lat": 38.89849, "lon": -77.03273, "stop_count": 2050 }, "mode_profile": { "ferry_only": false, "graded": false, "has_ferry": false, "is_multimodal": false, "measured": true, "modes": [ { "key": "subway", "label": "Subway / metro", "route_count": 6, "trip_count": 9955, "trip_share_pct": 100.0 } ], "primary_mode": "subway", "primary_mode_label": "Subway / metro", "route_count": 6, "trip_count": 9955 }, "ntd_id_alignment": { "detail": "Your feed's agency_id is 1; your National Transit Database ID is 30030. A feed that serves several agencies (a shared regional feed) can legitimately carry more than one agency_id. The values do not need to equal the five-digit NTD ID, so this difference is allowed and carries no score.", "feed_agency_ids": [ "1" ], "fix": "Confirm that P-50 crosswalks agency_id 1 to NTD ID 30030, and keep the feed value stable. Do not change it solely to make the two values equal.", "ntd_id": "30030", "status": "mismatch" }, "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 expired 659 days ago, so FTA would find the link out of date.", "key": "current", "status": "not_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": "not_ready", "summary": "Resolve this before you certify on the D-10. 2 validator errors to resolve. Service data expired 659 days ago, so FTA would find the link out of date." }, "overall": { "grade": "F", "margin_to_lower_band": 26.7, "margin_to_next_band": 33.3, "score": 26.7 }, "recommendations": [ { "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 (Green).", "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": 418, "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": "418 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"VAN DORN ST METRORAIL STATION\", \"MORGAN BLVD METRORAIL STATION\", \"ADDISON RD METRORAIL STATION\", 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." } ], "routability": { "boardable_stops": 125, "findings": [], "orphan_stops": 0, "single_stop_trips": 0, "trips_total": 9955 }, "route_map": { "drawn_route_count": 6, "has_shapes": true, "path": "data/artifacts/washington-metropolitan-area-transit-authority-wmata-1847/geometry.geojson", "route_count": 6, "routes": [ { "color": "0076C0", "color_name": "teal", "has_shape": true, "id": "BLUE", "label": "Blue", "long": "Metrorail Blue Line", "short": "Blue", "text_color": "FFFFFF", "type_label": "Subway / metro" }, { "color": "00A94F", "color_name": "green", "has_shape": true, "id": "GREEN", "label": "Green", "long": "Metrorail Green Line", "short": "Green", "text_color": "FFFFFF", "type_label": "Subway / metro" }, { "color": "F7941E", "color_name": "orange", "has_shape": true, "id": "ORANGE", "label": "Orange", "long": "Metrorail Orange Line", "short": "Orange", "text_color": "000000", "type_label": "Subway / metro" }, { "color": "E31837", "color_name": "red", "has_shape": true, "id": "RED", "label": "Red", "long": "Metrorail Red Line", "short": "Red", "text_color": "FFFFFF", "type_label": "Subway / metro" }, { "color": "A1A2A1", "color_name": "gray", "has_shape": true, "id": "SILVER", "label": "Silver", "long": "Metrorail Silver Line", "short": "Silver", "text_color": "000000", "type_label": "Subway / metro" }, { "color": "FFD200", "color_name": "yellow", "has_shape": true, "id": "YELLOW", "label": "Yellow", "long": "Metrorail Yellow Line", "short": "Yellow", "text_color": "000000", "type_label": "Subway / metro" } ], "stop_count": 2050, "stop_points_capped": true }, "rubric_version": "1.3", "schema_version": "1.17", "scoring_profile": { "id": "gtfs-scorecard-1.3", "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.3" }, "shapes_readiness": { "detail": "All 9955 trips have a shape in shapes.txt.", "status": "ready", "total_trips": 9955, "trips_with_shape": 9955 }, "snapshot_date": "2026-08-01", "top_fixes": [ { "code": "scorecard_feed_expired", "count": 1, "effort": "Usually one export setting; export on a schedule so it never lapses again.", "fix": "Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.", "owner": "Likely your export tool", "points": 100.0, "rank": 1, "severity": "ERROR", "what": "Service data ended 659 day(s) ago.", "why": "When the calendar runs out, trip planners stop showing this agency even though the transit vehicles are still running. Riders are told the service does not exist." }, { "code": "number_out_of_range", "count": 4, "effort": "Varies.", "fix": "Review the rule documentation for 'number_out_of_range' 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": "Number out of range (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "bidirectional_exit_gate", "count": 1, "effort": "Varies.", "fix": "Review the rule documentation for 'bidirectional_exit_gate' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 12.0, "rank": 3, "severity": "ERROR", "what": "Bidirectional exit gate (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." } ], "validator_version": "8.0.1" }