NYC Ferry

What changed since the last check

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

Top three things to fix

1. Check the vehicle positions endpoint with your AVL vendor; it should return a fresh GTFS-Realtime protobuf on every request.

   The vehicle positions realtime feed failed during sampling. When this feed is down, riders see scheduled times presented as if they were live.

   Effort: Usually a vendor support ticket.

2. Set wheelchair_accessible on every trip (most small-agency fleets are 100% accessible, so this is often a single default).

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

   Effort: Often one default setting in your export.

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

   Effort: Varies.

NTD GTFS readiness: Ready

This feed looks ready for your NTD certification: published at a public URL, valid, and current. The official check is still your D-10 certification.

Published Ready

Published at a public URL.

Valid Ready

Passes validation with no errors.

Current Ready

Service data covers the next 549 days.

agency_id and NTD ID: Not checked yet. Setting your GTFS agency_id to your five-digit NTD ID is an optional way to line a feed up with its National Transit Database record. FTA links the two on your P-50 form, so it is not a required feed change. We don't have your NTD ID on file, so this is not checked yet.

Key facts

Feed URL

http://nycferry.connexionz.net/rtt/public/utility/gtfs.aspx

Last checked

2026-07-11

Service window

538 days of service data remain. Last service date 2027-12-31.

Feed version

20260629