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`.
27	"3645"	71	"8681"	"144"	"Vilnius (Žalgirio stotelė) – Nemenčinė per Pikeliškes"	3	"53"

equal_shape_distance_same_coordinates

Two consecutive points have equal shape_dist_traveled and the same lat/lon coordinates in shapes.txt.

When sorted by shape.shape_pt_sequence, the values for shape_dist_traveled must increase along a shape. Two consecutive points with equal values for shape_dist_traveled and the same coordinates indicate a duplicative shape point.

You can see more about this notice here.

shapeId (?) The id of the faulty shape.	csvRowNumber (?) The row number from `shapes.txt`.	shapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the faulty record.	shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`.	prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point.	prevShapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the previous shape point.	prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`.
"16761"	76932	34775.1	1306	76931	34775.1	1305
"16760"	78515	29380.9	786	78514	29380.9	785
"9142"	47862	44085.1	1397	47861	44085.1	1396
"9323"	55665	5321.0	212	55664	5321.0	211
"9324"	116284	44085.1	1397	116283	44085.1	1396
"9325"	83999	9339.5	341	83998	9339.5	340

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"

missing_timepoint_value

stop_times.timepoint value is missing for a record.

Even though the column timepoint is optional in stop_times.txt according to the specification, stop_times.timepoint should not be empty when provided.

You can see more about this notice here.

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

csvRowNumber (?) The row number of the faulty record.	tripId (?) The faulty record's `stop_times.trip_id`.	stopSequence (?) The faulty record's `stop_times.stop_sequence`.
2	"43001"	1
3	"43001"	2
4	"43001"	3
5	"43001"	4
6	"43001"	5
7	"43001"	6
8	"43001"	7
9	"43001"	8
10	"43001"	9
11	"43001"	10
12	"43001"	11
13	"43001"	12
14	"43001"	13
15	"43001"	14
16	"43001"	15
17	"43001"	16
18	"43001"	17
19	"43001"	18
20	"43001"	19
21	"43001"	20
22	"43001"	21
23	"43003"	1
24	"43003"	2
25	"43003"	3
26	"43003"	4
27	"43003"	5
28	"43003"	6
29	"43003"	7
30	"43003"	8
31	"43003"	9
32	"43003"	10
33	"43003"	11
34	"43003"	12
35	"43003"	13
36	"43003"	14
37	"43003"	15
38	"43003"	16
39	"43003"	17
40	"43003"	18
41	"43003"	19
42	"43003"	20
43	"43003"	21
44	"43030"	1
45	"43030"	2
46	"43030"	3
47	"43030"	4
48	"43030"	5
49	"43030"	6
50	"43030"	7
51	"43030"	8

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"	"40 km"	178
"stops.txt"	"stop_name"	"13-sis kilometras"	191
"stops.txt"	"stop_name"	"11-as kilometras"	215
"stops.txt"	"stop_name"	"RUKAINIŲ GIRIN."	235
"stops.txt"	"stop_name"	"23 km"	328
"stops.txt"	"stop_name"	"23 km"	335
"stops.txt"	"stop_name"	"11-as kilometras"	358
"stops.txt"	"stop_name"	"16-sis kilometras"	367
"stops.txt"	"stop_name"	"RUKAINIŲ GIRIN."	372
"stops.txt"	"stop_name"	"40 km"	398
"stops.txt"	"stop_name"	"16-sis kilometras"	486
"stops.txt"	"stop_name"	"13-sis kilometras"	488
"stops.txt"	"stop_name"	"9 kilometras"	698
"stops.txt"	"stop_name"	"9 kilometras"	699
"stops.txt"	"stop_name"	"32 kilometras"	701
"stops.txt"	"stop_name"	"32 kilometras"	702
"stops.txt"	"stop_name"	"žieda"	916

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.
448	"17131"	"2515700"	6504	"16347"	"Sudervė"	[54.761036,25.063001999999997]	2603.225038082936

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.
"fare_attributes.txt"	"journey_duration"	8
"routes.txt"	"eligibility_restricted"	11
"routes.txt"	"bikes_allowed"	12
"routes.txt"	"regional_fare_card"	14
"stops.txt"	"stop_direction"	12
"stops.txt"	"vehicle_type"	14
"stops.txt"	"mta_stop_id"	17
"stops.txt"	"regional_fare_card"	18
"stop_times.txt"	"start_service_area_id"	1
"stop_times.txt"	"end_service_area_id"	2
"stop_times.txt"	"note_id"	5
"stop_times.txt"	"to_stop_sequence"	16
"stop_times.txt"	"route_short_name"	18
"stop_times.txt"	"start_service_area_radius"	24
"stop_times.txt"	"end_service_area_radius"	25
"stop_times.txt"	"fare_period_id"	26
"stop_times.txt"	"departure_buffer"	27
"stop_times.txt"	"track"	28
"stop_times.txt"	"mean_duration_factor"	29
"stop_times.txt"	"mean_duration_offset"	30
"stop_times.txt"	"safe_duration_factor"	31
"stop_times.txt"	"safe_duration_offset"	32
"stop_times.txt"	"free_running_flag"	33
"trips.txt"	"note_id"	2
"trips.txt"	"mean_duration_factor"	12
"trips.txt"	"mean_duration_offset"	13
"trips.txt"	"safe_duration_factor"	14
"trips.txt"	"safe_duration_offset"	15
"trips.txt"	"cars_allowed"	16
"trips.txt"	"peak_offpeak"	17
"trips.txt"	"mta_trip_id"	18
"trips.txt"	"boarding_type"	19