{
  "agency": {
    "country": "FR",
    "id": "fr-pan-8487",
    "name": "R\u00e9seau urbain TUM (Mende)",
    "subdivision_code": "FR-OCC",
    "subdivision_name": "Occitanie"
  },
  "categories": {
    "completeness": {
      "details": {
        "accessibility": {
          "measures": "presence_not_usability",
          "score": 0.0,
          "stops_marked_accessible_pct": 0.0,
          "stops_marked_not_accessible_pct": 0.0,
          "stops_stated_pct": 0.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": 15.0,
          "wheelchair_stops": 0.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": 266,
        "headsign_loop_exempt_trips": 0,
        "headsign_pct": 100.0,
        "headsign_scored_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": 123,
        "translations": {
          "feed_lang": "FR",
          "has_translations": false,
          "languages": [],
          "translated_tables": [],
          "translation_count": 0
        },
        "trips": 266,
        "unmeasured_components": [],
        "wheelchair_accessible_pct": 0.0,
        "wheelchair_boarding_pct": 0.0,
        "wheelchair_marked_accessible_pct": 0.0,
        "wheelchair_marked_not_accessible_pct": 0.0
      },
      "findings": [
        {
          "code": "scorecard_wheelchair_boarding_unknown",
          "count": 123,
          "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": 25.0,
          "severity": "WARNING",
          "what": "123 of 123 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_wheelchair_accessible_unknown",
          "count": 266,
          "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": "266 of 266 trips don't say whether the vehicle is wheelchair accessible.",
          "why": "Even with accessible stops, riders need to know the bus 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_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. Small errors then sit in the feed for months."
        },
        {
          "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 to link entrances, platforms, and elevators. Give each one a level.",
          "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": 37.5,
      "status": "measured",
      "summary": "0% of stops state wheelchair accessibility (0% 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": 20,
          "WARNING": 6907
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "missing_timepoint_value",
          "count": 3865,
          "effort": "Usually one export setting.",
          "fix": "Set timepoint=1 on stops that are real time checks and 0 on the rest. If every published time is a scheduled one, mark them all 1.",
          "owner": "Likely your export tool",
          "points": 8.0,
          "severity": "WARNING",
          "what": "Some rows in stop_times.txt leave the timepoint column blank.",
          "why": "That column says whether a time is a real checkpoint or an estimate. Blank leaves apps guessing, and they may show your estimates as promises."
        },
        {
          "code": "equal_shape_distance_diff_coordinates_distance_below_threshold",
          "count": 3032,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'equal_shape_distance_diff_coordinates_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": "Equal shape distance diff coordinates distance below threshold (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "equal_shape_distance_same_coordinates",
          "count": 4,
          "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": 4.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": "route_long_name_contains_short_name",
          "count": 3,
          "effort": "One field per flagged route.",
          "fix": "Drop the short name from route_long_name and keep the long name descriptive, like 'Downtown via 5th Ave'.",
          "owner": "",
          "points": 4.0,
          "severity": "WARNING",
          "what": "Some route long names repeat the route's short name inside them.",
          "why": "Apps show both names together, so riders see the number twice, like '5 5 Downtown'."
        },
        {
          "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": "same_name_and_description_for_stop",
          "count": 1,
          "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": "service_has_no_active_day_of_the_week",
          "count": 1,
          "effort": "A few minutes in your scheduling software.",
          "fix": "Delete the empty calendars or set their service days.",
          "owner": "Likely your export tool",
          "points": 4.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": "big_gap_in_service",
          "count": 18,
          "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": 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."
        }
      ],
      "name": "correctness",
      "score": 62.8,
      "status": "measured",
      "summary": "The MobilityData validator flagged 9 kinds of issue across 6927 instances (0 error, 6907 warning, 20 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": 361,
        "effective_expiry_date": "2027-08-28",
        "feed_end_date": "2027-08-29",
        "feed_start_date": "2026-08-29",
        "feed_version": "1788158765383",
        "has_feed_info": true,
        "last_service_date": "2027-08-28",
        "seasonal_boundary": false,
        "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 361 days.",
      "weight": 0.2
    },
    "realtime": {
      "details": {
        "configured_kinds": [
          "trip_updates",
          "vehicle_positions"
        ],
        "coverage_pct": null,
        "kinds_configured": 2,
        "kinds_reachable": 2,
        "reachable_kinds": [
          "trip_updates",
          "vehicle_positions"
        ],
        "rt_freshness": "fresh",
        "samples": 6,
        "scheduled_trips_in_window": 0,
        "worst_lag_seconds": 0
      },
      "findings": [],
      "name": "realtime",
      "score": 100.0,
      "status": "measured",
      "summary": "Sampled 6 times outside service hours: 2 of 2 configured feeds healthy; vehicle position plausibility was not measurable.",
      "weight": 0.2
    }
  },
  "confidence": {
    "feed_age_days": 0,
    "fetch_source": "origin",
    "level": "high",
    "measured_categories": 4,
    "notes": [
      "All four score categories were measured this run.",
      "Realtime was sampled in one bounded window of 6 snapshots.",
      "The feed was downloaded from the official feed URL on file."
    ],
    "rt_windows": 1,
    "total_categories": 4
  },
  "conformance": {
    "awarded": false,
    "criteria": [
      {
        "detail": "Passes validation with no errors.",
        "key": "valid",
        "met": true
      },
      {
        "detail": "Service data covers the next 361 days.",
        "key": "current",
        "met": true
      },
      {
        "detail": "States wheelchair access on 0% of stops and 0% 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 0% of stops and 0% of trips; the mark needs 90% of each.",
    "version": 2
  },
  "feed": {
    "license_note": "Open Database License (ODbL), recorded by France's National Access Point; credit R\u00e9gion Occitanie (CC Coeur de Loz\u00e8re), identify the ODbL, and preserve share-alike terms where they apply.",
    "reachable": true,
    "sha256": "7f06cdfecf13f8380d02eb587c0747085fed9eb2d45261d83a9ce63c79f133e3",
    "size_bytes": 213209,
    "source_provenance": "official",
    "static_url": "https://www.data.gouv.fr/api/1/datasets/r/2f42baea-fbe1-4b01-bf4a-8232fd83b24e"
  },
  "fetch": {
    "final_url": "https://zenbus.net/gtfs/static/download.zip?dataset=tum",
    "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-09-01T00:00:00+00:00",
  "geo": {
    "bbox": [
      3.44697,
      44.51535,
      3.51495,
      44.54687
    ],
    "lat": 44.5235,
    "lon": 3.49681,
    "stop_count": 123
  },
  "mode_profile": {
    "ferry_only": false,
    "graded": false,
    "has_ferry": false,
    "is_multimodal": false,
    "measured": true,
    "modes": [
      {
        "key": "bus",
        "label": "Bus",
        "route_count": 6,
        "trip_count": 266,
        "trip_share_pct": 100.0
      }
    ],
    "primary_mode": "bus",
    "primary_mode_label": "Bus",
    "route_count": 6,
    "trip_count": 266
  },
  "overall": {
    "grade": "C",
    "margin_to_lower_band": 1.3,
    "margin_to_next_band": 8.7,
    "score": 71.3
  },
  "recommendations": [
    {
      "category": "accessibility",
      "code": "scorecard_route_color_low_contrast",
      "count": 4,
      "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": "4 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (3, 2, 1, SCO1).",
      "why": "Riders with low vision struggle to read a low-contrast route badge. It also washes out on a phone screen in sunlight at the stop."
    },
    {
      "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 if a step-free route exists inside the station. Trip planners can't route anyone through it."
    }
  ],
  "routability": {
    "boardable_stops": 72,
    "findings": [],
    "orphan_stops": 0,
    "single_stop_trips": 0,
    "trips_total": 266
  },
  "route_map": {
    "drawn_route_count": 6,
    "has_shapes": true,
    "path": "data/artifacts/fr-pan-8487/geometry.geojson",
    "route_count": 6,
    "routes": [
      {
        "color": "946AAB",
        "color_name": "purple",
        "has_shape": true,
        "id": "zenbus:Line:16050162:LOC",
        "label": "3",
        "long": "Ligne 3",
        "short": "3",
        "text_color": "FFFFFF",
        "type_label": "Bus"
      },
      {
        "color": "E8308A",
        "color_name": "pink",
        "has_shape": true,
        "id": "zenbus:Line:4549308700426240:LOC",
        "label": "2",
        "long": "Ligne 2",
        "short": "2",
        "text_color": "FFFFFF",
        "type_label": "Bus"
      },
      {
        "color": "028D0B",
        "color_name": "green",
        "has_shape": true,
        "id": "zenbus:Line:4580583746306048:LOC",
        "label": "SCO1",
        "long": "SCO1",
        "short": "SCO1",
        "text_color": "FFFFFF",
        "type_label": "Bus"
      },
      {
        "color": "E9FA00",
        "color_name": "yellow",
        "has_shape": true,
        "id": "zenbus:Line:4606557863018496:LOC",
        "label": "SCO3",
        "long": "SCO3",
        "short": "SCO3",
        "text_color": "000000",
        "type_label": "Bus"
      },
      {
        "color": "0BBBEF",
        "color_name": "teal",
        "has_shape": true,
        "id": "zenbus:Line:4771309419495424:LOC",
        "label": "1",
        "long": "Ligne 1",
        "short": "1",
        "text_color": "FFFFFF",
        "type_label": "Bus"
      },
      {
        "color": "87F500",
        "color_name": "yellow",
        "has_shape": true,
        "id": "zenbus:Line:6033597388554240:LOC",
        "label": "SCO2",
        "long": "SCO2",
        "short": "SCO2",
        "text_color": "000000",
        "type_label": "Bus"
      }
    ],
    "stop_count": 123,
    "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"
  },
  "snapshot_date": "2026-09-01",
  "top_fixes": [
    {
      "code": "scorecard_wheelchair_boarding_unknown",
      "count": 123,
      "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": 25.0,
      "rank": 1,
      "severity": "WARNING",
      "what": "123 of 123 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_wheelchair_accessible_unknown",
      "count": 266,
      "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,
      "rank": 2,
      "severity": "WARNING",
      "what": "266 of 266 trips don't say whether the vehicle is wheelchair accessible.",
      "why": "Even with accessible stops, riders need to know the bus 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,
      "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"
}