Feed status · checked 2026-11-21

Casco Bay Lines

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

Service mode Ferry

78.2 / 100

unchanged since 2026-11-20

Cataloged in Maine.

Covers 180 daysRealtime not yet published

The grade is not a count of validator errors. It also weighs freshness and rider information. How the grade works

Checked 2026-11-08: the feed URL on file had stopped working, so this record now tracks gtfs.remix.com, the address the Mobility Database lists for the record that replaced this one. The agency name and service area in that file match this record. Grades dated before this change came from an older Mobility Database mirror copy.

Top things to fix

Fix 01

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.

Trip distance exceeds shape distance (flagged by the MobilityData validator). See the linked rule for what this affects.

This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

⏱ Varies.worth about +24 points in its category

Fix 02

Re-generate shape_dist_traveled on export so stop and shape distances use the same units.Likely your export tool

On some trips the stop distances run a little past the end of the route line. The stop and shape distance values don't quite line up, so any math that uses them can drift.

This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

⏱ Usually an export-tool fix, not hand editing.worth about +8 points in its category

Fix 03

Remove past service periods the next time you export the feed.Likely your export tool

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.

This is a validator notice, and the validator decides what each instance covers, so no share of the network can be read from it here.

⏱ One setting in most export tools.worth about +6 points in its category

Riders and need behind these fixes

  • This feed carries no National Transit Database ID, so annual rider-trips are not known for it.
  • Maine as a whole measures moderate on transit need. That is a statewide reading, not one for this feed's service area. Source: US Census ACS 5-year 2022, statewide overlay, as of 2026-11-02.

These describe this feed only. They do not rank agencies, and they do not change the grade or the order of the fixes.

This feed is exported from Remix. The change happens in your Remix workspace; once your planners update the data there, the published export picks it up.

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.

Finding
Fix 01 in Top things to fix: its feed evidence and the requested change.
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. Fix 01

    Make the change. This feed is exported from Remix. The change happens in your Remix workspace; once your planners update the data there, the published export picks it up.

    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. Fix 02 · Read the fix guide for trip_distance_exceeds_shape_distance_below_threshold

    Make the change. This feed is exported from Remix. The change happens in your Remix workspace; once your planners update the data there, the published export picks it up.

    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. Fix 03 · Read the fix guide for expired_calendar

    Make the change. This feed is exported from Remix. The change happens in your Remix workspace; once your planners update the data there, the published export picks it up.

    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 is in 180 days.
Published accessibility data
Accessibility information is stated for 90% of terminals and 99.7% of trips. This measures published data, not whether terminals or vessels are physically usable.
Fare information
Fare information is published using GTFS Fares v1.
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 labeled as whole-feed. Unknown values are not treated as no.

Ferry service
3 routes · 1,349 trips
Terminal structure
9 ferry boarding locations; 2 link to 1 referenced station record.
Terminal access
Unknown: none of the 2 eligible child terminal locations publish stop_access.
Published accessibility
100% of ferry boarding locations publish a value; 100% of all ferry boarding locations explicitly say allowed (9 of 9). Unstated values remain unknown. 99.7% of ferry trips publish a value; 99.7% of all ferry trips explicitly say allowed (1,345 of 1,349). Unstated values remain unknown. This reports published values, not verified physical usability.
Bicycles
99.7% of ferry trips publish a value; 99.7% of all ferry trips explicitly say allowed (1,345 of 1,349). Unstated values remain unknown.
Cars
Unknown: none of the 1,349 ferry trips publish cars_allowed.
Fares
Whole feed: applied fare data is published using GTFS Fares v1.
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 exported from Remix. If your planners work in Remix, the change happens in your own workspace; otherwise forward this to whoever maintains your Remix data. Each fix names the validator notice and a guide link.

About this feed

Looking for times or routes? This page checks the data file that trip planners use. For schedules, use the agency's own website or a trip planner.

Casco Bay Lines’s published feed lists 3 ferry routes, 1,349 scheduled trips and 10 stops. Its service dates run from 2026-05-22 through 2027-05-20. The published file last changed on 2026-11-09.

Score by category

Correctness52.0 / 100

The MobilityData validator flagged 8 kinds of issue across 1623 instances (137 error, 133 warning, 1353 informational).

Freshness100.0 / 100

Service data covers the next 180 days.

Rider experience97.5 / 100

90% of terminals state wheelchair accessibility (90% marked accessible, 0% marked not accessible). This measures what the feed publishes, not whether a terminal is physically usable. Fare data is published.

Accessibility93.6 / 100

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

1 accessibility depth signal

  • This feed models stations or entrances but has no pathways.txt and levels.txt.

    Consider: Add pathways.txt connecting entrances, platforms, and elevators, and levels.txt for each floor, so the step-free route is described.

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.

FaresLegacy fares

Fares are applied to trips.

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

  • DB (purple)
  • IB (teal)
  • PK (red)
Routes in Casco Bay Lines's feed
RouteTypeLine color
DB Down Bay IslandsFerrypurple
IB Inner Bay IslandsFerryteal
PK Peaks IslandFerryred
List every terminal
  • Casco Bay Lines Terminal
  • Diamond Cove
  • Chebeague Island
  • Cliff Island
  • Gates 2, 3, or 4
  • Gate 5
  • Peaks Island
  • Little Diamond Island
  • Great Diamond Island
  • Long Island

Over time

Overall score across the last 13 checks — unchanged since 2026-11-20.

2026-11-09: 78.22026-11-10: 78.22026-11-11: 78.22026-11-12: 78.22026-11-13: 78.22026-11-14: 78.22026-11-15: 78.22026-11-16: 78.22026-11-17: 78.22026-11-18: 78.22026-11-19: 78.22026-11-20: 78.22026-11-21: 78.2
Show the numbers
Overall score by check, with the change from the previous check
CheckScoreChange
2026-11-0978.2 first check
2026-11-1078.2 no change
2026-11-1178.2 no change
2026-11-1278.2 no change
2026-11-1378.2 no change
2026-11-1478.2 no change
2026-11-1578.2 no change
2026-11-1678.2 no change
2026-11-1778.2 no change
2026-11-1878.2 no change
2026-11-1978.2 no change
2026-11-2078.2 no change
2026-11-2178.2 no change

What changed since your last check

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

Feed history

Every check on record for this feed, grouped by the published file, newest first. A new file means the published zip changed. Grades from earlier rubric versions are shown with their rubric and are not comparable with today’s grade or the trend above.

Feed history by published file
CheckedPublished fileService dates throughGrade at the time
2026-11-09 to 2026-11-21 (13 checks)0c8766f80b172027-05-20Current rubric: see the trend above
2026-10-02 to 2026-11-06 (35 checks)bddc517ac4fd2026-06-12F, 52.8 under rubric 1.4, an earlier scoring contract; not comparable with today’s grade
2026-09-09 to 2026-10-01 (19 checks)bddc517ac4fd2026-06-12F, 52.8 under rubric 1.3, an earlier scoring contract; not comparable with today’s grade
2026-07-13 to 2026-09-08 (56 checks)b52b0e566c902022-09-05F, 46.6 under rubric 1.2, an earlier scoring contract; not comparable with today’s grade
2026-06-19 to 2026-07-12 (24 checks)b52b0e566c902022-09-05F, 46.6 under rubric 1.1, an earlier scoring contract; not comparable with today’s grade

Everything we checked

11 findings, ordered by severity.

Show every finding
  • Error137 instances

    Trip distance exceeds shape distance (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: trip_distance_exceeds_shape_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning108 instances

    On some trips the stop distances run a little past the end of the route line.

    The stop and shape distance values don't quite line up, so any math that uses them can drift.

    Fix: Re-generate shape_dist_traveled on export so stop and shape distances use the same units. (Usually an export-tool fix, not hand editing.)

    Finding code: trip_distance_exceeds_shape_distance_below_threshold · Read the fix guide for trip_distance_exceeds_shape_distance_below_threshold · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning18 instances

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

    Finding code: expired_calendar · Read the fix guide for expired_calendar · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

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

    Finding code: missing_bike_allowance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning4 instances

    4 of 1349 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 (opens the GTFS Schedule reference on an external site)

  • Warning3 instances

    Some terminals sit far from the route line, going by the feed's own distance values.

    Trip planners may draw the route down the wrong path or point riders to the wrong terminal.

    Fix: Check the flagged terminals' shape_dist_traveled against the route shape, and re-generate it on export if they disagree. (Usually an export-tool fix, not hand editing.)

    Finding code: stop_too_far_from_shape_using_user_distance · Read the fix guide for stop_too_far_from_shape_using_user_distance · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

  • Warning1 instance

    1 of 10 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 (opens the GTFS Schedule reference on an external site)

  • Warning1 instance

    This feed models stations or entrances but has no pathways.txt.

    Trip planners can't guide riders through the station, and there is no step-free route information for wheelchair users.

    Fix: Add pathways.txt to link entrances, platforms, and elevators. Give each one a level. (Worth it for multi-level or large stations; flat stops don't need it.)

    Finding code: scorecard_station_no_pathways · Read the fix guide for scorecard_station_no_pathways · See GTFS Schedule reference (opens the GTFS Schedule reference on an external site)

  • Info1349 instances

    Unsorted stop times (flagged by the MobilityData validator).

    See the linked rule for what this affects.

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

    Finding code: unsorted_stop_times · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

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

    Finding code: unknown_column · Read the fix guide for unknown_column · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

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

    Finding code: unknown_file · Read the fix guide for unknown_file · See MobilityData GTFS Validator rules (opens the validator rules on an external site)

How we measured this

Checked for changes 18 hours ago; last changed 12 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.

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.5, validator 8.0.1.

NTD GTFS readiness Needs attention

This feed is close to NTD-ready. 1 validator error to resolve.

Published Ready
Published at a public URL.
Valid Needs attention
1 validator error to resolve.
Current Ready
Service data covers the next 180 days.
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 1349 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

One requirement remains for this feed to earn the conformance mark. 1 validator error to resolve.

Valid Not yet
1 validator error to resolve.
Current Met
Service data covers the next 180 days.
Accessible Met
States wheelchair access on 90% of terminals and 100% of trips.

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 has 179 days of service ahead, clearing the four-week (28-day) window Maps asks for. The feed also carries 137 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.

Correctness 52 / 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 100 / 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 98 / 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 Maine portfolio: the same scorecards for every feed we track in that group, on one free page.

Similar feeds in Maine

Other scorecards in Maine, starting with the same kind of service at a similar size. Listed for comparison, not ranked.

Show your grade

Put this badge on your agency site or feed README. It updates after each completed scoring check, shows the date of that check, and links back to this scorecard. When there is no current score it says so instead of showing an old one.

Casco Bay Lines: GTFS feed quality grade C, 78.2 of 100, checked 2026-11-21. GTFS Scorecard.

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/casco-bay-lines/2026-11-21.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-11-21. 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.