{
  "agency": {
    "id": "maryland-transit-administration-metro-subway",
    "name": "Metro SubwayLink",
    "subdivision_code": "US-MD",
    "subdivision_name": "Maryland"
  },
  "categories": {
    "completeness": {
      "details": {
        "accessibility": {
          "measures": "presence_not_usability",
          "score": 62.9,
          "stops_marked_accessible_pct": 40.6,
          "stops_marked_not_accessible_pct": 0.0,
          "stops_stated_pct": 40.6,
          "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": 13.9,
          "wheelchair_stops": 10.1,
          "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_applicable_trips": 399,
        "headsign_loop_exempt_trips": 0,
        "headsign_pct": 100.0,
        "headsign_scored_pct": 100.0,
        "mixed_case_stop_name_pct": 92.5,
        "pathways": {
          "has_entrances": true,
          "has_levels": true,
          "has_pathways": true,
          "has_stations": true,
          "has_step_free": true,
          "pathway_count": 319
        },
        "stops": 239,
        "translations": {
          "feed_lang": null,
          "has_translations": false,
          "languages": [],
          "translated_tables": [],
          "translation_count": 0
        },
        "trips": 399,
        "wheelchair_accessible_pct": 100.0,
        "wheelchair_boarding_pct": 40.6,
        "wheelchair_marked_accessible_pct": 40.6,
        "wheelchair_marked_not_accessible_pct": 0.0
      },
      "findings": [
        {
          "code": "scorecard_wheelchair_boarding_unknown",
          "count": 142,
          "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": 14.9,
          "severity": "WARNING",
          "what": "142 of 239 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_stop_names_all_caps",
          "count": 18,
          "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": 1.1,
          "severity": "INFO",
          "what": "About 18 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": 319,
          "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": 76.5,
      "status": "measured",
      "summary": "41% of stops state wheelchair accessibility (41% 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": 7,
        "instances_by_severity": {
          "ERROR": 0,
          "INFO": 4,
          "WARNING": 683
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "mixed_case_recommended_field",
          "count": 573,
          "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": "equal_shape_distance_same_coordinates",
          "count": 73,
          "effort": "Usually one export setting.",
          "fix": "Turn on shape cleanup in your export tool, or drop the repeated points from shapes.txt.",
          "owner": "Likely your export tool",
          "points": 8.0,
          "severity": "WARNING",
          "what": "Some route lines list the same point twice in a row.",
          "why": "Repeated points don't hurt riders, but they can skew distance math and hint at a shaky export."
        },
        {
          "code": "stop_too_far_from_shape_using_user_distance",
          "count": 35,
          "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": 6.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": "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": "unknown_column",
          "count": 2,
          "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": "A quick look at the flagged file.",
          "fix": "Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra.",
          "owner": "",
          "points": 0.5,
          "severity": "INFO",
          "what": "The feed includes a file that is not part of the GTFS spec.",
          "why": "Apps ignore files they don't know, and a stray file can hide a misspelled standard file name."
        }
      ],
      "name": "correctness",
      "score": 69.0,
      "status": "measured",
      "summary": "The MobilityData validator flagged 7 kinds of issue across 687 instances (0 error, 683 warning, 4 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": 130,
        "effective_expiry_date": "2026-12-31",
        "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_horizon_review_years": 10,
        "service_horizon_status": "within_review_threshold",
        "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 130 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 configured feed URL. Publisher ownership of that URL is not verified."
    ],
    "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 130 days.",
        "key": "current",
        "met": true
      },
      {
        "detail": "States wheelchair access on 41% of stops and 100% of trips; the mark needs 90% of each.",
        "key": "accessible",
        "met": false
      }
    ],
    "status": "not_yet",
    "summary": "One requirement remains for this feed to earn the conformance mark. States wheelchair access on 41% of stops and 100% of trips; the mark needs 90% of each.",
    "version": 2
  },
  "feed": {
    "license_note": "No stated data license in the Mobility Database; verify before publishing.",
    "reachable": true,
    "sha256": "7d536b02798b35bcd36c64f6faacb11f042e1dee520237f9cb3f7d75ac4e881b",
    "size_bytes": 56280,
    "source_provenance": "unverified",
    "static_url": "https://mdotmta-gtfs.s3.amazonaws.com/mdotmta_gtfs_metro.zip"
  },
  "fetch": {
    "final_url": "https://mdotmta-gtfs.s3.amazonaws.com/mdotmta_gtfs_metro.zip",
    "max_attempts": 4,
    "reader_archive_profile": "raw-v1",
    "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-08-10T00:00:00+00:00",
  "geo": {
    "bbox": [
      -76.78068,
      39.28934,
      -76.59413,
      39.40815
    ],
    "lat": 39.30414,
    "lon": -76.63551,
    "stop_count": 239
  },
  "mode_profile": {
    "ferry_only": false,
    "graded": false,
    "has_ferry": false,
    "is_multimodal": false,
    "measured": true,
    "modes": [
      {
        "key": "subway",
        "label": "Subway / metro",
        "route_count": 1,
        "trip_count": 399,
        "trip_share_pct": 100.0
      }
    ],
    "primary_mode": "subway",
    "primary_mode_label": "Subway / metro",
    "route_count": 1,
    "trip_count": 399
  },
  "ntd_id_alignment": {
    "detail": "This feed provides agency_id. For RY2026, keep one stable value for each NTD reporter represented in the feed and crosswalk it on the P-50 form. The value does not need to equal the five-digit NTD ID; we do not have that ID on file, so the optional equality comparison 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 143 days.",
        "key": "current",
        "status": "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": "ready",
    "summary": "Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination."
  },
  "overall": {
    "grade": "C",
    "margin_to_lower_band": 5.3,
    "margin_to_next_band": 4.7,
    "score": 75.3
  },
  "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_stop_name_needs_tts",
      "count": 15,
      "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": "15 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"ROGERS AVE STATION (METRO) nb\", \"ROGERS AVE STATION (METRO) sb\", \"ROGERS AVE METRO\", 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-08-23",
    "feed_fetched_date": "2026-08-22",
    "kind": "freshness"
  },
  "routability": {
    "boardable_stops": 26,
    "findings": [],
    "orphan_stops": 0,
    "single_stop_trips": 0,
    "trips_total": 399
  },
  "route_map": {
    "drawn_route_count": 1,
    "has_shapes": true,
    "path": "data/artifacts/maryland-transit-administration-metro-subway/geometry.geojson",
    "route_count": 1,
    "routes": [
      {
        "color": "008000",
        "color_name": "green",
        "has_shape": true,
        "id": "11682",
        "label": "METRO SUBWAYLINK",
        "long": "Owings Mills - Johns Hopkins",
        "short": "METRO SUBWAYLINK",
        "text_color": "FFFFFF",
        "type_label": "Subway / metro"
      }
    ],
    "stop_count": 239,
    "stop_points_capped": false
  },
  "rubric_version": "1.3",
  "schema_version": "1.18",
  "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 399 trips have a shape in shapes.txt.",
    "status": "ready",
    "total_trips": 399,
    "trips_with_shape": 399
  },
  "snapshot_date": "2026-08-23",
  "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": 142,
      "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": 14.9,
      "rank": 2,
      "severity": "WARNING",
      "what": "142 of 239 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": 573,
      "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"
}
