GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-05T14:50:46Z,
for the dataset file:///shared/vineyard.zip. No country code was provided.

Summary

Agencies included

Vineyard Fast Ferry
- website: https://www.vineyardfastferry.com/
- phone number: (401)295-4040
- email: Not provided

Feed Info

Publisher Name:
Busmaps.com: Publisher URL:
https://busmaps.com: Feed Email:
alex@busmaps.com: Feed Language:
English: Feed Start Date:
2025-09-11: Feed End Date:
2026-05-01: Service Window:
2025-09-11 to 2026-05-01 (?) The range of service dates covered by the feed, based on trips with an associated service_id in calendar.txt and/or calendar_dates.txt

Files included

agency.txt
calendar.txt
calendar_dates.txt
fare_attributes.txt
fare_rules.txt
feed_info.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 1
Routes: 2
Shapes: 2
Stops: 2
Trips: 10

GTFS Features included (?) GTFS features provide a standardized vocabulary to define and describe features that are officially adopted in GTFS.

Shapes Feed Information Fares V1 Headsigns Stops Wheelchair Accessibility Trips Wheelchair Accessibility Bike Allowed Location Types Continuous Stops

Specification Compliance report

8 notices reported (0 errors, 8 warnings, 0 infos)

Notice Code

Severity

Total

expired_calendar

WARNING

expired_calendar

Dataset should not contain date ranges for services that have already expired.

This warning takes into account the calendar_dates.txt file as well as the calendar.txt file.

You can see more about this notice here.

csvRowNumber (?) The row of the faulty record.	serviceId (?) The service id of the faulty record.
3	"340-Green-Calendar-(All-days-of-week)"
4	"340-merged_7606c321f32de97828ce"
5	"340-Pink-Calendar-(All-days-of-week)"

missing_bike_allowance

WARNING

missing_bike_allowance

Ferry trips should include bike allowance information.

All ferry trips should have a valid value in the bikes_allowed field in trips.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	routeId (?) The faulty record's route id.	tripId (?) The faulty record's trip id.
2	"340-2099"	"340-t_1047619_b_84374_tn_0"
4	"340-2099"	"340-t_1047618_b_84374_tn_0"
6	"340-2099"	"340-t_1047623_b_84372_tn_0"
8	"340-2099"	"340-t_1351076_b_84346_tn_0"
10	"340-2099"	"340-t_1351075_b_84346_tn_0"