GTFS Scorecard
← All agencies

Feed status · checked 2026-08-01

NYC Ferry

Based on the feed this agency publishes

Service mode Bus + Ferry

87.9 / 100

down 0.8 since 2026-07-31

Catalogued in New York.

Covers 517 daysAccessibility gaps

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 72 minutes ago; last changed 3 days ago.

Measured 4 of 4 score categories from the agency's own feed.

How we measured this

Confidence in this measurement: high.

  • All four score categories were measured this run.
  • Realtime was sampled in one bounded window of 6 snapshots.
  • The feed was downloaded from the agency's own URL.

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

Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.Likely your export tool

723 of 723 trips don't say whether the vehicle is wheelchair accessible. Even with accessible stops, riders need to know the transit vehicle itself can take them.

⏱ A default or per-trip field in your export.worth about +15 points in its category

Fix 02

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

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

⏱ Varies.worth about +8 points in its category

Fix 03

Add feed_contact_email or feed_contact_url to feed_info.txt.Likely your export tool

feed_info.txt lists no contact email and no contact URL. Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.

⏱ One field, set once in export settings.worth about +4 points in its category

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
723 of 723 trips don't say whether the vehicle is wheelchair accessible.
Next action
Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip.
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. Set wheelchair_accessible on every trip. If every vehicle is accessible, this may be one default; otherwise use the value for each trip. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    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. See this feed's finding-clearance log.

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

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    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. See this feed's finding-clearance log.

  3. Add feed_contact_email or feed_contact_url to feed_info.txt. · Read the fix guide

    Make the change. Make this change in whatever tool produces your feed, then re-export.

    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. See this feed's finding-clearance log.

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 517 days.
Published accessibility data
Accessibility information is stated for 98% of stops and 0% of trips. This measures published data, not whether stops or vehicles are physically usable.
Fare information
Fare information is published using GTFS Fares v1.
Realtime information
Live-arrival data covered 91.3% of scheduled trips in the sampled window.

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
7 routes · 563 trips
Terminal structure
25 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
100% of ferry boarding locations publish a value; 100% of all ferry boarding locations explicitly say allowed (25 of 25). Unstated values remain unknown. Unknown: none of the 563 ferry trips publish wheelchair_accessible. This reports published values, not verified physical usability.
Bicycles
Unknown: none of the 563 ferry trips publish bikes_allowed.
Cars
Unknown: none of the 563 ferry trips publish cars_allowed.
Fares
Whole feed: applied fare data is published using GTFS Fares v1.
Realtime
Whole feed: configured GTFS-Realtime endpoints are Trip Updates, Service Alerts.

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

You may not control the GTFS export yourself. Copy this and send it to whoever runs your scheduling software export. It names each fix with the validator notice and a guide link.

Score by category

Correctness84.0 / 100

The MobilityData validator flagged 3 kinds of issue across 565 instances (0 error, 565 warning, 0 informational).

Freshness100.0 / 100

Service data covers the next 517 days.

Rider experience77.0 / 100

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

Accessibility61.3 / 100

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

2 accessibility depth signals

  • 7 route badge(s) pair a color and text color below the WCAG 4.5:1 contrast bar (AS, ER, GI, RES, RR, and more).

    Consider: Adjust route_color or route_text_color so each pair clears 4.5:1. Often switching the text between black and white is enough.

  • 34 stop name(s) use abbreviations or symbols a screen reader may mispronounce, with no spoken form set ("Atlantic Ave/BBP Pier 6", "Beach Channel Dr/Beach 108th Street", "Dumbo/Fulton Ferry", and more).

    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.

FaresLegacy fares

Fares are applied to trips.

Realtime quality96.4 / 100

Sampled 6 times: 2 of 2 configured feeds healthy; 91.3% of scheduled trips had live predictions; predictions ran a median of 154s ahead of schedule.

Routes and stops

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

This feed has 50 stops.

Skip to route and stop data

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

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

  • AS (orange)
  • ER (teal)
  • GI (gray)
  • RES (teal)
  • RR (pink)
  • RS (purple)
  • RWS (teal)
  • SB (yellow)
  • SG (red)
Routes in NYC Ferry's feed
RouteTypeLine color
AS AstoriaFerryorange
ER East RiverFerryteal
GI Governors Island ShuttleFerrygray
RES Rockaway EastBusteal
RR Rockaway RocketFerrypink
RS Rockaway-SoundviewFerrypurple
RWS Rockaway WestBusteal
SB South BrooklynFerryyellow
SG St. GeorgeFerryred
List every stop
  • Rockaway Beach Boulevard & Beach 67th Street
  • Rockaway Beach Boulevard & Beach 96th Street
  • Rockaway Beach Boulevard & Beach 77th Street
  • Atlantic Ave/BBP Pier 6
  • Gov. Island/Yankee Pier
  • Soundview
  • East 90th St
  • Stuyvesant Cove
  • Corlears Hook
  • Sunset Park/BAT
  • Brooklyn Navy Yard
  • Battery Park City/Vesey St.
  • St. George
  • Midtown West 39th St-Pier 79
  • Ferry Point Park
  • Rockaway Beach Boulevard & Beach 102nd Street
  • Rockaway Beach Boulevard & Beach 118th Street
  • Rockaway Beach Boulevard & Beach 96th Street
  • Rockaway Beach Boulevard & Beach 79th Street
  • Rockaway Beach Boulevard & Beach 67th Street
  • Beach Channel Dr/Beach 108th Street
  • East 34th Street
  • Greenpoint
  • North Williamsburg
  • Dumbo/Fulton Ferry
  • Bay Ridge
  • Red Hook/Atlantic Basin
  • Roosevelt Island
  • Beach Channel Dr/Beach 54th Street
  • Rockaway Beach Boulevard & Beach 86th Street
  • Hunters Point South
  • Rockaway Beach Boulevard & Beach 86th Street
  • Beach Channel Dr/Beach 54th Street
  • Beach Channel Dr/Beach 41st Street
  • Rockaway Point Boulevard & Beach 169th Street
  • Jacob Riis Park Road/Bath House
  • Rockaway Beach Boulevard & Beach 149th Street
  • Rockaway Beach Boulevard & Beach 135th Street
  • Rockaway Beach Boulevard & Beach 127th Street
  • Rockaway Beach Boulevard & Beach 118th Street
  • Rockaway Beach Boulevard & Beach 127th Street
  • Rockaway Beach Boulevard & Beach 135th Street
  • Rockaway Beach Boulevard & Beach 149th Street
  • Beach Channel Dr/Beach 41st Street
  • Beach Channel Dr/Beach 36th Street
  • South Williamsburg
  • Wall St/Pier 11
  • Rockaway
  • Astoria
  • Long Island City

Over time

Overall score across the last 4 checks — down 0.8 since 2026-07-31.

2026-07-25: 88.72026-07-30: 88.72026-07-31: 88.72026-08-01: 87.9
Show the numbers
CheckScoreChange
2026-07-2588.7 first check
2026-07-3088.7 no change
2026-07-3188.7 no change
2026-08-0187.9 down 0.8

What changed since your last check

  • Correctness no change
  • Freshness no change
  • Rider experience no change
  • Realtime quality down 3.6

What changed in this feed

Overall score fell 0.8 points since 2026-07-31.

Same feed file as 2026-07-31; the published zip did not change.

New since 2026-07-31 (1 finding)

  • Warning2 instances

    2 of 23 trips scheduled during the sampling window had no live predictions.

    Finding code: scorecard_rt_trip_coverage · Read the fix guide · See GTFS-Realtime reference

Subscribe to this feed’s changes (Atom) to hear about grade drops in a reader, with no sign-up.

Everything we checked

7 findings, ordered by severity.

Show every finding
  • Warning723 instances

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

    Even with accessible stops, riders need to know the transit vehicle 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 · See GTFS Schedule reference

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

  • Warning2 instances

    2 of 23 trips scheduled during the sampling window had no live predictions.

    Riders on those trips get schedule data dressed up as realtime. Caltrans expects every operating trip in TripUpdates.

    Fix: Check with your AVL vendor that every vehicle assignment flows into TripUpdates, including school-day and tripper runs. (A vendor data-mapping question.)

    Finding code: scorecard_rt_trip_coverage · Read the fix guide · See GTFS-Realtime reference

  • Warning1 instance

    feed_info.txt lists no contact email and no contact URL.

    Without a contact, apps like Google Maps can't reach you when they find a problem in the feed.

    Fix: Add feed_contact_email or feed_contact_url to feed_info.txt. (One field, set once in export settings.)

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

  • Warning1 instance

    Some route colors don't contrast with their text color.

    Route badges get hard to read, most of all for riders with low vision.

    Fix: Pick a darker/lighter route_text_color for the flagged routes. (One field per route.)

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

  • Warning1 instance

    1 of 50 stops 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 stop. A field survey can start with the busiest stops. (A column in stops.txt; your scheduling software likely has it.)

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

  • Info1 instance

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

    Trip-planning apps and regional data coordinators have nobody to email when they spot a problem with your feed, so problems linger.

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

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

NTD GTFS readiness Ready

Published at a public URL, valid, current, and identified with agency_id: the four feed checks for RY2026 all hold here. Only your own D-10 and P-50 filings make that official; this is a heads-up, not a determination.

Published Ready
Published at a public URL.
Valid Ready
Passes validation with no errors.
Current Ready
Service data covers the next 517 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 723 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. States wheelchair access on 98% of stops and 0% of trips; the mark needs 90% of each.

Valid Met
Passes validation with no errors.
Current Met
Service data covers the next 517 days.
Accessible Not yet
States wheelchair access on 98% of stops 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 stop and trip is wheelchair accessible.

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

Realtime reliability

The realtime feed responded on 100.0% of 200 checks over the last 34 days, with 3s median lag.

Sampled on a schedule between full scores, so this tracks uptime and freshness over time rather than at a single moment.

Live predictions vs schedule

Arrival predictions ran a median 154s early versus the schedule, and stayed within 632s nine times in ten. They were on time (about a minute early to five late) 20.0% of the time.

From the last full realtime sample: how far live arrival predictions sat from the schedule, and whether vehicle positions fell on the route. These feed the realtime score; they change no other category.

Clears the Google and Apple Maps four-week coverage bar. This feed has 517 days of service ahead, clearing the four-week (28-day) window Maps asks for. No validator errors either, so riders keep seeing this agency in their trip planners; warnings lower the grade here but do not remove a feed from Maps.

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 84 / 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 77 / 100
GTFS Best Practices for rider-facing fields. MobilityData grading covers stop names and headsigns.
Realtime quality 96 / 100
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.

NYC Ferry GTFS data quality grade: B

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/nyc-ferry/2026-08-01.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-08-01. 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.