GTFS Schedule Validation Report

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	"6410248"	9	"6443451"	"720"	"Willingboro, Westampton - Midtown Manhattan"	3	"1761374"
10	"6452372"	11	"6471062"	"200"	"Shore Points - Port Authority"	3	"1761374"
8	"6410260"	12	"6474410"	"302"	"Parkway Express - Port Authority"	3	"1761374"
13	"6474412"	14	"6474476"	"314"	"Parkway Express - Wall Street"	3	"1761374"
15	"6474562"	16	"6474681"	"410"	"Lakehurst, Manchester, Jackson - Port Authority"	3	"1761374"
5	"6410256"	17	"6474682"	"406"	"Jackson - Port Authority"	3	"1761374"
4	"6410252"	18	"6489993"	"602"	"Route 36 - Port Authority"	3	"1761374"
3	"6410251"	19	"6490583"	"604"	"Route 36 - Wall Street"	3	"1761374"
6	"6410257"	20	"6497305"	"404"	"Route 9 - Wall Street"	3	"1761374"
23	"8709460"	24	"8709461"	"206"	"Parkway Express - Wall Street Via Jersey City"	3	"1761374"

fast_travel_between_consecutive_stops

A transit vehicle moves too fast between two consecutive stops.

The speed threshold depends on route type:

Route type	Description	Threshold, km/h
0	Light rail	100
1	Subway	150
2	Rail	500
3	Bus	150
4	Ferry	80
5	Cable tram	30
6	Aerial lift	50
7	Funicular	50
11	Trolleybus	150
12	Monorail	150
-	Unknown	200

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the problematic trip.	tripId (?) `trip_id` of the problematic trip.	routeId (?) `route_id` of the problematic trip.	speedKph (?) Travel speed (km/h).	distanceKm (?) Distance between stops (km).	csvRowNumber1 (?) The row number of the first stop time.	stopSequence1 (?) `stop_sequence` of the first stop.	stopId1 (?) `stop_id` of the first stop.	stopName1 (?) `stop_name` of the first stop.	departureTime1 (?) `departure_time` of the first stop.	csvRowNumber2 (?) The row number of the second stop time.	stopSequence2 (?) `stop_sequence` of the second stop.	stopId2 (?) `stop_id` of the second stop.	stopName2 (?) `stop_name` of the second stop.	arrivalTime2 (?) `arrival_time` of the second stop.
164	"1404323890"	"7566101"	150.03339782108756	1.4586580343716848	2399	12	"39727405"	"Freehold - Us-9 @ Schibanoff Rd (Northbound)"	"07:22:00"	2400	13	"39727406"	"Manalapan - Us-9 @ E Freehold Rd (Northbound)"	"07:22:35"
159	"1064580205"	"7566101"	164.09902886681454	1.4586580343716848	1875	29	"39727405"	"Freehold - Us-9 @ Schibanoff Rd (Northbound)"	"07:26:00"	1876	30	"39727406"	"Manalapan - Us-9 @ E Freehold Rd (Northbound)"	"07:26:32"
154	"787777742"	"7566101"	150.03339782108756	1.4586580343716848	1624	12	"39727405"	"Freehold - Us-9 @ Schibanoff Rd (Northbound)"	"08:42:00"	1625	13	"39727406"	"Manalapan - Us-9 @ E Freehold Rd (Northbound)"	"08:42:35"
156	"1064579099"	"7566101"	164.09902886681454	1.4586580343716848	1767	29	"39727405"	"Freehold - Us-9 @ Schibanoff Rd (Northbound)"	"05:27:00"	1768	30	"39727406"	"Manalapan - Us-9 @ E Freehold Rd (Northbound)"	"05:27:32"
152	"787777739"	"7566101"	164.09902886681454	1.4586580343716848	1569	29	"39727405"	"Freehold - Us-9 @ Schibanoff Rd (Northbound)"	"05:46:00"	1570	30	"39727406"	"Manalapan - Us-9 @ E Freehold Rd (Northbound)"	"05:46:32"
157	"1064580203"	"7566101"	164.09902886681454	1.4586580343716848	1803	29	"39727405"	"Freehold - Us-9 @ Schibanoff Rd (Northbound)"	"06:27:00"	1804	30	"39727406"	"Manalapan - Us-9 @ E Freehold Rd (Northbound)"	"06:27:32"
155	"787777743"	"7566101"	150.03339782108756	1.4586580343716848	1660	12	"39727405"	"Freehold - Us-9 @ Schibanoff Rd (Northbound)"	"09:07:00"	1661	13	"39727406"	"Manalapan - Us-9 @ E Freehold Rd (Northbound)"	"09:07:35"
153	"787777741"	"7566101"	164.09902886681454	1.4586580343716848	1605	29	"39727405"	"Freehold - Us-9 @ Schibanoff Rd (Northbound)"	"06:49:00"	1606	30	"39727406"	"Manalapan - Us-9 @ E Freehold Rd (Northbound)"	"06:49:32"
158	"1064580204"	"7566101"	164.09902886681454	1.4586580343716848	1839	29	"39727405"	"Freehold - Us-9 @ Schibanoff Rd (Northbound)"	"07:07:00"	1840	30	"39727406"	"Manalapan - Us-9 @ E Freehold Rd (Northbound)"	"07:07:32"

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.
"trips.txt"	98	"trip_headsign"	"Lakehurst, Manchester, Jackson to Port Authority "
"trips.txt"	99	"trip_headsign"	"Lakehurst, Manchester, Jackson to Port Authority "
"trips.txt"	100	"trip_headsign"	"Lakehurst, Manchester, Jackson to Port Authority "
"trips.txt"	101	"trip_headsign"	"Lakehurst, Manchester, Jackson to Port Authority "
"trips.txt"	132	"trip_headsign"	"Wall Street to Route 9 (Freehold Mall) "

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"

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.
"trips.txt"	"trip_headsign"	"PNC to PABT"	47
"trips.txt"	"trip_headsign"	"PNC to PABT"	48
"trips.txt"	"trip_headsign"	"PNC to PABT"	49
"trips.txt"	"trip_headsign"	"PNC to PABT"	50
"trips.txt"	"trip_headsign"	"PNC to PABT"	51
"trips.txt"	"trip_headsign"	"PNC to PABT"	52
"trips.txt"	"trip_headsign"	"PNC to PABT"	53
"trips.txt"	"trip_headsign"	"PNC to PABT"	54

same_name_and_description_for_route

Same name and description for route.

The GTFS spec defines routes.txt route_desc as:

Description of a route that provides useful, quality information. Do not simply duplicate the name of the route.

See the GTFS and GTFS Best Practices links below for more examples of how to populate the route_short_name, route_long_name, and route_desc fields.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	routeId (?) The id of the faulty record.	routeDesc (?) The `routes.routes_desc` of the faulty record.	specifiedField (?) Either `route_short_name` or `route_long_name`.
21	"7566101"	"139"	"route_short_name"

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"	"20210913"	"20251211"

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.
"agency.txt"	"is_rt_supported"	7
"agency.txt"	"is_sa_supported"	8
"trips.txt"	"line_id"	9

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"line_group_stops.txt"
"line_groups.txt"
"lines.txt"
"metro_data.txt"