GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-05T19:07:49Z,
for the dataset file:///shared/sakataferryoffice.zip. No country code was provided.

Notice Code

Severity

Total

missing_required_column

ERROR

missing_required_column

A required column is missing in the input file.

You can see more about this notice here.

filename (?) The name of the faulty file.	fieldName (?) The name of the missing column.
"translations.txt"	"field_name"
"translations.txt"	"language"
"translations.txt"	"table_name"

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.
2	"令和4年度1航海"
306	"令和4年度2航海"
365	"令和4年度2航海（5月28日）"
366	"令和4年度3航海"

feed_expiration_date7_days

WARNING

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	currentDate (?) Current date (YYYYMMDD format).	feedEndDate (?) Feed end date (YYYYMMDD format).	suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2	"20251205"	"20230331"	"20251212"

missing_timepoint_value

WARNING

missing_timepoint_value

stop_times.timepoint value is missing for a record.

When at least one of stop_times.arrival_time or stop_times.departure_time are provided, stop_times.timepoint should be defined

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	tripId (?) The faulty record's `stop_times.trip_id`.	stopSequence (?) The faulty record's `stop_times.stop_sequence`.
2	"[001]とびしま：酒田発1便令和4年度1航海"	0
3	"[001]とびしま：酒田発1便令和4年度1航海"	1
4	"[002]とびしま：飛島発1便令和4年度1航海"	0
5	"[002]とびしま：飛島発1便令和4年度1航海"	1
6	"[003]とびしま：酒田発1便令和4年度2航海"	0
7	"[003]とびしま：酒田発1便令和4年度2航海"	1
8	"[004]とびしま：飛島発1便令和4年度2航海"	0
9	"[004]とびしま：飛島発1便令和4年度2航海"	1
10	"[005]とびしま：酒田発2便令和4年度2航海"	0
11	"[005]とびしま：酒田発2便令和4年度2航海"	1
12	"[006]とびしま：飛島発2便令和4年度2航海"	0
13	"[006]とびしま：飛島発2便令和4年度2航海"	1
14	"[007]とびしま：酒田発1便令和4年度2航海（5月28日）"	0
15	"[007]とびしま：酒田発1便令和4年度2航海（5月28日）"	1
16	"[008]とびしま：酒田発1便令和4年度3航海"	0
17	"[008]とびしま：酒田発1便令和4年度3航海"	1
18	"[009]とびしま：飛島発1便令和4年度3航海"	0
19	"[009]とびしま：飛島発1便令和4年度3航海"	1
20	"[010]とびしま：酒田発2便令和4年度3航海"	0
21	"[010]とびしま：酒田発2便令和4年度3航海"	1
22	"[011]とびしま：飛島発2便令和4年度3航海"	0
23	"[011]とびしま：飛島発2便令和4年度3航海"	1
24	"[012]とびしま：酒田発3便令和4年度3航海"	0
25	"[012]とびしま：酒田発3便令和4年度3航海"	1
26	"[013]とびしま：飛島発3便令和4年度3航海"	0
27	"[013]とびしま：飛島発3便令和4年度3航海"	1

mixed_case_recommended_field

WARNING

mixed_case_recommended_field

This field has customer-facing text and should use Mixed Case (should contain upper and lower case letters).

This field contains customer-facing text and should use Mixed Case (upper and lower case letters) to ensure good readability when displayed to riders. Avoid the use of abbreviations throughout the feed (e.g. St. for Street) unless a location is called by its abbreviated name (e.g. “JFK Airport”). Abbreviations may be problematic for accessibility by screen reader software and voice user interfaces.

Good examples:
`Field Text`	`Dataset`
"Schwerin, Hauptbahnhof"	Verkehrsverbund Berlin-Brandenburg
"Red Hook/Atlantic Basin"	NYC Ferry
"Campo Grande Norte"	Carris

Bad examples:
`Field Text`
"GALLERIA MALL"
"3427 GG 17"
"21 Clark Rd Est"

You can see more about this notice here.

filename (?) Name of the faulty file.	fieldName (?) Name of the faulty field.	fieldValue (?) Faulty value.	csvRowNumber (?) The row number of the faulty record.
"routes.txt"	"route_long_name"	"酒田～飛島"	2
"stops.txt"	"stop_name"	"勝浦港（飛島）"	3
"trips.txt"	"trip_headsign"	"勝浦港（飛島）"	2
"trips.txt"	"trip_short_name"	"とびしま：酒田発1便"	2
"trips.txt"	"trip_short_name"	"とびしま：飛島発1便"	3
"trips.txt"	"trip_headsign"	"勝浦港（飛島）"	4
"trips.txt"	"trip_short_name"	"とびしま：酒田発1便"	4
"trips.txt"	"trip_short_name"	"とびしま：飛島発1便"	5
"trips.txt"	"trip_headsign"	"勝浦港（飛島）"	6
"trips.txt"	"trip_short_name"	"とびしま：酒田発2便"	6
"trips.txt"	"trip_short_name"	"とびしま：飛島発2便"	7
"trips.txt"	"trip_headsign"	"勝浦港（飛島）"	8
"trips.txt"	"trip_short_name"	"とびしま：酒田発1便"	8
"trips.txt"	"trip_headsign"	"勝浦港（飛島）"	9
"trips.txt"	"trip_short_name"	"とびしま：酒田発1便"	9
"trips.txt"	"trip_short_name"	"とびしま：飛島発1便"	10
"trips.txt"	"trip_headsign"	"勝浦港（飛島）"	11
"trips.txt"	"trip_short_name"	"とびしま：酒田発2便"	11
"trips.txt"	"trip_short_name"	"とびしま：飛島発2便"	12
"trips.txt"	"trip_headsign"	"勝浦港（飛島）"	13
"trips.txt"	"trip_short_name"	"とびしま：酒田発3便"	13
"trips.txt"	"trip_short_name"	"とびしま：飛島発3便"	14

non_ascii_or_non_printable_char

WARNING

508

non_ascii_or_non_printable_char

Non ascii or non printable char in ID field.

A value of a field with type ID contains non ASCII or non printable characters. This is not recommended.

You can see more about this notice here.

Only the first 50 of 508 affected records are displayed below.

filename (?) Name of the faulty file.	csvRowNumber (?) Row number of the faulty record.	columnName (?) Name of the column where the error occurred.	fieldValue (?) Faulty value.
"calendar_dates.txt"	2	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	3	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	4	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	5	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	6	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	7	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	8	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	9	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	10	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	11	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	12	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	13	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	14	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	15	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	16	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	17	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	18	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	19	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	20	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	21	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	22	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	23	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	24	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	25	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	26	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	27	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	28	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	29	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	30	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	31	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	32	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	33	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	34	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	35	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	36	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	37	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	38	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	39	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	40	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	41	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	42	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	43	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	44	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	45	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	46	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	47	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	48	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	49	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	50	"service_id"	"令和4年度1航海"
"calendar_dates.txt"	51	"service_id"	"令和4年度1航海"

same_route_and_agency_url

WARNING

same_route_and_agency_url

Same routes.route_url and agency.agency_url.

A route should not have the same routes.route_url as a record from agency.txt.

You can see more about this notice here.

routeCsvRowNumber (?) The row number of the faulty record from `routes.txt`.	routeId (?) The faulty record's id.	agencyName (?) The faulty record's referenced agency name.	routeUrl (?) The duplicate URL value	agencyCsvRowNumber (?) The row number of the faulty record from `agency.txt`.
2	"[01]酒田～飛島"	"酒田市定期航路事業所"	"http://www.city.sakata.lg.jp/sangyo/kotsu/teikisen/index.html"	2

trip_coverage_not_active_for_next7_days

WARNING

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format).	serviceWindowStartDate (?) The start date of the majority service window.	serviceWindowEndDate (?) The end date of the majority service window.
"20251205"	"20220429"	"20220925"

unknown_column

INFO

unknown_column

A column name is unknown.

You can see more about this notice here.

filename (?) The name of the faulty file.	fieldName (?) The name of the unknown column.	index (?) The index of the faulty column.
"fare_attributes.txt"	"cabin_name"	8
"translations.txt"	"trans_id"	1
"translations.txt"	"lang"	2
"trips.txt"	"payload_id"	11
"trips.txt"	"ships_id"	12

unknown_file

INFO

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"payload.txt"
"payload_fare_attributes.txt"
"payload_fare_rules.txt"
"ships.txt"

GTFS Schedule Validation Report

Summary

Agencies included

Feed Info

Files included

Counts

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

Specification Compliance report

575 notices reported (3 errors, 563 warnings, 9 infos)

missing_required_column

expired_calendar

feed_expiration_date7_days

missing_timepoint_value

mixed_case_recommended_field

non_ascii_or_non_printable_char

same_route_and_agency_url

trip_coverage_not_active_for_next7_days

unknown_column

unknown_file