GTFS Schedule Validation Report

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"

new_line_in_value

New line or carriage return in a value in CSV file.

This error is usually found when the CSV file does not close double quotes properly, so the next line is considered as a continuation of the previous line.

Example: the following file was intended to have fields "f11", "f12", "f21", "f22", but it actually parses as two fields: "f11", "f12\nf21,"f22"".

f11,"f12
f21,"f22"

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 faulty field.	fieldValue (?) Faulty value.
"agency.txt"	2	"agency_fare_url"	"https://www.stadtwerke-hof.de/oepnv/tarife/bustarife.html\r"
"agency.txt"	3	"agency_fare_url"	"https://www.stadtwerke-hof.de/oepnv/tarife/bustarife.html\r"

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	"0"
3	"2"
4	"3"
5	"4"
6	"5"
7	"6"
8	"7"
9	"8"
10	"9"
11	"10"

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	"20250422"	"20181216"	"20250429"

leading_or_trailing_whitespaces

The value in CSV file has leading or trailing whitespaces.

This notice is emitted for values protected with double quotes since whitespaces for non-protected values are trimmed automatically by CSV parser.

The validator strips whitespaces from protected values. We do not see any use case when such a whitespace may be needed. On the other hand, some real-world feeds use trailing whitespaces for some values and omit them for the others. This is causing the largest problem when a primary key and a foreign key differ just by a whitespace: it is clear that they are intended to be the same, that is why we always strip whitespaces.

You can see more about this notice here.

filename (?) The name of the faulty file.	csvRowNumber (?) The row of the faulty record.	fieldName (?) Faulty record's field name.	fieldValue (?) Faulty value.
"agency.txt"	2	"agency_fare_url"	"https://www.stadtwerke-hof.de/oepnv/tarife/bustarife.html\r"
"agency.txt"	3	"agency_fare_url"	"https://www.stadtwerke-hof.de/oepnv/tarife/bustarife.html\r"

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2

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"	"10 ALB"	15
"routes.txt"	"route_short_name"	"11 ALB"	16
"routes.txt"	"route_short_name"	"12 ALB"	17
"routes.txt"	"route_short_name"	"13 ALB"	18

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.
"20250422"	"20181001"	"20181214"

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