GTFS Scorecard
← All agencies

Feed status · checked 2026-07-23

Tideline Water Taxi

Based on the feed this agency publishes

Service mode Ferry

40.3 / 100

First scorecard for this agency

Catalogued in California.

Feed expiredAccessibility gapsFlexible serviceRealtime not yet published

A data-quality and completeness lens to help an agency improve its GTFS feed. Not an official compliance determination from any transit program. New to this? How to read your scorecard. Interactive view of this scorecard. Rubric v1.2, validator 8.0.1.

Measured 3 of 4 score categories from the Mobility Database's mirror copy of the feed.

How we measured this

Confidence in this measurement: provisional.

  • 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.

Confidence describes how much the pipeline could measure this run, not the feed itself. It never changes the grade.

Top things to fix

Fix 01

Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change.Likely your export tool

Service data ended 1179 day(s) ago. 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.

⏱ Usually one export setting; export on a schedule so it never lapses again.worth about +100 points in its category

Fix 02

Add the required column named in the finding to the flagged file.Likely your export tool

A file is missing a column that GTFS requires. Apps may reject the whole file, so riders could lose the affected routes or stops.

⏱ Often an export setting; ask your vendor if it recurs.worth about +12 points in its category

Fix 03

Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every terminal. A field survey can start with the busiest terminals.Likely your team

5 of 5 terminals don't say whether a wheelchair user can board there. Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

⏱ A column in stops.txt; your scheduling software likely has it.worth about +25 points in its category

Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.

How to make and check these changes

Check the result on the published feed. Read the guide, make the change in your tool, and use the next comparable run to see whether the finding is still reported. Only an action or ticket record can attribute who made the change.

  1. Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. · Read the fix guide

    Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  2. Add the required column named in the finding to the flagged file. · Read the fix guide

    Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

  3. Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every terminal. A field survey can start with the busiest terminals. · Read the fix guide

    Make the change. Trillium produces and hosts this feed as a service. These changes are made on their side: send the fix list to your Trillium contact and they apply it and republish.

    Check the result. The next scorecard run checks this finding again. If a comparable check no longer reports it, the feed's clearance log records that result. This confirms feed state, not who made the change. Self-check a feed before you publish.

Rider view: what this feed publishes

A quick read of rider-facing information in this feed.

Schedule visibility
The feed's last published service date was 1179 days ago.
Published accessibility data
Accessibility information is stated for 0% of terminals and 0% of trips. This measures published data, not whether terminals or vessels are physically usable.
Fare information
No fare information is published in the feed.
Realtime information
Realtime-feed availability and live-arrival coverage are not known from this scorecard.

Important: This does not rate service reliability. Riders should confirm current service alerts, fares, and accessibility accommodations with the transit operator before traveling.

Ungraded capability read

Ferry data profile

A ferry-specific view of what this GTFS feed publishes. Schedule measurements use ferry routes and trips only; fare and realtime facts are labelled as whole-feed. Unknown values are not treated as no.

Ferry service
2 routes · 8 trips
Terminal structure
3 ferry boarding locations; no parent-station hierarchy is published.
Terminal access
Not applicable: no ferry boarding location is linked to a parent station, so stop_access is not permitted here.
Published accessibility
Unknown: none of the 3 ferry boarding locations publish wheelchair_boarding. Unknown: none of the 8 ferry trips publish wheelchair_accessible. This reports published values, not verified physical usability.
Bicycles
Unknown: none of the 8 ferry trips publish bikes_allowed.
Cars
Unknown: none of the 8 ferry trips publish cars_allowed.
Fares
Whole feed: no applied fare data is published. This is not evidence that ferry service is free.
Realtime
Whole feed: no GTFS-Realtime endpoints are configured in this scorecard.

Descriptive only. This profile does not change the grade or verify vessels, terminal facilities, vehicle carriage, fares, or accessibility in the real world. Field meanings follow the GTFS Schedule reference.

Send Trillium a fix request

This feed is produced and hosted by Trillium. Copy this and send it to your Trillium contact; they make the change and republish the feed. Each fix names the validator notice and a guide link.

Send the agency a note

Supporting this agency? Copy this and email it to them. It names what lapsed, why it matters to riders, and the one setting to change.

Score by category

Correctness60.0 / 100

The MobilityData validator flagged 10 kinds of issue across 63 instances (2 error, 14 warning, 47 informational).

Freshness0.0 / 100

Service data ended 1179 day(s) ago. Trip planners have likely already dropped this feed.

Rider experience45.0 / 100

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.

Accessibility0 / 100

0% of terminals state accessibility (0% marked accessible). Reflects what the feed states, not verified physical usability.

Realtime qualityNot yet measured

Not scored yet. Nothing here counts against the grade.

Routes and terminals

Each route is drawn once, using the longest shape its trips follow; terminals are the dots.

Skip to route and terminal data

Basemap: OpenFreeMap, © OpenStreetMap contributors. Routes and terminals: this agency's GTFS feed.

  • Berk - P52 - P1.5 (blue)
  • Berk-SF (blue)
Routes in Tideline Water Taxi's feed
RouteTypeLine color
Berk - P52 - P1.5 Berkeley - Pier 52 - Pier 1.5Ferryblue
Berk-SF Berkeley - San FranciscoFerryblue

This feed has 5 terminals.

List every terminal
  • Marina Bay Yacht Harbor, Richmond CA
  • San Francisco Pier 1.5
  • San Fransisco Pier 40
  • Pier 52 San Francisco, CA
  • Berkeley Marina, Berkeley CA

Over time

This is the first scorecard for this agency. A trend and a "what changed" summary appear here once it has been checked more than once.

Everything we checked

15 findings, ordered by severity.

Show every finding
  • Error2 instances

    A file is missing a column that GTFS requires.

    Apps may reject the whole file, so riders could lose the affected routes or stops.

    Fix: Add the required column named in the finding to the flagged file. (Often an export setting; ask your vendor if it recurs.)

    Validator rule: missing_required_column · Read the fix guide · See MobilityData GTFS Validator rules

  • Error1 instance

    Service data ended 1179 day(s) ago.

    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.

    Fix: Re-export the feed with a calendar that reaches further out, and set feed_info feed_end_date past your next service change. (Usually one export setting; export on a schedule so it never lapses again.)

    Validator rule: scorecard_feed_expired · Read the fix guide · See GTFS Best Practices

  • Warning8 instances

    Missing bike allowance (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    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. (Varies.)

    Validator rule: missing_bike_allowance · See MobilityData GTFS Validator rules

  • Warning8 instances

    8 of 8 trips don't say whether the vehicle is wheelchair accessible.

    Even with accessible terminals, riders need to know the vessel itself can take them.

    Fix: Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. (A default or per-trip field in your export.)

    Validator rule: scorecard_wheelchair_accessible_unknown · Read the fix guide · See GTFS Schedule reference

  • Warning5 instances

    5 of 5 terminals don't say whether a wheelchair user can board there.

    Riders who use wheelchairs can't plan a trip when accessibility is marked 'unknown'; apps show no information at all.

    Fix: Set wheelchair_boarding to 1 (accessible) or 2 (not accessible) for every terminal. A field survey can start with the busiest terminals. (A column in stops.txt; your scheduling software likely has it.)

    Validator rule: scorecard_wheelchair_boarding_unknown · Read the fix guide · See GTFS Schedule reference

  • Warning2 instances

    Some terminals exist in the feed but no trip serves them.

    Riders may go to a terminal where no vessel is scheduled to arrive.

    Fix: Remove retired stops from the export, or add them back to the trips that should serve them. (A review pass in your scheduling software.)

    Validator rule: stop_without_stop_time · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    Some service calendars in the feed have already ended.

    Expired calendars are dead weight and can hide real schedule problems from your staff and vendors.

    Fix: Remove past service periods the next time you export the feed. (One setting in most export tools.)

    Validator rule: expired_calendar · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    This feed's service calendar runs out within the next 7 days.

    When the calendar ends, Google Maps and other trip planners drop your agency entirely. Riders see no service at all.

    Fix: Export and publish an updated GTFS feed that covers at least the next 30 days of service. (Usually a re-export from your scheduling software.)

    Validator rule: feed_expiration_date7_days · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    Route short name too long (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    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. (Varies.)

    Validator rule: route_short_name_too_long · See MobilityData GTFS Validator rules

  • Warning1 instance

    Many of the feed's trips don't run at all in the next 7 days.

    It usually means old service periods are still in the export, making the feed bigger and harder to check.

    Fix: Trim past service periods the next time you export. (One setting in most export tools.)

    Validator rule: trip_coverage_not_active_for_next7_days · Read the fix guide · See MobilityData GTFS Validator rules

  • Warning1 instance

    The feed contains no fare information.

    Riders see 'fare unknown' in trip planners and can't budget their trip; visitors are most affected.

    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. (A small file for most flat-fare systems.)

    Validator rule: scorecard_no_fare_data · Read the fix guide · See GTFS Best Practices

  • Warning1 instance

    This feed describes flexible (demand-responsive) service but has no booking_rules.txt.

    Riders can see the service area but not how or when to reserve a trip, so they can't actually use the service.

    Fix: Add booking_rules.txt saying how far ahead and how to book (phone, app, or web). (A small file; one rule often covers the whole service.)

    Validator rule: scorecard_flex_no_booking_rules · Read the fix guide · See GTFS Schedule reference

  • Info37 instances

    Some files contain columns that are not part of the GTFS spec.

    Harmless to riders, but apps ignore these columns and they can hide typos in real column names.

    Fix: Check the flagged column names for misspellings of standard GTFS fields; remove them if they are vendor extras. (A quick look at the flagged files.)

    Validator rule: unknown_column · Read the fix guide · See MobilityData GTFS Validator rules

  • Info9 instances

    The feed includes a file that is not part of the GTFS spec.

    Apps ignore files they don't know, and a stray file can hide a misspelled standard file name.

    Fix: Check the flagged file name for a typo of a standard GTFS file. Remove it if it is a vendor extra. (A quick look at the flagged file.)

    Validator rule: unknown_file · Read the fix guide · See MobilityData GTFS Validator rules

  • Info1 instance

    Some service dates fall outside the date window set in feed_info.txt.

    feed_info.txt should span every day your service runs, so apps know when the data applies.

    Fix: Widen feed_start_date and feed_end_date to cover all service dates, or fix the dates that fall outside. (Two fields in feed_info.txt, or one export setting.)

    Validator rule: service_window_outside_feed_period · Read the fix guide · See MobilityData GTFS Validator rules

Beyond the grade

Opportunities that do not change your grade today: fare detail, on-demand service, and deeper accessibility data.

  • Flex zones are published but no booking_rules.txt is present.

    Consider: Add booking_rules.txt with how far ahead and how to reserve (phone, app, or web).

NTD GTFS readiness Not ready

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.

Published Ready
Published at a public URL.
Valid Needs attention
1 validator error to resolve.
Current Not ready
Service data expired 1179 days ago, so FTA would find the link out of date.
agency_id provided Ready
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.
agency_id equals your NTD ID (optional) Not checked yet
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.
shapes.txt covers your trips Ready
All 8 trips have a shape in shapes.txt.

In plain words: if you report to the federal transit database, you have to publish a working, up-to-date feed, provide a stable agency_id for each represented reporter, and confirm the feed and P-50 crosswalk each year. This box is a heads-up; your filings are the official check.

A readiness signal mapping this feed to the FTA National Transit Database GTFS requirement (Report Year 2023 onward: a public, valid, current feed, certified annually on the D-10). For RY2026, each represented reporter needs a stable agency_id, unique within the feed and crosswalked to its five-digit NTD ID on P-50; the values do not need to be equal. FTA also requires shapes.txt in the published GTFS: Full Reporters from Report Year 2025, and Reduced, Rural, and Tribal Reporters from Report Year 2026. Not an official determination; your certification is the official check.

Conformance mark Not yet

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.

Valid Not yet
1 validator error to resolve.
Current Not yet
Service data expired 1179 days ago.
Accessible Not yet
States wheelchair access on 0% of terminals and 0% of trips; the mark needs 90% of each.

In plain words: earn this mark when your feed passes validation, has not expired, and says whether nearly every terminal and trip is wheelchair accessible.

A pass credential for a feed that is valid, current, and states wheelchair access on nearly every terminal and trip. Accessibility here measures what the feed publishes, not whether a terminal is physically usable. How the conformance mark works.

Can riders use it?

Checks beyond structural validation: places where the feed is valid but a rider still could not travel.

  • 2 of 5 boardable stops are never served by any trip. Riders see these stops in apps and on the map but can never catch anything there, which erodes trust in the data. Remove stops no route serves, or add the trips that should call at them.

These do not change the grade. They catch trips with no rideable leg and stops no trip serves, the kind of gap a trip planner trips over.

Below the Google and Apple Maps four-week coverage bar. This feed's last day of service has passed, so Google and Apple Maps will stop showing your agency. Re-export with a calendar that covers at least the next four weeks. The feed also carries 2 validator errors, the other thing Maps checks at onboarding; the findings below name each fix.

How this agency maps to the standards

The scorecard is a data-quality lens, not a compliance determination. Its universal references describe good GTFS and useful rider information. Useful references here are GTFS Schedule Best Practices, GTFS-Realtime Best Practices, MobilityData grading scheme, Google Transit publication guidance, FTA National Transit Database GTFS requirement. Read the full standards crosswalk.

In California, the published guideline is California Transit Data Guidelines. Caltrans' published quality guidelines and compliance checklist; this rubric is anchored to them.

California Minimum GTFS Guidelines checklist (3 of 6 measured items met)

The state's own Data Process Checklist, matched item by item to what this scorecard already measures. An item marked "not measured here" is real ground the checklist covers that this tool does not check; see the official checklist for the full picture.

  • Meets Publish GTFS Schedule at a stable, automatically-fetchable URL

    The published feed URL downloaded at the last check.

  • Not measured here Implement required fields: Fares v2, text-to-speech stop names, shapes.txt, wheelchair_boarding, and Pathways where applicable

    This scorecard measures wheelchair_boarding, shapes.txt coverage, fare data, and station pathways separately, below; it does not check the Fares v2 format specifically or text-to-speech stop names.

  • Not measured here Achieve a passing score in every category of the MobilityData GTFS Grading Scheme v1

    This scorecard automates a proxy for the Grading Scheme's rider-facing fields (see the standards crosswalk) rather than running the scheme itself, which grades by comparison to the real world by hand.

  • Not measured here Publish changes to the base schedule at least one week ahead of every service change

    This scorecard does not track a feed's publish history, so advance notice cannot be checked.

  • Gap Produce no critical errors in the MobilityData GTFS Validator

    1 validator error to resolve.

  • Not measured here Publish Trip Updates, Vehicle Positions, and Alerts feeds

    This scorecard checks realtime reachability and freshness overall; it does not check for all three feed types individually.

  • Not measured here Update Trip Updates and Vehicle Positions at least every 20 seconds

    This scorecard samples realtime freshness; it does not check this specific 20-second cadence.

  • Not measured here Publish information for at least 99% of vehicles in service

    This scorecard measures the share of scheduled trips represented in TripUpdates, a related but different figure than vehicle coverage.

  • Not measured here Keep 100% of trip_ids consistent between Schedule and Realtime

    This scorecard does not currently check trip_id consistency between the Schedule and Realtime feeds.

  • Not measured here Produce no critical errors in the Center for Urban Transportation Research realtime validator

    This scorecard does not run the CUTR realtime validator.

  • Not measured here Publish accessible feed links on the agency or regional partner website

    This scorecard does not check the agency's own website.

  • Not measured here Register GTFS and GTFS-Realtime feeds with transit.land and the Mobility Database

    This scorecard does not currently check aggregator registration for this section.

  • Meets Designate a technical contact in feed_info.txt's feed_contact_email

    feed_info.txt states a technical contact.

  • Gap wheelchair_boarding stated on stops and trips

    States wheelchair access on 0% of terminals and 0% of trips.

  • Meets shapes.txt with a shape for every trip

    All 8 trips have a shape in shapes.txt.

  • Gap Fare data published, or the service marked fare-free

    No fare data is published.

Correctness 60 / 100
GTFS Schedule best practices, checked by the MobilityData validator. MobilityData grading covers stop locations, route names, and colors. Google Transit requires a feed to pass validation for publication. FTA NTD readiness also checks that the published feed is valid.
Freshness 0 / 100
GTFS Schedule best practices call for a dataset that stays current. An expired calendar can remove service from Google Transit and other rider trip planners. FTA NTD readiness also checks that the published feed is current.
Rider experience 45 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality Not yet published
GTFS-Realtime best practices: a stable URL, high uptime, and frequent updates.

Show your grade

Put a badge on your agency site or feed README. It updates after each completed scoring check and links back to this scorecard.

Tideline Water Taxi GTFS data quality grade: F

Prefer a shields.io style? Point a dynamic endpoint badge at the published badge.json.

Cite this record

This page updates on every check. The record below does not: it is the dated file this grade came from, published at https://gtfsscorecard.org/data/artifacts/tideline-water-taxi/2026-07-23.json and never overwritten, pinning the grade, category scores, rubric version, validator version, reader archive profile, and the scored feed's sha256 as they stood on 2026-07-23. Use it in a board packet, a regulatory filing, or a research citation instead of linking the live page, whose content will differ on your next visit.

Citing the tool itself rather than one agency's record? Use the repo's CITATION.cff.