{ "agency": { "id": "north-county-transit-district-nctd-14", "name": "North County Transit District (NCTD)" }, "autofix": { "available": true, "download_path": "data/artifacts/north-county-transit-district-nctd-14/corrected.zip", "download_url": "https://d14aimrgrbaz2a.cloudfront.net/data/artifacts/north-county-transit-district-nctd-14/corrected.zip", "fixes": [ { "code": "autofix_trim_whitespace", "count": 1804, "examples": [ "'stop_lat': ' 32.868293' -> '32.868293'", "'stop_lat': ' 32.876949' -> '32.876949'", "'stop_lat': ' 32.867232' -> '32.867232'" ], "label": "Trimmed surrounding whitespace" }, { "code": "autofix_stop_name_case", "count": 1, "examples": [ "WEST RING RD & WEST RING RD -> West Ring Rd & West Ring Rd" ], "label": "Recased shouting stop names" }, { "code": "autofix_route_name_case", "count": 3, "examples": [ "COASTER -> Coaster", "SPRINTER -> Sprinter", "COASTER -> Coaster" ], "label": "Recased shouting route names" } ], "total": 1808 }, "categories": { "completeness": { "details": { "accessibility": { "measures": "presence_not_usability", "score": 37.5, "stops_marked_accessible_pct": 0.0, "stops_marked_not_accessible_pct": 0.0, "stops_stated_pct": 0.0, "trips_stated_pct": 100.0 }, "accessibility_measures": "presence_not_usability", "components": { "contact": 7.5, "fares": 15.0, "headsigns": 14.6, "stop_names": 15.0, "wheelchair_stops": 0.0, "wheelchair_trips": 15.0 }, "fare_free": false, "fares": { "applied": true, "has_leg_rules": true, "has_products": true, "has_transfer_rules": true, "model": "v2", "product_count": 91 }, "flex": { "booking_reachable": false, "booking_rule_count": 0, "has_booking_rules": false, "has_flex": false }, "has_fares": true, "headsign_pct": 97.5, "mixed_case_stop_name_pct": 99.9, "pathways": { "has_entrances": false, "has_levels": false, "has_pathways": false, "has_stations": true, "has_step_free": false, "pathway_count": 0 }, "stops": 1804, "trips": 11202, "wheelchair_accessible_pct": 100.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": 1804, "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": "1804 of 1804 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_missing_headsigns", "count": 284, "effort": "Usually a bulk edit in your scheduling software.", "fix": "Populate trip_headsign to match what the bus displays.", "owner": "Likely your export tool", "points": 0.4, "severity": "WARNING", "what": "284 of 11202 trips have no headsign.", "why": "Riders at the stop can't tell which direction a bus is going." }, { "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 with your feed, so problems linger." }, { "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 connecting entrances, platforms, and any elevators, with a level for each.", "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": 67.1, "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 published.", "weight": 0.25 }, "correctness": { "details": { "distinct_codes": 14, "instances_by_severity": { "ERROR": 762, "INFO": 46, "WARNING": 4901 }, "validator_version": "8.0.1" }, "findings": [ { "code": "trip_distance_exceeds_shape_distance", "count": 598, "effort": "Varies.", "fix": "Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 24.0, "severity": "ERROR", "what": "Trip distance exceeds shape distance (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "equal_shape_distance_diff_coordinates", "count": 114, "effort": "Varies.", "fix": "Review the rule documentation for 'equal_shape_distance_diff_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 24.0, "severity": "ERROR", "what": "Equal shape distance diff coordinates (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "foreign_key_violation", "count": 50, "effort": "Varies.", "fix": "Review the rule documentation for 'foreign_key_violation' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 18.0, "severity": "ERROR", "what": "Foreign key violation (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "equal_shape_distance_same_coordinates", "count": 4114, "effort": "Varies.", "fix": "Review the rule documentation for 'equal_shape_distance_same_coordinates' 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 same coordinates (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "trip_distance_exceeds_shape_distance_below_threshold", "count": 390, "effort": "Varies.", "fix": "Review the rule documentation for 'trip_distance_exceeds_shape_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": "Trip distance exceeds shape distance below threshold (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "equal_shape_distance_diff_coordinates_distance_below_threshold", "count": 270, "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": "missing_recommended_field", "count": 57, "effort": "A field at a time; not urgent.", "fix": "Review the flagged fields and fill in the ones your riders would use.", "owner": "", "points": 8.0, "severity": "WARNING", "what": "Some files are missing recommended (not required) fields.", "why": "Recommended fields like agency_phone or stop descriptions make the feed more useful to riders and trip planners." }, { "code": "expired_calendar", "count": 47, "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": 6.0, "severity": "WARNING", "what": "Some service calendars in the feed have already expired.", "why": "Expired calendars are dead weight and can hide real schedule problems from your staff and vendors." }, { "code": "stop_too_far_from_shape_using_user_distance", "count": 20, "effort": "Varies.", "fix": "Review the rule documentation for 'stop_too_far_from_shape_using_user_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 6.0, "severity": "WARNING", "what": "Stop too far from shape using user distance (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "mixed_case_recommended_field", "count": 2, "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": 4.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": "missing_feed_contact_email_and_url", "count": 1, "effort": "Varies.", "fix": "Review the rule documentation for 'missing_feed_contact_email_and_url' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 4.0, "severity": "WARNING", "what": "Missing feed contact email and url (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "unknown_column", "count": 29, "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": "big_gap_in_service", "count": 13, "effort": "Varies.", "fix": "Review the rule documentation for 'big_gap_in_service' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 0.8, "severity": "INFO", "what": "Big gap in service (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "unused_station", "count": 4, "effort": "Varies.", "fix": "Review the rule documentation for 'unused_station' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 0.5, "severity": "INFO", "what": "Unused station (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." } ], "name": "correctness", "score": 0.0, "status": "measured", "summary": "The MobilityData validator flagged 14 kinds of issue across 5709 instances (762 error, 4901 warning, 46 informational).", "weight": 0.35 }, "freshness": { "details": { "days_until_expiry": 23, "feed_end_date": null, "feed_start_date": null, "feed_version": "Version_20251012", "has_feed_info": true, "last_service_date": "2026-08-02", "seasonal_boundary": false, "service_type": "fixed" }, "findings": [ { "code": "scorecard_feed_expiring_soon", "count": 1, "effort": "One export setting.", "fix": "Re-export with a validity window that reaches at least 60 days out.", "owner": "Likely your export tool", "points": 57.0, "severity": "WARNING", "what": "Service data runs out in 23 day(s).", "why": "When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice." }, { "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", "why": "Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates." } ], "name": "freshness", "score": 23.3, "status": "measured", "summary": "Service data runs out in 23 day(s). Publish an updated feed soon or riders will lose trip planning.", "weight": 0.2 }, "realtime": { "name": "realtime", "status": "not_yet_measured", "summary": "This agency publishes realtime, but the feed needs an access key we don't have yet. Nothing here counts against the grade.", "weight": 0.2 } }, "conformance": { "awarded": false, "criteria": [ { "detail": "3 validator errors to resolve.", "key": "valid", "met": false }, { "detail": "Service data covers the next 33 days.", "key": "current", "met": true }, { "detail": "States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each.", "key": "accessible", "met": false } ], "status": "not_yet", "summary": "This feed is close to the conformance mark. 3 validator errors to resolve. States wheelchair access on 0% of stops and 100% of trips; the mark needs 90% of each." }, "feed": { "license_note": "No stated data license in the Mobility Database; verify before publishing.", "reachable": true, "sha256": "bf24f7df409747ca9a033c75d2f59dfc536af558caf1c004a8dc268ade3e57d2", "size_bytes": 3600631, "static_url": "http://www.gonctd.com/google_transit.zip" }, "generated_at": "2026-06-30T00:00:00+00:00", "geo": { "bbox": [ -117.51421, 32.7169, -116.86978, 33.39416 ], "lat": 33.1569, "lon": -117.25207, "stop_count": 1804 }, "ntd_id_alignment": { "detail": "If you report to the National Transit Database, your GTFS agency_id should be your five-digit NTD ID by report year 2026 (2025 for full reporters). We don't have your NTD ID on file, so this one is not checked yet.", "feed_agency_ids": [ "NCTD" ], "status": "unknown" }, "ntd_readiness": { "pillars": [ { "detail": "Published at a public URL.", "key": "published", "status": "ready" }, { "detail": "3 validator errors to resolve.", "key": "valid", "status": "at_risk" }, { "detail": "Service data covers the next 33 days.", "key": "current", "status": "ready" } ], "status": "at_risk", "summary": "This feed is close to NTD-ready. 3 validator errors to resolve." }, "overall": { "grade": "F", "margin_to_lower_band": 26.8, "margin_to_next_band": 33.2, "score": 26.8 }, "recommendations": [ { "code": "scorecard_route_color_low_contrast", "count": 39, "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": "39 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (101, 302, 303, 304, 305, and more).", "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." }, { "code": "scorecard_stop_name_needs_tts", "count": 1688, "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": "1688 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set (\"Nobel Dr & Lebon Dr\", \"Gilman Dr & Myers Dr\", \"Nobel Dr & Regents Rd\", 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." }, { "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 whether a step-free route exists inside the station, and trip planners can't route anyone through it." } ], "recompute": { "as_of": "2026-07-10", "feed_fetched_date": "2026-06-30", "kind": "freshness" }, "routability": { "boardable_stops": 1792, "findings": [], "orphan_stops": 0, "single_stop_trips": 0, "trips_total": 11202 }, "rubric_version": "1.1", "schema_version": "1.4", "snapshot_date": "2026-07-10", "top_fixes": [ { "code": "scorecard_feed_expiring_soon", "count": 1, "effort": "One export setting.", "fix": "Re-export with a validity window that reaches at least 60 days out.", "owner": "Likely your export tool", "points": 57.0, "rank": 1, "severity": "WARNING", "what": "Service data runs out in 23 day(s).", "why": "When the calendar runs out, trip planners stop showing this agency. Fixing it now is calmer than after riders notice." }, { "code": "trip_distance_exceeds_shape_distance", "count": 598, "effort": "Varies.", "fix": "Review the rule documentation for 'trip_distance_exceeds_shape_distance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 24.0, "rank": 2, "severity": "ERROR", "what": "Trip distance exceeds shape distance (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "equal_shape_distance_diff_coordinates", "count": 114, "effort": "Varies.", "fix": "Review the rule documentation for 'equal_shape_distance_diff_coordinates' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 24.0, "rank": 3, "severity": "ERROR", "what": "Equal shape distance diff coordinates (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." } ], "validator_version": "8.0.1" }