GTFS Scorecard
← All agencies

Feed status · checked 2026-09-13

Catalina Express

Based on the feed source on file; publisher ownership is not verified

Service mode Ferry

54.5 / 100

unchanged since 2026-09-12

Catalogued in California.

Review service end dateAccessibility gapsRealtime 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.3, validator 8.0.1.

Checked for changes 30 hours ago; last changed 76 days ago.

Measured 3 of 4 score categories from the feed URL on file (publisher not verified).

How we measured this

Confidence in this measurement: medium.

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

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

Review the rule documentation for 'missing_required_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

Missing required file (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +12 points in its category

Fix 02

Review the rule documentation for 'invalid_input_files_in_subfolder' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

Invalid input files in subfolder (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +12 points in its category

Fix 03

Review the rule documentation for 'missing_calendar_and_calendar_date_files' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

Missing calendar and calendar date files (flagged by the MobilityData validator). See the linked rule for what this affects.

⏱ Varies.worth about +12 points in its category

This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.

Finding handoff

Move one finding to a recheck

Select one finding. Copy the request, make the change in the feed-producing tool, then compare the next complete run.

Feed evidence
Missing required file (flagged by the MobilityData validator).
Next action
Review the rule documentation for 'missing_required_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.
Recheck
Publish the changed feed at the same URL. On the next complete, comparable scorecard run, confirm that this finding is no longer reported.
Copy handoff text
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. Review the rule documentation for 'missing_required_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Make the change. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.

    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. Review the rule documentation for 'invalid_input_files_in_subfolder' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Make the change. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.

    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. Review the rule documentation for 'missing_calendar_and_calendar_date_files' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed.

    Make the change. This feed is published from a code repository, so whoever maintains that repository regenerates the zip — often planning staff or a consultant. The fix happens in the source data, then a fresh export is committed.

    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 states that service is published through 2050-01-01. This may be intentional or a placeholder; confirm current service with the transit operator.
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
6 routes · 28 trips
Terminal structure
4 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 4 ferry boarding locations publish wheelchair_boarding. Unknown: none of the 28 ferry trips publish wheelchair_accessible. This reports published values, not verified physical usability.
Bicycles
Unknown: none of the 28 ferry trips publish bikes_allowed.
Cars
Unknown: none of the 28 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 your vendor a fix request

This feed is published from a code repository. Forward this to whoever maintains that repository; the fix happens in the source data, then a fresh export is committed. Each fix names the validator notice and a guide link.

Score by category

Correctness60.0 / 100

The MobilityData validator flagged 4 kinds of issue across 8 instances (7 error, 1 warning, 0 informational).

Freshness85.0 / 100

Service is published through 2050-01-01. It may be intentional, but confirm the end date before treating the feed as maintained.

Rider experience22.5 / 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.

1 accessibility depth signal

  • 3 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("CRESCENT AV/CATALINA AV", "GOLDEN SHORE/320 GOLDEN SHORE", "STREET OF THE GOLDEN LANTERN/34675 STREET OF THE GOLDEN LANTERN").

    Consider: Add tts_stop_name with the spoken form, e.g. 'Main Street and Second Avenue', for the affected stops.

Opportunities to strengthen the data, not deductions from the sub-score above. States what the second accessibility lens can check from the feed, 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.

This feed has 4 terminals.

Skip to route and terminal data

The route and terminal data is ready below. Load the map only when you want the geographic view. It uses additional data.

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

  • CATALINA EXPRESS (teal)
  • CATALINA EXPRESS_1 (teal)
  • CATALINA EXPRESS (teal)
  • CATALINA EXPRESS_1 (teal)
  • CATALINA EXPRESS (teal)
  • CATALINA EXPRESS_1 (teal)
Routes in Catalina Express's feed
RouteTypeLine color
CATALINA EXPRESSFerryteal
CATALINA EXPRESS_1Ferryteal
CATALINA EXPRESSFerryteal
CATALINA EXPRESS_1Ferryteal
CATALINA EXPRESSFerryteal
CATALINA EXPRESS_1Ferryteal
List every terminal
  • CRESCENT AV/CATALINA AV
  • SAN PEDRO CATALINA TERMINAL
  • GOLDEN SHORE/320 GOLDEN SHORE
  • STREET OF THE GOLDEN LANTERN/34675 STREET OF THE GOLDEN LANTERN

Over time

Overall score across the last 2 checks — unchanged since 2026-09-12.

2026-09-12: 54.52026-09-13: 54.5
Show the numbers
CheckScoreChange
2026-09-1254.5 first check
2026-09-1354.5 no change

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change

Everything we checked

10 findings, ordered by severity.

Show every finding
  • Error5 instances

    Missing required file (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'missing_required_file' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: missing_required_file · See MobilityData GTFS Validator rules

  • Error1 instance

    Invalid input files in subfolder (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'invalid_input_files_in_subfolder' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: invalid_input_files_in_subfolder · See MobilityData GTFS Validator rules

  • Error1 instance

    Missing calendar and calendar date files (flagged by the MobilityData validator).

    See the linked rule for what this affects.

    Fix: Review the rule documentation for 'missing_calendar_and_calendar_date_files' at https://gtfs-validator.mobilitydata.org/rules.html and check the flagged rows in your feed. (Varies.)

    Finding code: missing_calendar_and_calendar_date_files · See MobilityData GTFS Validator rules

  • Warning28 instances

    28 of 28 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.)

    Finding code: scorecard_wheelchair_accessible_unknown · Read the fix guide for scorecard_wheelchair_accessible_unknown · See GTFS Schedule reference

  • Warning4 instances

    4 of 4 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.)

    Finding code: scorecard_wheelchair_boarding_unknown · Read the fix guide for scorecard_wheelchair_boarding_unknown · See GTFS Schedule reference

  • Warning1 instance

    A file GTFS asks for (usually feed_info.txt) is missing.

    feed_info.txt tells apps who publishes the feed and when it expires; without it nobody is warned before data goes stale.

    Fix: Add feed_info.txt with publisher name, URL, language, and feed_start_date/feed_end_date. (One small file, set once in export settings.)

    Finding code: missing_recommended_file · Read the fix guide for missing_recommended_file · See MobilityData GTFS Validator rules

  • Warning1 instance

    feed_info.txt is missing its start/end dates (the file itself is absent)

    Apps and this scorecard can't warn anyone before the feed goes stale without stated validity dates.

    Fix: Add feed_info.txt with feed_start_date and feed_end_date to your export. (Two fields, set once in export settings.)

    Finding code: scorecard_missing_feed_info_dates · Read the fix guide for scorecard_missing_feed_info_dates · 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.)

    Finding code: scorecard_no_fare_data · Read the fix guide for scorecard_no_fare_data · See GTFS Best Practices

  • Info4 instances

    About 4 stop names are written in ALL CAPS.

    Mixed-case names are easier to read in apps and are read more naturally by screen readers.

    Fix: Rename stops to mixed case where the language has letter case (for example, 'Central Station'). (Often a bulk fix in your scheduling software.)

    Finding code: scorecard_stop_names_all_caps · Read the fix guide for scorecard_stop_names_all_caps · See GTFS Best Practices

  • Info1 instance

    feed_info.txt has no technical contact (feed_contact_email or feed_contact_url).

    App makers and state data programs have nobody to email when they spot a problem. Small errors then sit in the feed for months.

    Fix: Add feed_contact_email to feed_info.txt. (One field.)

    Finding code: scorecard_no_feed_contact · Read the fix guide for scorecard_no_feed_contact · See MobilityData GTFS Validator rules

NTD GTFS readiness Needs attention

This feed is close to NTD-ready. 3 validator errors to resolve.

Published Ready
Published at a public URL.
Valid Needs attention
3 validator errors to resolve.
Current Ready
The published window is current, but its service end date is unusually distant; confirm that date is intentional.
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 28 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

Two requirements remain for this feed to earn the conformance mark. 3 validator errors to resolve. States wheelchair access on 0% of terminals and 0% of trips; the mark needs 90% of each.

Valid Not yet
3 validator errors to resolve.
Current Met
The published window is current, but its service end date is unusually distant; confirm that date is intentional.
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.

Clears the Google and Apple Maps four-week coverage bar. This feed clears the four-week coverage window, but its service end date is unusually distant. Confirm that date is intentional before treating it as evidence of ongoing maintenance. The feed also carries 7 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 (2 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

    3 validator errors 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.

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

    feed_info.txt has no feed_contact_email or feed_contact_url.

  • 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 28 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 85 / 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 22 / 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.

Part of the California portfolio: the same scorecards for every feed we track in that group, on one free page.

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.

Catalina Express 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/catalina-express/2026-09-13.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-09-13. 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.