{
  "agency": {
    "country": "FR",
    "id": "fr-pan-83994",
    "name": "T\u00e9l\u00e9cabine Eau d'Olle Express (Allemond - Oz)",
    "subdivision_code": "FR-ARA",
    "subdivision_name": "Auvergne-Rh\u00f4ne-Alpes"
  },
  "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": 15.0,
          "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": 6,
        "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": 4,
        "translations": {
          "feed_lang": "fr",
          "has_translations": false,
          "languages": [],
          "translated_tables": [],
          "translation_count": 0
        },
        "trips": 6,
        "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": 4,
          "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": "4 of 4 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": 6,
          "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": "6 of 6 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_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": 45.0,
      "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": 4,
        "instances_by_severity": {
          "ERROR": 0,
          "INFO": 3,
          "WARNING": 4
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "expired_calendar",
          "count": 2,
          "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": "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": "route_long_name_contains_short_name",
          "count": 1,
          "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": "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": 87.5,
      "status": "measured",
      "summary": "The MobilityData validator flagged 4 kinds of issue across 7 instances (0 error, 4 warning, 3 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": 230,
        "effective_expiry_date": "2027-04-19",
        "feed_end_date": "2027-04-19",
        "feed_start_date": "2025-12-06",
        "feed_version": null,
        "has_feed_info": true,
        "last_service_date": "2027-04-19",
        "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 230 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 official feed URL on file."
    ],
    "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 230 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": "Licence Ouverte 2.0 (Etalab), recorded by France's National Access Point; reuse including commercial reuse is permitted with attribution to Loopi, Mobilit\u00e9 Touristique and the update date.",
    "reachable": true,
    "sha256": "deeb8d06326a2a4854964c89d0b6dec462249aba115eb2579a7b0918a12ac03d",
    "size_bytes": 2457,
    "source_provenance": "official",
    "static_url": "https://www.data.gouv.fr/api/1/datasets/r/179d2464-f007-4005-976e-a7fd98eabcfe"
  },
  "fetch": {
    "final_url": "https://static.data.gouv.fr/resources/telecabine-eau-dolle-express-allemond-oz/20260831-084938/gtfs-telecabine-eau-dolle-express-hiver-2026-avril-2027.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-09-01T00:00:00+00:00",
  "geo": {
    "bbox": [
      6.03804,
      45.12603,
      6.07246,
      45.12732
    ],
    "lat": 45.12667,
    "lon": 6.05525,
    "stop_count": 4
  },
  "mode_profile": {
    "ferry_only": false,
    "graded": false,
    "has_ferry": false,
    "is_multimodal": false,
    "measured": true,
    "modes": [
      {
        "key": "aerial_lift",
        "label": "Aerial lift",
        "route_count": 1,
        "trip_count": 6,
        "trip_share_pct": 100.0
      }
    ],
    "primary_mode": "aerial_lift",
    "primary_mode_label": "Aerial lift",
    "route_count": 1,
    "trip_count": 6
  },
  "overall": {
    "grade": "C",
    "margin_to_lower_band": 7.3,
    "margin_to_next_band": 2.7,
    "score": 77.3
  },
  "recommendations": [
    {
      "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": 2,
    "findings": [],
    "orphan_stops": 0,
    "single_stop_trips": 0,
    "trips_total": 6
  },
  "route_map": {
    "drawn_route_count": 1,
    "has_shapes": true,
    "path": "data/artifacts/fr-pan-83994/geometry.geojson",
    "route_count": 1,
    "routes": [
      {
        "color": "000000",
        "color_name": "black",
        "has_shape": true,
        "id": "eau_dolle_express",
        "label": "T\u00e9l\u00e9cabine",
        "long": "T\u00e9l\u00e9cabine Eau d'Olle Express",
        "short": "T\u00e9l\u00e9cabine",
        "text_color": "FFFFFF",
        "type_label": "Aerial lift"
      }
    ],
    "stop_count": 4,
    "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": 4,
      "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": "4 of 4 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": 6,
      "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": "6 of 6 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,
      "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"
}