GTFS Schedule Validation Report

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 52 affected records are displayed below.

csvRowNumber (?) The row of the faulty record.	serviceId (?) The service id of the faulty record.
3	"1313"
4	"1314"
5	"1315"
6	"1316"
7	"1317"
8	"1318"
9	"1319"
10	"1320"
11	"1321"
12	"1322"
13	"1323"
14	"1324"
15	"1325"
16	"1326"
17	"1327"
18	"1328"
19	"1329"
20	"1330"
21	"1331"
22	"1332"
23	"1333"
24	"1334"
25	"1335"
26	"1336"
27	"1337"
28	"1338"
29	"1339"
30	"1340"
31	"1341"
32	"1342"
33	"1343"
34	"1344"
35	"1345"
36	"1346"
38	"1348"
39	"1349"
40	"1350"
41	"1351"
42	"1352"
44	"1354"
45	"1355"
46	"1356"
47	"1357"
48	"1358"
49	"1359"
50	"1360"
51	"1361"
52	"1362"
53	"1363"
54	"1364"

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.

filename (?) The name of the faulty file.	csvRowNumber (?) The row of the faulty record.	fieldName (?) The name of the missing field.
"feed_info.txt"	2	"feed_start_date"
"feed_info.txt"	2	"feed_end_date"

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"	"560X EB"	33
"routes.txt"	"route_short_name"	"560X WB"	34
"routes.txt"	"route_short_name"	"413 NB"	35
"routes.txt"	"route_short_name"	"413 SB"	36
"routes.txt"	"route_long_name"	"NOT IN SERVICE"	37
"routes.txt"	"route_short_name"	"411M NB"	38
"routes.txt"	"route_short_name"	"411 NB"	39
"routes.txt"	"route_short_name"	"411 SB"	40
"routes.txt"	"route_short_name"	"203 EB"	48
"routes.txt"	"route_short_name"	"203 WB"	49
"stops.txt"	"stop_name"	"VIOLA ROAD NORTHEAST AND VIOLA HEIGHTS DRIVE NORTHEAST"	32
"stops.txt"	"stop_name"	"ALONG VIOLA HEIGHTS DRIVE NORTHEAST AND NORTH OF 26TH ST. NORTHEAST"	36
"stops.txt"	"stop_name"	"ROCKY CREEK DRIVE NORTHEAST AND VIOLA HEIGHTS DRIVE NORTHEAST"	37
"stops.txt"	"stop_name"	"MAYO CLINIC NORTHWEST"	39
"stops.txt"	"stop_name"	"VIOLA HEIGHTS DRIVE NORTHEAST AND NORTHERN VIOLA LANE NORTHEAST"	40
"stops.txt"	"stop_name"	"DOWNTOWN TRANSIT CENTER E"	50
"stops.txt"	"stop_name"	"ALONG WILLOW HEIGHTS DRIVE SOUTHWEST AND NORTH OF 40TH ST SOUTHWEST"	218
"stops.txt"	"stop_name"	"TARGET NORTH"	417
"stops.txt"	"stop_name"	"JOHN MARSHALL HIGH SCHOOL"	449
"stops.txt"	"stop_name"	"MEADOW HILLS DRIVE SOUTHWEST AND HIGHVIEW AVENUE SOUTHWEST"	467
"stops.txt"	"stop_name"	"JOHN ADAMS MIDDLE SCHOOL"	509
"stops.txt"	"stop_name"	"60TH STREET AT MOUNTAIN ASH LANE NORTHWEST"	540
"stops.txt"	"stop_name"	"60TH STREET AT 25TH AVENUE NORTHWEST"	542
"stops.txt"	"stop_name"	"25TH AVENUE AT BOULDER RIDGE DRIVE NORTHWEST"	543
"stops.txt"	"stop_name"	"BOULDER RIDGE DRIVE AT GRANITE DRIVE NORTHWEST"	544
"stops.txt"	"stop_name"	"BOULDER RIDGE DRIVE AT 28TH AVENUE NORTHWEST"	545
"stops.txt"	"stop_name"	"BOULDER RIDGE DRIVE AT BANDEL ROAD NORTHWEST"	546
"stops.txt"	"stop_name"	"IBM BLDG 33rd"	577
"stops.txt"	"stop_name"	"MAYO NORTHWEST"	582
"stops.txt"	"stop_name"	"125 LIVE"	659

route_short_name_too_long

Short name of a route is too long (more than 12 characters).

You can see more about this notice here.

routeId (?) The id of the faulty record.	csvRowNumber (?) The row number of the faulty record.	routeShortName (?) The faulty record's `route_short_name`.
"1330"	20	"25 Weekend NB"
"1331"	21	"25 Weekend SB"
"1335"	25	"26 Weekend SB"

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. This potentially indicates a problem with the location of the stop or the path of the shape.

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.	stopTimeCsvRowNumber (?) The row number of the faulty record from `stop_times.txt`.	stopId (?) The id of the stop that is referred to.	stopName (?) The name of the stop that is referred to.	match (?) Latitude and longitude pair of the location.	geoDistanceToShape (?) Distance from stop to shape.
322	"1361"	"387"	10272	"631"	"5th Street Southwest and 2nd Avenue Southwest"	[44.01805936001877,-92.46294807741265]	231.7675874841232
27	"1365"	"120"	966	"1508"	"IBM Park AND Ride"	[44.06143,-92.50369]	206.88954282646282

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	stopId (?) The id of the faulty stop.	stopName (?) The name of the faulty stop.
51	"1499"	"Rochester Public Transit Garage"
252	"257"	"4th Street Southeast and 11th Avenue Southeast"
253	"258"	"4th Street Southeast and 9th Avenue Southeast"
254	"259"	"4th Street Southeast and 15th Avenue Southeast"
256	"260"	"4th Street Southeast and 14th Avenue Southeast"
258	"262"	"4th Street Southeast and 16th Avenue Southeast"
299	"307"	"4th Street Southeast and 4th Avenue Southeast"
391	"412"	"4th Street Southeast and 7th Avenue Southeast"

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.
521	"1334"	"566"	13471	"480"	"Along 3rd Avenue Northwest and 1000 North of 14th St. Northwest"	[44.03824060576848,-92.46707624684451]	13470	"485"	"14th St. Northwest and 5th Avenue Northwest"	[44.03615633579028,-92.47007831552163]
522	"1334"	"567"	13488	"715"	"6th St Northwest and 6th Avenue Northwest"	[44.029613913040144,-92.47096178385368]	13487	"714"	"4th Street Northwest and 6th Avenue Northwest"	[44.02733068871308,-92.4709880035409]
532	"1334"	"576"	13720	"714"	"4th Street Northwest and 6th Avenue Northwest"	[44.02733068871308,-92.4709880035409]	13719	"167"	"6th Avenue Northwest and 1st St. Northwest"	[44.02432014660276,-92.47103066359828]
361	"1332"	"421"	11364	"717"	"West River Parkway Northwest and 9th Avenue Northwest"	[44.05985553623457,-92.47306745621482]	11363	"83"	"Elton Hills Drive Northwest and Viking Drive Northwest"	[44.04524157628965,-92.46878630966953]
314	"1342"	"38"	9901	"90"	"Fairway Drive Northwest AND Chesapeke LN Northwest"	[44.07992238260365,-92.52195483538227]	9900	"387"	"31th Avenue Northwest and Arbor Drive Northwest"	[44.07056026687825,-92.50874201188455]
309	"1330"	"375"	9705	"143"	"41st Street Northwest and East Frontage Highway 52nd Road Northwest"	[44.06529716709164,-92.49422519358514]	9704	"149"	"Along 41st St. Northwest and West Of 19th Avenue Northwest"	[44.065297264761384,-92.4942413330618]
313	"1330"	"379"	9883	"143"	"41st Street Northwest and East Frontage Highway 52nd Road Northwest"	[44.06529716709164,-92.49422519358514]	9882	"149"	"Along 41st St. Northwest and West Of 19th Avenue Northwest"	[44.065297264761384,-92.4942413330618]
296	"1328"	"363"	9126	"143"	"41st Street Northwest and East Frontage Highway 52nd Road Northwest"	[44.06529716709164,-92.49422519358514]	9125	"149"	"Along 41st St. Northwest and West Of 19th Avenue Northwest"	[44.065297264761384,-92.4942413330618]

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"	"20230424"	"20250228"

unusable_trip

Trips must have more than one stop to be usable.

A trip must visit more than one stop in stop_times.txt to be usable by passengers for boarding and alighting.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	tripId (?) The faulty record's id.
353	"414"
354	"415"
355	"416"
356	"417"
357	"418"
358	"419"
360	"420"
367	"427"
368	"428"
369	"429"
371	"430"
372	"431"
373	"432"
374	"433"

unused_shape

Shape is not used in GTFS file trips.txt.

All records defined by GTFS shapes.txt should be used in trips.txt.

You can see more about this notice here.

shapeId (?) The faulty record's id.	csvRowNumber (?) The row number of the faulty record.
"1347"	5789

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.
"feed_info.txt"	"feed_id"	1
"trips.txt"	"drt_advance_book_min"	5
"trips.txt"	"peak_offpeak"	6
"trips.txt"	"boarding_type"	7
"stop_times.txt"	"departure_buffer"	6