GTFS Schedule Validation Report

equal_shape_distance_diff_coordinates_distance_below_threshold

Two consecutive points have equal shape_dist_traveled and different lat/lon coordinates in shapes.txt and the distance between the two points is less than 1.11m.

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 small difference of coordinates (less than 1.11 m distance) result in a warning.

You can see more about this notice here.

shapeId (?) The id of the faulty shape.	csvRowNumber (?) The row number from `shapes.txt`.	shapeDistTraveled (?) The faulty record's `shape_dist_traveled` value.	shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`.	prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point.	prevShapeDistTraveled (?) The previous shape point's `shape_dist_traveled` value.	prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`.	actualDistanceBetweenShapePoints (?) Actual distance traveled along the shape from the first shape point to the previous shape point.
"zenbus:Route:5914280958361600:LOC"	245	8619.0	243	244	8619.0	242	0.5747374867576858
"zenbus:Route:5082957771440128:LOC"	812	2715.0	74	811	2715.0	73	0.4507001696502792
"zenbus:Route:5082957771440128:LOC"	898	6753.0	160	897	6753.0	159	0.7353035478620231
"zenbus:Route:5082957771440128:LOC"	1092	14390.0	354	1091	14390.0	353	0.6766664711535713
"zenbus:Route:4813491980468224:LOC"	601	7958.0	220	600	7958.0	219	0.5747374867576858

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 386 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	"6282085046157312:0"	0
3	"6282085046157312:0"	1
4	"6282085046157312:0"	2
5	"6282085046157312:0"	3
6	"6282085046157312:0"	4
7	"6282085046157312:0"	5
8	"6282085046157312:0"	6
9	"6282085046157312:0"	7
10	"6282085046157312:0"	8
11	"6282085046157312:0"	9
12	"6282085046157312:0"	10
13	"6282085046157312:0"	11
14	"6282085046157312:0"	12
15	"6282085046157312:0"	13
16	"6282085046157312:0"	14
17	"6282085046157312:0"	15
18	"6282085046157312:0"	16
19	"6282085046157312:0"	17
20	"6282085046157312:0"	18
21	"6282085046157312:0"	19
22	"6282085046157312:0"	20
23	"6282085046157312:0"	21
24	"6282085046157312:0"	22
25	"6282085046157312:0"	23
26	"6282085046157312:0"	24
27	"6282085046157312:0"	25
28	"6282085046157312:0"	26
29	"6282085046157312:0"	27
30	"6282085046157312:1"	1
31	"6282085046157312:1"	2
32	"6282085046157312:1"	3
33	"6282085046157312:1"	4
34	"6282085046157312:1"	5
35	"6282085046157312:1"	6
36	"6282085046157312:1"	7
37	"6282085046157312:1"	8
38	"6282085046157312:1"	9
39	"6282085046157312:1"	10
40	"6282085046157312:1"	11
41	"6282085046157312:1"	12
42	"6282085046157312:1"	13
43	"6282085046157312:1"	14
44	"6282085046157312:1"	15
45	"6282085046157312:1"	16
46	"6282085046157312:1"	17
47	"6282085046157312:1"	18
48	"6282085046157312:1"	19
49	"6282085046157312:1"	20
50	"6282085046157312:1"	21
51	"6282085046157312:1"	22

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_desc"	"PUBLISH_AS_LINE_ID=30030155"	2

route_long_name_contains_short_name

Long name should not contain short name for a single route.

In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.

Good examples:

route_short_name/route_long_name	Dataset
"N"/"Judah"	Muni San Fransisco
"6"/"ML King Jr Blvd"	Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent"	STM Montreal
"1"/"Rangiora/Cashmere"	Metro Christchurch

Bad examples:

route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"

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`.	routeLongName (?) The faulty record's `route_long_name`.
"zenbus:Line:30030155:LOC"	2	"Urbain"	"Urbain Bernay"

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"	"zenbus_mission_id"	11
"trips.txt"	"trip_headsign_code"	12