{
  "agency": {
    "country": "PT",
    "id": "metro-sul-do-tejo",
    "name": "Metro Sul do Tejo",
    "operating_note": "The official National Access Point still designates the dated archive as the current MTS feed, and its service calendar passed the 60-day gate.",
    "subdivision_code": "PT-15",
    "subdivision_name": "Set\u00fabal"
  },
  "categories": {
    "completeness": {
      "details": {
        "accessibility": {
          "measures": "presence_not_usability",
          "score": 100.0,
          "stops_marked_accessible_pct": 100.0,
          "stops_marked_not_accessible_pct": 0.0,
          "stops_stated_pct": 100.0,
          "trips_stated_pct": 100.0
        },
        "accessibility_measures": "presence_not_usability",
        "cemv": {
          "declared": false,
          "supported": false
        },
        "components": {
          "contact": 15.0,
          "fares": 0.0,
          "headsigns": 15.0,
          "stop_names": 15.0,
          "wheelchair_stops": 25.0,
          "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": 100.0,
        "mixed_case_stop_name_pct": 100.0,
        "pathways": {
          "has_entrances": false,
          "has_levels": false,
          "has_pathways": false,
          "has_stations": false,
          "has_step_free": false,
          "pathway_count": 0
        },
        "stops": 19,
        "translations": {
          "feed_lang": "pt",
          "has_translations": false,
          "languages": [],
          "translated_tables": [],
          "translation_count": 0
        },
        "trips": 2067,
        "wheelchair_accessible_pct": 100.0,
        "wheelchair_boarding_pct": 100.0,
        "wheelchair_marked_accessible_pct": 100.0,
        "wheelchair_marked_not_accessible_pct": 0.0
      },
      "findings": [
        {
          "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."
        }
      ],
      "name": "completeness",
      "score": 85.0,
      "status": "measured",
      "summary": "100% of stops state wheelchair accessibility (100% 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": 8,
        "instances_by_severity": {
          "ERROR": 0,
          "INFO": 62,
          "WARNING": 8
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "stops_match_shape_out_of_order",
          "count": 4,
          "effort": "A few minutes per flagged trip.",
          "fix": "Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards.",
          "owner": "Likely your export tool",
          "points": 4.0,
          "severity": "WARNING",
          "what": "On some trips the stops fall along the route line in a different order than the schedule lists.",
          "why": "Trip planners can draw the transit vehicle doubling back or skipping ahead, which confuses riders reading the map."
        },
        {
          "code": "expired_calendar",
          "count": 3,
          "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 ended.",
          "why": "Expired calendars are dead weight and can hide real schedule problems from your staff and vendors."
        },
        {
          "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": "big_gap_in_service",
          "count": 46,
          "effort": "A review of your calendar dates.",
          "fix": "Check whether the gap is real, like a seasonal break; if not, add the missing dates to the calendar.",
          "owner": "",
          "points": 0.8,
          "severity": "INFO",
          "what": "The feed has a stretch of two weeks or more with no service running.",
          "why": "A long gap can mean dates were left out of the calendar. Apps then show no trips on those days."
        },
        {
          "code": "unknown_column",
          "count": 13,
          "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.8,
          "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": "service_extends_far_in_the_future",
          "count": 1,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'service_extends_far_in_the_future' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 0.5,
          "severity": "INFO",
          "what": "Service extends far in the future (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "service_window_outside_feed_period",
          "count": 1,
          "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_file",
          "count": 1,
          "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": 85.0,
      "status": "measured",
      "summary": "The MobilityData validator flagged 8 kinds of issue across 70 instances (0 error, 8 warning, 62 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": 1257,
        "effective_expiry_date": "2030-01-01",
        "feed_end_date": "2030-01-01",
        "feed_start_date": "2024-01-01",
        "feed_version": "1.0",
        "has_feed_info": true,
        "last_service_date": "2030-12-25",
        "seasonal_boundary": true,
        "service_horizon_review_years": 10,
        "service_horizon_status": "within_review_threshold",
        "service_type": "fixed"
      },
      "findings": [],
      "name": "freshness",
      "score": 100.0,
      "status": "measured",
      "summary": "Service data covers the next 1257 days.",
      "weight": 0.2
    },
    "realtime": {
      "name": "realtime",
      "status": "not_yet_measured",
      "summary": "Not scored 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": true,
    "criteria": [
      {
        "detail": "Passes validation with no errors.",
        "key": "valid",
        "met": true
      },
      {
        "detail": "Service data covers the next 1257 days.",
        "key": "current",
        "met": true
      },
      {
        "detail": "States wheelchair access on 100% of stops and 100% of trips.",
        "key": "accessible",
        "met": true
      }
    ],
    "status": "awarded",
    "summary": "This feed earns the conformance mark: valid, current, and stating wheelchair access on nearly every stop and trip."
  },
  "feed": {
    "license_note": "CC BY 4.0 through Portugal's National Access Point; credit Metro Transportes do Sul.",
    "reachable": true,
    "sha256": "6ed4f97ba6fa95721cd29c86af974ff9768a6a079f32c60c890fe757c0b13286",
    "size_bytes": 252508,
    "static_url": "https://mts.pt/imt/MTS-20240129.zip"
  },
  "fetch": {
    "final_url": "https://mts.pt/imt/MTS-20240129.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-07-24T00:00:00+00:00",
  "geo": {
    "bbox": [
      -9.20717,
      38.63712,
      -9.14738,
      38.68755
    ],
    "lat": 38.66553,
    "lon": -9.16001,
    "stop_count": 19
  },
  "mode_profile": {
    "ferry_only": false,
    "graded": false,
    "has_ferry": false,
    "is_multimodal": false,
    "measured": true,
    "modes": [
      {
        "key": "tram",
        "label": "Tram / light rail",
        "route_count": 3,
        "trip_count": 2067,
        "trip_share_pct": 100.0
      }
    ],
    "primary_mode": "tram",
    "primary_mode_label": "Tram / light rail",
    "route_count": 3,
    "trip_count": 2067
  },
  "overall": {
    "grade": "B",
    "margin_to_lower_band": 8.8,
    "margin_to_next_band": 1.2,
    "score": 88.8
  },
  "recommendations": [
    {
      "category": "accessibility",
      "code": "scorecard_route_color_low_contrast",
      "count": 2,
      "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": "2 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (1, 3).",
      "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."
    }
  ],
  "routability": {
    "boardable_stops": 19,
    "findings": [],
    "orphan_stops": 0,
    "single_stop_trips": 0,
    "trips_total": 2067
  },
  "route_map": {
    "drawn_route_count": 3,
    "has_shapes": true,
    "path": "data/artifacts/metro-sul-do-tejo/geometry.geojson",
    "route_count": 3,
    "routes": [
      {
        "color": "00A3E8",
        "color_name": "teal",
        "has_shape": true,
        "id": "1_0",
        "label": "1",
        "long": "Corroios - Cacilhas",
        "short": "1",
        "text_color": "FFFFFF",
        "type_label": "Tram / light rail"
      },
      {
        "color": "FBCD01",
        "color_name": "yellow",
        "has_shape": true,
        "id": "2_0",
        "label": "2",
        "long": "Corroios - Pragal",
        "short": "2",
        "text_color": "000000",
        "type_label": "Tram / light rail"
      },
      {
        "color": "BBCF16",
        "color_name": "yellow",
        "has_shape": true,
        "id": "3_0",
        "label": "3",
        "long": "Cacilhas - Universidade",
        "short": "3",
        "text_color": "FFFFFF",
        "type_label": "Tram / light rail"
      }
    ],
    "stop_count": 19,
    "stop_points_capped": false
  },
  "rubric_version": "1.2",
  "schema_version": "1.16",
  "scoring_profile": {
    "id": "gtfs-scorecard-1.2",
    "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.2"
  },
  "snapshot_date": "2026-07-24",
  "top_fixes": [
    {
      "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": 1,
      "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": "stops_match_shape_out_of_order",
      "count": 4,
      "effort": "A few minutes per flagged trip.",
      "fix": "Check the stop order and the shape direction in your scheduling software; the shape is often drawn backwards.",
      "owner": "Likely your export tool",
      "points": 4.0,
      "rank": 2,
      "severity": "WARNING",
      "what": "On some trips the stops fall along the route line in a different order than the schedule lists.",
      "why": "Trip planners can draw the transit vehicle doubling back or skipping ahead, which confuses riders reading the map."
    },
    {
      "code": "expired_calendar",
      "count": 3,
      "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,
      "rank": 3,
      "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."
    }
  ],
  "validator_version": "8.0.1"
}