{ "agency": { "id": "tideline-water-taxi", "name": "Tideline Water Taxi", "subdivision_code": "US-CA", "subdivision_name": "California" }, "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": true }, "has_fares": false, "headsign_pct": 100.0, "mixed_case_stop_name_pct": 100.0, "pathways": { "has_entrances": false, "has_levels": false, "has_pathways": false, "has_stations": false, "has_step_free": false, "pathway_count": 0 }, "stops": 5, "translations": { "feed_lang": "en", "has_translations": false, "languages": [], "translated_tables": [], "translation_count": 0 }, "trips": 8, "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": 5, "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 terminal. A field survey can start with the busiest terminals.", "owner": "Likely your team", "points": 25.0, "severity": "WARNING", "what": "5 of 5 terminals 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": 8, "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": "8 of 8 trips don't say whether the vehicle is wheelchair accessible.", "why": "Even with accessible terminals, riders need to know the vessel 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_flex_no_booking_rules", "count": 1, "effort": "A small file; one rule often covers the whole service.", "fix": "Add booking_rules.txt saying how far ahead and how to book (phone, app, or web).", "owner": "", "points": 0.0, "severity": "WARNING", "what": "This feed describes flexible (demand-responsive) service but has no booking_rules.txt.", "why": "Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service." } ], "name": "completeness", "score": 45.0, "status": "measured", "summary": "0% of terminals state wheelchair accessibility (0% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a terminal is physically usable. Fare data is not published.", "weight": 0.25 }, "correctness": { "details": { "distinct_codes": 10, "instances_by_severity": { "ERROR": 2, "INFO": 47, "WARNING": 14 }, "validator_version": "8.0.1" }, "findings": [ { "code": "missing_required_column", "count": 2, "effort": "Often an export setting; ask your vendor if it recurs.", "fix": "Add the required column named in the finding to the flagged file.", "owner": "Likely your export tool", "points": 12.0, "severity": "ERROR", "what": "A file is missing a column that GTFS requires.", "why": "Apps may reject the whole file, so riders could lose the affected routes or stops." }, { "code": "missing_bike_allowance", "count": 8, "effort": "Varies.", "fix": "Review the rule documentation for 'missing_bike_allowance' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.", "owner": "", "points": 6.0, "severity": "WARNING", "what": "Missing bike allowance (flagged by the MobilityData validator).", "why": "See the linked rule for what this affects." }, { "code": "stop_without_stop_time", "count": 2, "effort": "A review pass in your scheduling software.", "fix": "Remove retired stops from the export, or add them back to the trips that should serve them.", "owner": "Likely your export tool", "points": 4.0, "severity": "WARNING", "what": "Some terminals exist in the feed but no trip serves them.", "why": "Riders may go to a terminal where no vessel is scheduled to arrive." }, { "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": "route_short_name_too_long", "count": 1, "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": "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": 37, "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": "unknown_file", "count": 9, "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.8, "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": "service_window_outside_feed_period", "count": 1, "effort": "Two fields in feed_info.txt, or one export setting.", "fix": "Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside.", "owner": "Likely your export tool", "points": 0.5, "severity": "INFO", "what": "Some service dates fall outside the date window set in feed_info.txt.", "why": "feed_info.txt should span every day your service runs, so apps know when the data applies." } ], "name": "correctness", "score": 60.0, "status": "measured", "summary": "The MobilityData validator flagged 10 kinds of issue across 63 instances (2 error, 14 warning, 47 informational).", "weight": 0.35 }, "freshness": { "details": { "days_until_expiry": -1179, "effective_expiry_date": "2023-05-01", "feed_end_date": "2023-05-01", "feed_start_date": "2022-12-30", "feed_version": "UTC: 30-Dec-2022 22:08", "has_feed_info": true, "last_service_date": "2023-05-01", "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 1179 day(s) ago.", "why": "When the calendar runs out, trip planners stop showing this agency even though the vessels are still running. Riders are told the service does not exist." } ], "name": "freshness", "score": 0.0, "status": "measured", "summary": "Service data ended 1179 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": "1 validator error to resolve.", "key": "valid", "met": false }, { "detail": "Service data expired 1179 days ago.", "key": "current", "met": false }, { "detail": "States wheelchair access on 0% of terminals and 0% of trips; the mark needs 90% of each.", "key": "accessible", "met": false } ], "status": "not_yet", "summary": "This feed is close to the conformance mark. 1 validator error to resolve. Service data expired 1179 days ago. States wheelchair access on 0% of terminals and 0% 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": "28c61e0c2874272e5fb53a922e8ff79043471a29d08e045b975df49dd4097119", "size_bytes": 8602, "static_url": "http://trilliumtransit.com/transit_feeds/tidelinewatertaxi-ca-us/tidelinewatertaxi-ca-us.zip" }, "ferry_profile": { "accessibility": { "measures": "published_values_not_physical_usability", "terminals": { "allowed_count": 0, "allowed_pct": 0.0, "not_allowed_count": 0, "not_allowed_pct": 0.0, "stated_count": 0, "stated_pct": 0.0, "total_count": 3 }, "trips": { "allowed_count": 0, "allowed_pct": 0.0, "not_allowed_count": 0, "not_allowed_pct": 0.0, "stated_count": 0, "stated_pct": 0.0, "total_count": 8 } }, "bikes": { "allowed_count": 0, "allowed_pct": 0.0, "not_allowed_count": 0, "not_allowed_pct": 0.0, "stated_count": 0, "stated_pct": 0.0, "total_count": 8 }, "cars": { "allowed_count": 0, "allowed_pct": 0.0, "not_allowed_count": 0, "not_allowed_pct": 0.0, "stated_count": 0, "stated_pct": 0.0, "total_count": 8 }, "fares": { "applied": false, "fare_free": false, "model": "none", "scope": "whole_feed" }, "graded": false, "measured": true, "realtime": { "configured_kinds": [], "kinds_configured": 0, "scope": "whole_feed" }, "route_count": 2, "scope": "ferry_routes_and_trips", "stop_access": { "direct_count": 0, "eligible_terminal_count": 0, "stated_count": 0, "stated_pct": null, "through_station_count": 0 }, "terminal_hierarchy": { "boarding_location_count": 3, "parented_boarding_location_count": 0, "parented_boarding_location_pct": 0.0, "referenced_station_count": 0 }, "trip_count": 8 }, "fetch": { "final_url": "https://storage.googleapis.com/storage/v1/b/mdb-latest/o/us-california-tideline-water-taxi-gtfs-52.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-07-23T00:00:00+00:00", "geo": { "bbox": [ -122.39503, 37.77084, -122.31393, 37.91366 ], "lat": 37.79748, "lon": -122.38579, "stop_count": 5 }, "mode_profile": { "ferry_only": true, "graded": false, "has_ferry": true, "is_multimodal": false, "measured": true, "modes": [ { "key": "ferry", "label": "Ferry", "route_count": 2, "trip_count": 8, "trip_share_pct": 100.0 } ], "primary_mode": "ferry", "primary_mode_label": "Ferry", "route_count": 2, "trip_count": 8 }, "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": [ "513" ], "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 1179 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 1179 days ago, so FTA would find the link out of date." }, "overall": { "grade": "F", "margin_to_lower_band": 40.3, "margin_to_next_band": 19.7, "score": 40.3 }, "recommendations": [ { "category": "flex", "code": "scorecard_flex_completeness_no_booking_rules", "count": 1, "effort": "A small file; one rule often covers the whole service.", "fix": "Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).", "owner": "", "points": 0.0, "severity": "WARNING", "what": "Flex zones are published but no booking_rules.txt is present.", "why": "Riders can see the service area but not how to book, so they can't complete a trip." } ], "routability": { "boardable_stops": 5, "findings": [ { "code": "scorecard_orphan_stops", "count": 2, "effort": "A cleanup pass in your scheduling software.", "fix": "Remove stops no route serves, or add the trips that should call at them.", "owner": "Likely your export tool", "points": 0.0, "severity": "INFO", "what": "2 of 5 boardable stops are never served by any trip.", "why": "Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data." } ], "orphan_stops": 2, "single_stop_trips": 0, "trips_total": 8 }, "route_map": { "drawn_route_count": 2, "has_shapes": true, "path": "data/artifacts/tideline-water-taxi/geometry.geojson", "route_count": 2, "routes": [ { "color": "1E22AA", "color_name": "blue", "has_shape": true, "id": "13607", "label": "Berk - P52 - P1.5", "long": "Berkeley - Pier 52 - Pier 1.5", "short": "Berk - P52 - P1.5", "text_color": "FFFFFF", "type_label": "Ferry" }, { "color": "1E22AA", "color_name": "blue", "has_shape": true, "id": "5760", "label": "Berk-SF", "long": "Berkeley - San Francisco", "short": "Berk-SF", "text_color": "FFFFFF", "type_label": "Ferry" } ], "stop_count": 5, "stop_points_capped": false }, "rubric_version": "1.2", "schema_version": "1.16", "scoring_profile": { "id": "gtfs-scorecard-1.2", "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.2" }, "shapes_readiness": { "detail": "All 8 trips have a shape in shapes.txt.", "status": "ready", "total_trips": 8, "trips_with_shape": 8 }, "snapshot_date": "2026-07-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 1179 day(s) ago.", "why": "When the calendar runs out, trip planners stop showing this agency even though the vessels are still running. Riders are told the service does not exist." }, { "code": "missing_required_column", "count": 2, "effort": "Often an export setting; ask your vendor if it recurs.", "fix": "Add the required column named in the finding to the flagged file.", "owner": "Likely your export tool", "points": 12.0, "rank": 2, "severity": "ERROR", "what": "A file is missing a column that GTFS requires.", "why": "Apps may reject the whole file, so riders could lose the affected routes or stops." }, { "code": "scorecard_wheelchair_boarding_unknown", "count": 5, "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 terminal. A field survey can start with the busiest terminals.", "owner": "Likely your team", "points": 25.0, "rank": 3, "severity": "WARNING", "what": "5 of 5 terminals 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" }