{ "agency": { "id": "muletown-trolley", "name": "Muletown Trolley", "subdivision_code": "US-TN", "subdivision_name": "Tennessee" }, "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": 0.0, "stop_names": 13.5, "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_applicable_trips": 48, "headsign_loop_exempt_trips": 0, "headsign_pct": 0.0, "headsign_scored_pct": 0.0, "mixed_case_stop_name_pct": 89.7, "pathways": { "has_entrances": false, "has_levels": false, "has_pathways": false, "has_stations": false, "has_step_free": false, "pathway_count": 0 }, "stops": 68, "translations": { "feed_lang": "en", "has_translations": false, "languages": [], "translated_tables": [], "translation_count": 0 }, "trips": 48, "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." }, { "code": "scorecard_stop_names_all_caps", "count": 7, "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.5, "severity": "INFO", "what": "About 7 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_missing_headsigns", "count": 48, "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": 15.0, "severity": "WARNING", "what": "48 of 48 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." } ], "name": "completeness", "score": 68.5, "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": 5, "instances_by_severity": { "ERROR": 0, "INFO": 0, "WARNING": 12 }, "validator_version": "8.0.1" }, "findings": [ { "code": "mixed_case_recommended_field", "count": 7, "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": 6.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": "unusable_trip", "count": 2, "effort": "Worth a vendor question if it appears often.", "fix": "Check the flagged trips in your scheduling software; remove them or restore their missing stops.", "owner": "Likely your export tool", "points": 4.0, "severity": "WARNING", "what": "Some trips serve fewer than two stops.", "why": "A trip with one stop can't be ridden; planners ignore it and it may signal an export problem." }, { "code": "expired_calendar", "count": 1, "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": "feed_expiration_date7_days", "count": 1, "effort": "Usually a re-export from your scheduling software.", "fix": "Export and publish an updated GTFS feed that covers at least the next 30 days of service.", "owner": "Likely your export tool", "points": 4.0, "severity": "WARNING", "what": "This feed's service calendar runs out within the next 7 days.", "why": "When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all." }, { "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." } ], "name": "correctness", "score": 78.0, "status": "measured", "summary": "The MobilityData validator flagged 5 kinds of issue across 12 instances (0 error, 12 warning, 0 informational).", "weight": 0.35 }, "freshness": { "details": { "days_until_expiry": -219, "effective_expiry_date": "2025-12-25", "feed_end_date": "2025-12-25", "feed_start_date": "2023-12-06", "feed_version": "20231206", "has_feed_info": true, "last_service_date": "2025-12-25", "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 219 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." } ], "name": "freshness", "score": 0.0, "status": "measured", "summary": "Service data ended 219 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": "mirror", "level": "provisional", "measured_categories": 3, "notes": [ "Realtime quality was not measured this run. It does not count against the grade.", "The agency's own feed URL was unreachable, so the Mobility Database's hosted mirror copy was scored instead." ], "rt_windows": 0, "total_categories": 4 }, "conformance": { "awarded": false, "criteria": [ { "detail": "Passes validation with no errors.", "key": "valid", "met": true }, { "detail": "Service data expired 219 days ago.", "key": "current", "met": false }, { "detail": "States wheelchair access on 100% of stops and 100% of trips.", "key": "accessible", "met": true } ], "status": "not_yet", "summary": "This feed is close to the conformance mark. Service data expired 219 days ago." }, "feed": { "license_note": "No stated data license in the Mobility Database; verify before publishing.", "reachable": true, "sha256": "49bbcab3b37c5f261e14699fffad0d8252f8abd061a1c920a794af9e198a4ea6", "size_bytes": 10078, "static_url": "https://www.sctdd.org/wp-content/uploads/2025/02/gtfs_muletown.zip" }, "fetch": { "final_url": "https://storage.googleapis.com/storage/v1/b/mdb-latest/o/us-tennessee-muletown-trolley-gtfs-2420.zip?alt=media", "max_attempts": 1, "origin_error": "HTTPError", "reader_archive_profile": "raw-v1", "source": "mirror", "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-01T00:00:00+00:00", "geo": { "bbox": [ -87.20806, 35.53322, -87.00742, 35.65635 ], "lat": 35.61274, "lon": -87.04193, "stop_count": 68 }, "mode_profile": { "ferry_only": false, "graded": false, "has_ferry": false, "is_multimodal": false, "measured": true, "modes": [ { "key": "bus", "label": "Bus", "route_count": 4, "trip_count": 48, "trip_share_pct": 100.0 } ], "primary_mode": "bus", "primary_mode_label": "Bus", "route_count": 4, "trip_count": 48 }, "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": [ "MTT" ], "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 expired 219 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. Service data expired 219 days ago, so FTA would find the link out of date." }, "overall": { "grade": "F", "margin_to_lower_band": 55.5, "margin_to_next_band": 4.5, "score": 55.5 }, "recommendations": [ { "category": "accessibility", "code": "scorecard_route_color_low_contrast", "count": 1, "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": "1 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (East).", "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." }, { "category": "accessibility", "code": "scorecard_stop_name_needs_tts", "count": 11, "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": "11 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"North Mail St. and Clark Ave\", \"BETTYS PKWY\", \"Kroger Nashville HWY\", 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." } ], "routability": { "boardable_stops": 68, "findings": [ { "code": "scorecard_single_stop_trips", "count": 2, "effort": "Usually an export setting or a stop_times mapping in your software.", "fix": "Check your scheduling export: every trip should list each stop it calls at, in order, with times.", "owner": "Likely your export tool", "points": 0.0, "severity": "WARNING", "what": "2 of 48 trips list fewer than two stops.", "why": "A trip with one stop has no leg a rider can ride; trip planners can't route anyone on it, so the service effectively does not exist." } ], "orphan_stops": 0, "single_stop_trips": 2, "trips_total": 48 }, "route_map": { "drawn_route_count": 0, "has_shapes": false, "path": "data/artifacts/muletown-trolley/geometry.geojson", "route_count": 4, "routes": [ { "color": "7D3C98", "color_name": "purple", "has_shape": false, "id": "East", "label": "East", "long": "", "short": "East", "text_color": "FFFFFF", "type_label": "Bus" }, { "color": "3498DB", "color_name": "teal", "has_shape": false, "id": "North", "label": "North", "long": "", "short": "North", "text_color": "FFFFFF", "type_label": "Bus" }, { "color": "E74C3C", "color_name": "red", "has_shape": false, "id": "South", "label": "South", "long": "", "short": "South", "text_color": "FFFFFF", "type_label": "Bus" }, { "color": "2ECC71", "color_name": "green", "has_shape": false, "id": "West", "label": "West", "long": "", "short": "West", "text_color": "FFFFFF", "type_label": "Bus" } ], "stop_count": 68, "stop_points_capped": false }, "rubric_version": "1.3", "schema_version": "1.17", "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": "No trips in this feed have a shape_id linked to a row in shapes.txt.", "fix": "Add shapes.txt with a shape_id for each trip's path, and set trips.shape_id to match. Reduced, Rural, and Tribal NTD reporters need this in their published GTFS starting Report Year 2026; Full Reporters needed it in Report Year 2025.", "status": "not_ready", "total_trips": 48, "trips_with_shape": 0 }, "snapshot_date": "2026-08-01", "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 219 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_headsigns", "count": 48, "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": 15.0, "rank": 2, "severity": "WARNING", "what": "48 of 48 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_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" }