GTFS Schedule Validation Report

missing_trip_edge

Missing trip edge arrival_time or departure_time.

First and last stop of a trip must define both arrival_time and departure_time fields. Per stop_times.txt, "If there are not separate times for arrival and departure at a stop, enter the same value for arrival_time and departure_time."

You can see more about this notice here.

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

csvRowNumber (?) The row of the faulty record.	stopSequence (?) `stops.stop_sequence` of the faulty record.	tripId (?) The `trips.trip_id` of the faulty record.	specifiedField (?) Name of the missing field.
21345	29	"825"	"arrival_time"
21345	29	"825"	"departure_time"
21375	29	"826"	"arrival_time"
21375	29	"826"	"departure_time"
21405	29	"827"	"arrival_time"
21405	29	"827"	"departure_time"
21435	29	"828"	"arrival_time"
21435	29	"828"	"departure_time"
21465	29	"829"	"arrival_time"
21465	29	"829"	"departure_time"
21495	29	"830"	"arrival_time"
21495	29	"830"	"departure_time"
21525	29	"831"	"arrival_time"
21525	29	"831"	"departure_time"
21555	29	"832"	"arrival_time"
21555	29	"832"	"departure_time"
21585	29	"833"	"arrival_time"
21585	29	"833"	"departure_time"
21615	29	"834"	"arrival_time"
21615	29	"834"	"departure_time"
21645	29	"835"	"arrival_time"
21645	29	"835"	"departure_time"
21675	29	"836"	"arrival_time"
21675	29	"836"	"departure_time"
21315	29	"837"	"arrival_time"
21315	29	"837"	"departure_time"
15963	30	"637"	"arrival_time"
15963	30	"637"	"departure_time"
2838	29	"136"	"arrival_time"
2838	29	"136"	"departure_time"
2868	29	"137"	"arrival_time"
2868	29	"137"	"departure_time"
2898	29	"138"	"arrival_time"
2898	29	"138"	"departure_time"
2928	29	"139"	"arrival_time"
2928	29	"139"	"departure_time"
2958	29	"140"	"arrival_time"
2958	29	"140"	"departure_time"
2988	29	"141"	"arrival_time"
2988	29	"141"	"departure_time"
3018	29	"142"	"arrival_time"
3018	29	"142"	"departure_time"
3048	29	"143"	"arrival_time"
3048	29	"143"	"departure_time"
3078	29	"144"	"arrival_time"
3078	29	"144"	"departure_time"
3108	29	"145"	"arrival_time"
3108	29	"145"	"departure_time"
1256	29	"82"	"arrival_time"
1256	29	"82"	"departure_time"

stop_time_timepoint_without_times

arrival_time or departure_time not specified for timepoint.

Any records with stop_times.timepoint set to 1 must define a value for stop_times.arrival_time and stop_times.departure_time fields.

You can see more about this notice here.

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

csvRowNumber (?) The row number of the faulty record.	tripId (?) The faulty record's id.	stopSequence (?) The faulty record's `stops.stop_sequence`.	specifiedField (?) Either `departure_time` or `arrival_time`.
3	"0"	1	"arrival_time"
3	"0"	1	"departure_time"
7	"1"	1	"arrival_time"
7	"1"	1	"departure_time"
11	"2"	1	"arrival_time"
11	"2"	1	"departure_time"
15	"3"	1	"arrival_time"
15	"3"	1	"departure_time"
19	"4"	1	"arrival_time"
19	"4"	1	"departure_time"
23	"5"	1	"arrival_time"
23	"5"	1	"departure_time"
27	"6"	1	"arrival_time"
27	"6"	1	"departure_time"
31	"7"	1	"arrival_time"
31	"7"	1	"departure_time"
35	"8"	1	"arrival_time"
35	"8"	1	"departure_time"
39	"9"	1	"arrival_time"
39	"9"	1	"departure_time"
43	"10"	1	"arrival_time"
43	"10"	1	"departure_time"
47	"11"	1	"arrival_time"
47	"11"	1	"departure_time"
51	"12"	1	"arrival_time"
51	"12"	1	"departure_time"
55	"13"	1	"arrival_time"
55	"13"	1	"departure_time"
59	"14"	1	"arrival_time"
59	"14"	1	"departure_time"
63	"15"	1	"arrival_time"
63	"15"	1	"departure_time"
67	"16"	1	"arrival_time"
67	"16"	1	"departure_time"
71	"17"	1	"arrival_time"
71	"17"	1	"departure_time"
75	"18"	1	"arrival_time"
75	"18"	1	"departure_time"
79	"19"	1	"arrival_time"
79	"19"	1	"departure_time"
83	"20"	1	"arrival_time"
83	"20"	1	"departure_time"
87	"21"	1	"arrival_time"
87	"21"	1	"departure_time"
91	"22"	1	"arrival_time"
91	"22"	1	"departure_time"
95	"23"	1	"arrival_time"
95	"23"	1	"departure_time"
99	"24"	1	"arrival_time"
99	"24"	1	"departure_time"

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.

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

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	"30"	4	"88"	"3"	"#3 E 6th to Downtown"	3	""
5	"66"	9	"36"	"10"	"#10 W 10th to West Ridge"	3	""
6	"67"	12	"15"	"12"	"#12 Huntoon to Downtown"	3	""
3	"61"	14	"97"	"6"	"#6 W 6th to Downtown"	3	""
7	"29"	15	"85"	"1"	"#1 Oakland to Dillons North"	3	""
16	"25"	18	"72"	"21"	"#21 W 21st to Downtown"	3	""
10	"8"	22	"92"	"4"	"#4 California to Downtown"	3	""
20	"78"	29	"91"	"3"	"#3 E 6th Eastbound to Rice"	3	""
11	"96"	30	"62"	"6"	"#6 W 6th to Walmart West"	3	""
25	"38"	31	"68"	"12"	"#12 Huntoon to Walmart West"	3	""
2	"30"	33	"89"	"3"	"#3 E 6th to Downtown"	3	""
25	"38"	34	"102"	"12"	"#12 Huntoon to Walmart West"	3	""
7	"29"	35	"52"	"1"	"#1 Oakland to Dillons North"	3	""
6	"67"	36	"103"	"12"	"#12 Huntoon to Downtown"	3	""
8	"51"	37	"26"	"1"	"#1 Oakland to Downtown"	3	""
2	"30"	39	"79"	"3"	"#3 E 6th to Downtown"	3	""
32	"64"	42	"35"	"7"	"#7 Washburn to Walmart South"	3	""
17	"21"	43	"37"	"10S"	"10 Special"	3	""
41	"106"	44	"71"	"21"	"#21 W 21st to West Ridge"	3	""
21	"5"	45	"59"	"5"	"#5 Indiana to Downtown"	3	""
21	"5"	47	"95"	"5"	"#5 Indiana to Downtown"	3	""
38	"105"	48	"11"	"17"	"#17 W 17th to Downtown"	3	""
8	"51"	49	"84"	"1"	"#1 Oakland to Downtown"	3	""
32	"64"	52	"98"	"7"	"#7 Washburn to Walmart South"	3	""
41	"106"	53	"41"	"21"	"#21 W 21st to West Ridge"	3	""
10	"8"	54	"57"	"4"	"#4 California to Downtown"	3	""
20	"78"	55	"31"	"3"	"#3 E 6th Eastbound to Rice"	3	""
2	"30"	56	"55"	"3"	"#3 E 6th to Downtown"	3	""
19	"104"	57	"70"	"17"	"#17 W 17th to Walmart West"	3	""
11	"96"	58	"112"	"6"	"#6 W 6th to Walmart West"	3	""
16	"25"	59	"107"	"21"	"#21 W 21st to Downtown"	3	""
51	"93"	60	"32"	"4"	"#4 California to Avondale"	3	""
28	"60"	63	"94"	"5"	"#5 Indiana to 33rd & Gage"	3	""
32	"64"	64	"49"	"7"	"#7 Washburn to Walmart South"	3	""
3	"61"	66	"9"	"6"	"#6 W 6th to Downtown"	3	""
5	"66"	68	"100"	"10"	"#10 W 10th to West Ridge"	3	""
24	"4"	69	"43"	"10S2"	"10 Special #2"	3	""
40	"90"	70	"44"	"3"	"#3 E 6th Eastbound to Croco"	3	""
61	"28"	71	"87"	"2"	"#2 N Kansas to Downtown"	3	""
2	"30"	72	"45"	"3"	"#3 E 6th to Downtown"	3	""
27	"63"	73	"99"	"7"	"#7 Washburn to Downtown"	3	""
26	"54"	74	"86"	"2"	"#2 N Kansas to Dillons North"	3	""
21	"5"	75	"110"	"5"	"#5 Indiana to Downtown"	3	""
3	"61"	76	"111"	"6"	"#6 W 6th to Downtown"	3	""
28	"60"	77	"33"	"5"	"#5 Indiana to 33rd & Gage"	3	""
38	"105"	80	"69"	"17"	"#17 W 17th to Downtown"	3	""
51	"93"	81	"58"	"4"	"#4 California to Avondale"	3	""
50	"101"	83	"65"	"10"	"#10 W 10th to Downtown"	3	""
40	"90"	84	"56"	"3"	"#3 E 6th Eastbound to Croco"	3	""
78	"74"	85	"42"	"29"	"#29 W 29th to Urish"	3	""

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.

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

csvRowNumber (?) The row of the faulty record.	serviceId (?) The service id of the faulty record.
2	"113"
3	"86"
4	"110"
5	"4"
6	"39"
7	"100"
8	"35"
9	"11"
10	"84"
11	"58"
12	"64"
13	"101"
14	"85"
15	"66"
16	"28"
17	"34"
18	"103"
19	"26"
21	"54"
22	"43"
23	"44"
24	"87"
25	"67"
26	"38"
27	"45"
28	"63"
29	"53"
30	"51"
31	"16"
32	"25"
33	"36"
34	"31"
35	"55"
36	"33"
37	"60"
38	"21"
39	"91"
40	"72"
41	"105"
42	"8"
43	"104"
44	"37"
45	"62"
46	"30"
47	"93"
48	"108"
49	"70"
50	"89"
51	"94"
52	"71"

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

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.

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

filename (?) The name of the faulty file.	csvRowNumber (?) The row of the faulty record.	fieldName (?) The name of the missing field.
"agency.txt"	2	"agency_id"
"feed_info.txt"	2	"feed_start_date"
"feed_info.txt"	2	"feed_end_date"
"feed_info.txt"	2	"feed_version"
"routes.txt"	2	"agency_id"
"routes.txt"	3	"agency_id"
"routes.txt"	4	"agency_id"
"routes.txt"	5	"agency_id"
"routes.txt"	6	"agency_id"
"routes.txt"	7	"agency_id"
"routes.txt"	8	"agency_id"
"routes.txt"	9	"agency_id"
"routes.txt"	10	"agency_id"
"routes.txt"	11	"agency_id"
"routes.txt"	12	"agency_id"
"routes.txt"	13	"agency_id"
"routes.txt"	14	"agency_id"
"routes.txt"	15	"agency_id"
"routes.txt"	16	"agency_id"
"routes.txt"	17	"agency_id"
"routes.txt"	18	"agency_id"
"routes.txt"	19	"agency_id"
"routes.txt"	20	"agency_id"
"routes.txt"	21	"agency_id"
"routes.txt"	22	"agency_id"
"routes.txt"	23	"agency_id"
"routes.txt"	24	"agency_id"
"routes.txt"	25	"agency_id"
"routes.txt"	26	"agency_id"
"routes.txt"	27	"agency_id"
"routes.txt"	28	"agency_id"
"routes.txt"	29	"agency_id"
"routes.txt"	30	"agency_id"
"routes.txt"	31	"agency_id"
"routes.txt"	32	"agency_id"
"routes.txt"	33	"agency_id"
"routes.txt"	34	"agency_id"
"routes.txt"	35	"agency_id"
"routes.txt"	36	"agency_id"
"routes.txt"	37	"agency_id"
"routes.txt"	38	"agency_id"
"routes.txt"	39	"agency_id"
"routes.txt"	40	"agency_id"
"routes.txt"	41	"agency_id"
"routes.txt"	42	"agency_id"
"routes.txt"	43	"agency_id"
"routes.txt"	44	"agency_id"
"routes.txt"	45	"agency_id"
"routes.txt"	46	"agency_id"
"routes.txt"	47	"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.
"stops.txt"	"stop_name"	"25th @ HPHS"	45

stops_match_shape_out_of_order

Two stop entries are different than their arrival-departure order defined by shapes.txt.

This could indicate a problem with the location of the stops, the path of the shape, or the sequence of the stops for their trip.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record from `trips.txt`.	shapeId (?) The id of the shape that is referred to.	tripId (?) The id of the trip that is referred to.	stopTimeCsvRowNumber1 (?) The row number of the first faulty record from `stop_times.txt`.	stopId1 (?) The id of the first stop that is referred to.	stopName1 (?) The name of the first stop that is referred to.	match1 (?) Latitude and longitude pair of the first matching location.	stopTimeCsvRowNumber2 (?) The row number of the second faulty record from `stop_times.txt`.	stopId2 (?) The id of the second stop that is referred to.	stopName2 (?) The name of the second stop that is referred to.	match2 (?) Latitude and longitude pair of the second matching location.
988	"42"	"986"	25896	"569"	"27th @ Wanamaker"	[39.017810164005056,-95.7626607059506]	25895	"568"	"Villa West @ 27th"	[39.01770715232208,-95.76714539394256]

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.
"20260123"	"20191216"	"20211210"

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.
"trips.txt"	"block_name"	11