{
  "agency": {
    "id": "georgia-tech-trolley-stinger-shuttles",
    "name": "Georgia Tech Trolley & Stinger Shuttles",
    "subdivision_code": "US-GA",
    "subdivision_name": "Georgia"
  },
  "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": 4.7,
          "stop_names": 14.4,
          "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": 35,
        "headsign_loop_exempt_trips": 0,
        "headsign_pct": 31.4,
        "headsign_scored_pct": 31.4,
        "mixed_case_stop_name_pct": 96.3,
        "pathways": {
          "has_entrances": false,
          "has_levels": false,
          "has_pathways": false,
          "has_stations": false,
          "has_step_free": false,
          "pathway_count": 0
        },
        "stops": 54,
        "translations": {
          "feed_lang": null,
          "has_translations": false,
          "languages": [],
          "translated_tables": [],
          "translation_count": 0
        },
        "trips": 35,
        "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": 54,
          "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": "54 of 54 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": 35,
          "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": "35 of 35 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_missing_headsigns",
          "count": 24,
          "effort": "Usually one value per route pattern in your scheduling source.",
          "fix": "Add the destination, direction, or 'via' label riders actually see to trip_headsign. Do not copy the route name. If the label changes during the trip, use stop_headsign.",
          "owner": "",
          "points": 10.3,
          "severity": "WARNING",
          "what": "24 of 35 trips lack rider-facing destination or direction text.",
          "why": "When a route has multiple directions or patterns, the route name alone may not tell riders which service is coming."
        },
        {
          "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."
        }
      ],
      "name": "completeness",
      "score": 26.7,
      "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": 1,
          "INFO": 8,
          "WARNING": 12
        },
        "validator_version": "8.0.1"
      },
      "findings": [
        {
          "code": "duplicate_key",
          "count": 1,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'duplicate_key' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 12.0,
          "severity": "ERROR",
          "what": "Duplicate key (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        },
        {
          "code": "route_short_name_too_long",
          "count": 5,
          "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": "expired_calendar",
          "count": 4,
          "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_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": "stops_match_shape_out_of_order",
          "count": 1,
          "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 bus doubling back or skipping ahead, which confuses riders reading the map."
        },
        {
          "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": "unknown_column",
          "count": 5,
          "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."
        },
        {
          "code": "unsorted_stop_times",
          "count": 1,
          "effort": "Varies.",
          "fix": "Review the rule documentation for 'unsorted_stop_times' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.",
          "owner": "",
          "points": 0.5,
          "severity": "INFO",
          "what": "Unsorted stop times (flagged by the MobilityData validator).",
          "why": "See the linked rule for what this affects."
        }
      ],
      "name": "correctness",
      "score": 66.5,
      "status": "measured",
      "summary": "The MobilityData validator flagged 9 kinds of issue across 21 instances (1 error, 12 warning, 8 informational).",
      "weight": 0.35
    },
    "freshness": {
      "details": {
        "days_until_expiry": -4495,
        "effective_expiry_date": "2014-05-03",
        "feed_end_date": null,
        "feed_start_date": null,
        "feed_version": null,
        "has_feed_info": false,
        "last_service_date": "2014-05-03",
        "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 4495 day(s) ago.",
          "why": "When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist."
        },
        {
          "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": 0.0,
      "status": "measured",
      "summary": "Service data ended 4495 day(s) ago. Trip planners have likely already dropped this feed.",
      "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 configured feed URL. Publisher ownership of that URL is not verified."
    ],
    "rt_windows": 0,
    "total_categories": 4
  },
  "conformance": {
    "awarded": false,
    "criteria": [
      {
        "detail": "1 validator error to resolve.",
        "key": "valid",
        "met": false
      },
      {
        "detail": "Service data expired 4495 days ago.",
        "key": "current",
        "met": false
      },
      {
        "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": "This feed does not meet the conformance requirements yet. Here is what the mark needs: 1 validator error to resolve. Service data expired 4495 days ago. States wheelchair access on 0% of stops and 0% 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": "afa6b08bfbed891aae45d490462f41f69d60f4c9e655d6c7682792691dadd411",
    "size_bytes": 526563,
    "source_provenance": "unverified",
    "static_url": "http://documents.atlantaregional.com/transitdata/gtfs_GT.zip"
  },
  "fetch": {
    "final_url": "http://documents.atlantaregional.com/transitdata/gtfs_GT.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": [
      -84.40594,
      33.76875,
      -84.31713,
      33.79718
    ],
    "lat": 33.77717,
    "lon": -84.3956,
    "stop_count": 54
  },
  "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": 35,
        "trip_share_pct": 100.0
      }
    ],
    "primary_mode": "bus",
    "primary_mode_label": "Bus",
    "route_count": 6,
    "trip_count": 35
  },
  "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": [
      "GATECH"
    ],
    "status": "unknown"
  },
  "ntd_readiness": {
    "pillars": [
      {
        "detail": "Published at a public URL.",
        "key": "published",
        "status": "ready"
      },
      {
        "detail": "1 validator error to resolve.",
        "key": "valid",
        "status": "at_risk"
      },
      {
        "detail": "Service data expired 4482 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. 1 validator error to resolve. Service data expired 4482 days ago, so FTA would find the link out of date."
  },
  "overall": {
    "grade": "F",
    "margin_to_lower_band": 37.4,
    "margin_to_next_band": 22.6,
    "score": 37.4
  },
  "recommendations": [
    {
      "category": "accessibility",
      "code": "scorecard_stop_name_needs_tts",
      "count": 29,
      "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": "29 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"5th St./ Fowler NW\", \"5th St./ Fowler SW\", \"5th St./ Techwood\", 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": 54,
    "findings": [],
    "orphan_stops": 0,
    "single_stop_trips": 0,
    "trips_total": 35
  },
  "route_map": {
    "drawn_route_count": 6,
    "has_shapes": true,
    "path": "data/artifacts/georgia-tech-trolley-stinger-shuttles/geometry.geojson",
    "route_count": 6,
    "routes": [
      {
        "color": "1A7A46",
        "color_name": "green",
        "has_shape": true,
        "id": "1079682",
        "label": "Red Stinger Shuttle",
        "long": "",
        "short": "Red Stinger Shuttle",
        "text_color": "FFFFFF",
        "type_label": "Bus"
      },
      {
        "color": "1A7A46",
        "color_name": "green",
        "has_shape": true,
        "id": "1079683",
        "label": "Tech Trolley",
        "long": "",
        "short": "Tech Trolley",
        "text_color": "FFFFFF",
        "type_label": "Bus"
      },
      {
        "color": "1A7A46",
        "color_name": "green",
        "has_shape": true,
        "id": "1079684",
        "label": "Green Stinger Shuttle",
        "long": "",
        "short": "Green Stinger Shuttle",
        "text_color": "FFFFFF",
        "type_label": "Bus"
      },
      {
        "color": "1A7A46",
        "color_name": "green",
        "has_shape": true,
        "id": "1079686",
        "label": "Blue Stinger Shuttle",
        "long": "",
        "short": "Blue Stinger Shuttle",
        "text_color": "FFFFFF",
        "type_label": "Bus"
      },
      {
        "color": "1A7A46",
        "color_name": "green",
        "has_shape": true,
        "id": "1107100",
        "label": "Georgia Tech to Emory Shuttle",
        "long": "",
        "short": "Georgia Tech to Emory Shuttle",
        "text_color": "FFFFFF",
        "type_label": "Bus"
      },
      {
        "color": "1A7A46",
        "color_name": "green",
        "has_shape": true,
        "id": "1113483",
        "label": "Midnight Rambler",
        "long": "",
        "short": "Midnight Rambler",
        "text_color": "FFFFFF",
        "type_label": "Bus"
      }
    ],
    "stop_count": 54,
    "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 35 trips have a shape in shapes.txt.",
    "status": "ready",
    "total_trips": 35,
    "trips_with_shape": 35
  },
  "snapshot_date": "2026-08-23",
  "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 4495 day(s) ago.",
      "why": "When the calendar runs out, trip planners stop showing this agency even though the buses are still running. Riders are told the service does not exist."
    },
    {
      "code": "duplicate_key",
      "count": 1,
      "effort": "Varies.",
      "fix": "Review the rule documentation for 'duplicate_key' 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": "Duplicate key (flagged by the MobilityData validator).",
      "why": "See the linked rule for what this affects."
    },
    {
      "code": "scorecard_wheelchair_boarding_unknown",
      "count": 54,
      "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": 3,
      "severity": "WARNING",
      "what": "54 of 54 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."
    }
  ],
  "validator_version": "8.0.1"
}