GTFS Schedule Validation Report

duplicate_key

Duplicated entity.

The values of the given key and rows are duplicates.

You can see more about this notice here.

filename (?) The name of the faulty file	oldCsvRowNumber (?) The row of the first occurrence.	newCsvRowNumber (?) The row of the other occurrence.	fieldName1 (?) Composite key's first field name.	fieldValue1 (?) Composite key's first value.
"fare_rules.txt"	2	3	"fare_id,route_id"	"1192-200,1192-101001"
"fare_rules.txt"	8	10	"fare_id,route_id"	"1192-200,1192-102002"

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"

duplicate_route_name

Two distinct routes have either the same route_short_name, the same route_long_name, or the same combination of route_short_name and route_long_name.

All routes of the same route_type with the same agency_id should have unique combinations of route_short_name and route_long_name.

Note that there may be valid cases where routes have the same short and long name, e.g., if they serve different areas. However, different directions must be modeled as the same route.

Example of bad data:

route_id	route_short_name	route_long_name
route1	U1	Southern
route2	U1	Southern

You can see more about this notice here.

csvRowNumber1 (?) The row number of the first occurrence.	routeId1 (?) The id of the the first occurrence.	csvRowNumber2 (?) The row number of the other occurrence.	routeId2 (?) The id of the the other occurrence.	routeShortName (?) Common `routes.route_short_name`.	routeLongName (?) Common `routes.route_long_name`.	routeTypeValue (?) Common `routes.route_type`.	agencyId (?) Common `routes.agency_id`.
2	"1192-101001"	3	"1192-101003"	"焼津循環線 ゆりかもめ"	""	3	"1192-1000020222127"
2	"1192-101001"	5	"1192-101005"	"焼津循環線 ゆりかもめ"	""	3	"1192-1000020222127"
6	"1192-102001"	7	"1192-102002"	"焼津循環線 さつき"	""	3	"1192-1000020222127"
6	"1192-102001"	8	"1192-102003"	"焼津循環線 さつき"	""	3	"1192-1000020222127"
6	"1192-102001"	9	"1192-102005"	"焼津循環線 さつき"	""	3	"1192-1000020222127"
11	"1192-201001"	12	"1192-201002"	""	"大井川焼津線 焼津駅前行き"	3	"1192-1000020222127"
13	"1192-202001"	14	"1192-202002"	""	"大井川焼津線 大井川庁舎行き"	3	"1192-1000020222127"

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	"1192-土日祝（大井川焼津線）"
3	"1192-土日祝（焼津循環線）"
4	"1192-平日（焼津循環線）"

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	"20251212"	"20250331"	"20251219"

missing_recommended_field

A recommended field is missing.

The given field has no value in some input row, even though values are recommended.

You can see more about this notice here.

filename (?) The name of the faulty file.	csvRowNumber (?) The row of the faulty record.	fieldName (?) The name of the missing field.
"fare_attributes.txt"	2	"agency_id"
"fare_attributes.txt"	3	"agency_id"

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_short_name"	"焼津循環線 ゆりかもめ"	2
"routes.txt"	"route_short_name"	"焼津循環線 ゆりかもめ"	3
"routes.txt"	"route_long_name"	"焼津循環線 ゆりかもめ（日本坂pa～林叟院入口 フリー降車区間）"	4
"routes.txt"	"route_short_name"	"焼津循環線 ゆりかもめ"	5
"routes.txt"	"route_short_name"	"焼津循環線 さつき"	6
"routes.txt"	"route_short_name"	"焼津循環線 さつき"	7
"routes.txt"	"route_short_name"	"焼津循環線 さつき"	8
"routes.txt"	"route_short_name"	"焼津循環線 さつき"	9
"routes.txt"	"route_long_name"	"焼津循環線 さつき（林叟院入口～日本坂pa フリー降車区間）"	10
"routes.txt"	"route_long_name"	"大井川焼津線 焼津駅前行き"	11
"routes.txt"	"route_long_name"	"大井川焼津線 焼津駅前行き"	12
"routes.txt"	"route_long_name"	"大井川焼津線 大井川庁舎行き"	13
"routes.txt"	"route_long_name"	"大井川焼津線 大井川庁舎行き"	14
"stops.txt"	"stop_name"	"焼津駅前（４番のりば）"	2
"stops.txt"	"stop_name"	"焼津駅前（１番のりば）"	3

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 2897 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.txt"	2	"service_id"	"1192-土日祝（大井川焼津線）"
"calendar.txt"	3	"service_id"	"1192-土日祝（焼津循環線）"
"calendar.txt"	4	"service_id"	"1192-平日（焼津循環線）"
"calendar_dates.txt"	2	"service_id"	"1192-土日祝（大井川焼津線）"
"calendar_dates.txt"	3	"service_id"	"1192-土日祝（大井川焼津線）"
"calendar_dates.txt"	4	"service_id"	"1192-土日祝（大井川焼津線）"
"calendar_dates.txt"	5	"service_id"	"1192-土日祝（大井川焼津線）"
"calendar_dates.txt"	6	"service_id"	"1192-土日祝（大井川焼津線）"
"calendar_dates.txt"	7	"service_id"	"1192-土日祝（大井川焼津線）"
"calendar_dates.txt"	8	"service_id"	"1192-土日祝（大井川焼津線）"
"calendar_dates.txt"	9	"service_id"	"1192-土日祝（大井川焼津線）"
"calendar_dates.txt"	10	"service_id"	"1192-土日祝（大井川焼津線）"
"calendar_dates.txt"	11	"service_id"	"1192-土日祝（大井川焼津線）"
"calendar_dates.txt"	12	"service_id"	"1192-土日祝（大井川焼津線）"
"calendar_dates.txt"	13	"service_id"	"1192-土日祝（大井川焼津線）"
"calendar_dates.txt"	14	"service_id"	"1192-土日祝（大井川焼津線）"
"calendar_dates.txt"	15	"service_id"	"1192-土日祝（大井川焼津線）"
"calendar_dates.txt"	16	"service_id"	"1192-土日祝（大井川焼津線）"
"calendar_dates.txt"	17	"service_id"	"1192-土日祝（大井川焼津線）"
"calendar_dates.txt"	18	"service_id"	"1192-土日祝（大井川焼津線）"
"calendar_dates.txt"	19	"service_id"	"1192-土日祝（焼津循環線）"
"calendar_dates.txt"	20	"service_id"	"1192-土日祝（焼津循環線）"
"calendar_dates.txt"	21	"service_id"	"1192-土日祝（焼津循環線）"
"calendar_dates.txt"	22	"service_id"	"1192-土日祝（焼津循環線）"
"calendar_dates.txt"	23	"service_id"	"1192-土日祝（焼津循環線）"
"calendar_dates.txt"	24	"service_id"	"1192-土日祝（焼津循環線）"
"calendar_dates.txt"	25	"service_id"	"1192-土日祝（焼津循環線）"
"calendar_dates.txt"	26	"service_id"	"1192-土日祝（焼津循環線）"
"calendar_dates.txt"	27	"service_id"	"1192-土日祝（焼津循環線）"
"calendar_dates.txt"	28	"service_id"	"1192-土日祝（焼津循環線）"
"calendar_dates.txt"	29	"service_id"	"1192-土日祝（焼津循環線）"
"calendar_dates.txt"	30	"service_id"	"1192-土日祝（焼津循環線）"
"calendar_dates.txt"	31	"service_id"	"1192-土日祝（焼津循環線）"
"calendar_dates.txt"	32	"service_id"	"1192-土日祝（焼津循環線）"
"calendar_dates.txt"	33	"service_id"	"1192-平日（焼津循環線）"
"calendar_dates.txt"	34	"service_id"	"1192-平日（焼津循環線）"
"calendar_dates.txt"	35	"service_id"	"1192-平日（焼津循環線）"
"calendar_dates.txt"	36	"service_id"	"1192-平日（焼津循環線）"
"calendar_dates.txt"	37	"service_id"	"1192-平日（焼津循環線）"
"calendar_dates.txt"	38	"service_id"	"1192-平日（焼津循環線）"
"calendar_dates.txt"	39	"service_id"	"1192-平日（焼津循環線）"
"calendar_dates.txt"	40	"service_id"	"1192-平日（焼津循環線）"
"calendar_dates.txt"	41	"service_id"	"1192-平日（焼津循環線）"
"calendar_dates.txt"	42	"service_id"	"1192-平日（焼津循環線）"
"calendar_dates.txt"	43	"service_id"	"1192-平日（焼津循環線）"
"calendar_dates.txt"	44	"service_id"	"1192-平日（焼津循環線）"
"calendar_dates.txt"	45	"service_id"	"1192-平日（焼津循環線）"
"calendar_dates.txt"	46	"service_id"	"1192-平日（焼津循環線）"
"calendar_dates.txt"	47	"service_id"	"1192-平日（焼津循環線）"
"calendar_dates.txt"	48	"service_id"	"1192-平日（焼津循環線）"

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.
"20251212"	"20240401"	"20250331"

platform_without_parent_station

A platform has no parent_station field set.

This is different from location_without_parent_station since it is less severe.

You can see more about this notice here.

csvRowNumber (?) Row number of the faulty record.	stopId (?) The id of the faulty record.	stopName (?) The stop name of the faulty record.
2	"1192-101_01"	"焼津駅前（４番のりば）"
3	"1192-101_02"	"焼津駅前（１番のりば）"
31	"1192-116_01"	"焼津市立病院前"
32	"1192-116_02"	"焼津市立病院前"

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.
"translations.txt"	"trans_id"	1
"translations.txt"	"lang"	2