GTFS Schedule Validation Report

trip_distance_exceeds_shape_distance

The distance between the last shape point and last stop point is greater than or equal to the 11.1m threshold.

You can see more about this notice here.

tripId (?) The faulty record's trip id.	shapeId (?) The faulty record's shape id.	maxTripDistanceTraveled (?) The faulty record's trip max distance traveled.	maxShapeDistanceTraveled (?) The faulty record's shape max distance traveled.	geoDistanceToShape (?) The distance in meters between the shape and the stop.
"1"	"0"	20165.695	0.0	4858.404545179862
"10"	"5"	9820.1	0.0	4349.636889305186
"10_0"	"5"	9820.1	0.0	4349.636889305186
"10_0_0"	"5"	9820.1	0.0	4349.636889305186
"10_1"	"5"	9820.1	0.0	4349.636889305186
"11"	"6"	9539.5	0.0	4341.239032574345
"11_0"	"6"	9539.5	0.0	4341.239032574345
"11_0_0"	"6"	9539.5	0.0	4341.239032574345
"11_0_1"	"6"	9539.5	0.0	4341.239032574345
"1_0"	"0"	20165.695	0.0	4858.404545179862
"2"	"1"	9288.207	0.0	4858.404545179862
"2_0"	"1"	9288.207	0.0	4858.404545179862
"2_0_0"	"1"	9288.207	0.0	4858.404545179862
"2_1"	"1"	9288.207	0.0	4858.404545179862
"3"	"2"	20239.286	0.0	4860.497077103977
"4"	"3"	8043.038	0.0	4862.280780777525
"4_0"	"3"	8043.038	0.0	4862.280780777525
"4_1"	"3"	8043.038	0.0	4862.280780777525
"5"	"4"	15437.781	0.0	8756.53803084325

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.

csvRowNumber (?) The row of the faulty record.	serviceId (?) The service id of the faulty record.
2	"ETE 2024"
3	"ETE 2024 L2"

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.

When at least one of stop_times.arrival_time or stop_times.departure_time are provided, stop_times.timepoint should be defined

You can see more about this notice here.

Only the first 50 of 253 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	"1"	0
3	"1"	1
4	"1"	2
5	"1"	3
6	"1"	4
7	"1"	5
8	"1"	6
9	"1"	7
10	"1"	8
11	"1"	9
12	"1"	10
13	"1"	11
14	"1"	12
15	"1"	13
16	"1"	14
17	"1"	15
18	"1"	16
19	"1"	17
20	"1"	18
21	"1"	19
22	"10"	0
23	"10"	1
24	"10"	2
25	"10"	3
26	"10"	4
27	"10"	5
28	"10"	6
29	"10"	7
30	"10"	8
31	"10"	9
32	"10"	10
33	"10"	11
34	"10_0"	0
35	"10_0"	1
36	"10_0"	2
37	"10_0"	3
38	"10_0"	4
39	"10_0"	5
40	"10_0"	6
41	"10_0"	7
42	"10_0"	8
43	"10_0"	9
44	"10_0"	10
45	"10_0"	11
46	"10_0_0"	0
47	"10_0_0"	1
48	"10_0_0"	2
49	"10_0_0"	3
50	"10_0_0"	4
51	"10_0_0"	5
52	"10_0_0"	6
53	"10_0_0"	7
54	"10_0_0"	8
55	"10_0_0"	9
56	"10_0_0"	10
57	"10_0_0"	11
58	"10_1"	0
59	"10_1"	1
60	"10_1"	2
61	"10_1"	3
62	"10_1"	4
63	"10_1"	5
64	"10_1"	6
65	"10_1"	7
66	"10_1"	8
67	"10_1"	9
68	"10_1"	10
69	"10_1"	11
70	"11"	0
71	"11"	1
72	"11"	2
73	"11"	3
74	"11"	4
75	"11"	5
76	"11"	6
77	"11"	7
78	"11"	8
79	"11"	9
80	"11"	10
81	"11"	11
82	"11_0"	0
83	"11_0"	1
84	"11_0"	2
85	"11_0"	3
86	"11_0"	4
87	"11_0"	5
88	"11_0"	6
89	"11_0"	7
90	"11_0"	8
91	"11_0"	9
92	"11_0"	10
93	"11_0"	11
94	"11_0_0"	0
95	"11_0_0"	1
96	"11_0_0"	2
97	"11_0_0"	3
98	"11_0_0"	4
99	"11_0_0"	5
100	"11_0_0"	6
101	"11_0_0"	7
102	"11_0_0"	8
103	"11_0_0"	9
104	"11_0_0"	10
105	"11_0_0"	11
106	"11_0_1"	0
107	"11_0_1"	1
108	"11_0_1"	2
109	"11_0_1"	3
110	"11_0_1"	4
111	"11_0_1"	5
112	"11_0_1"	6
113	"11_0_1"	7
114	"11_0_1"	8
115	"11_0_1"	9
116	"11_0_1"	10
117	"11_0_1"	11
118	"1_0"	0
119	"1_0"	1
120	"1_0"	2
121	"1_0"	3
122	"1_0"	4
123	"1_0"	5
124	"1_0"	6
125	"1_0"	7
126	"1_0"	8
127	"1_0"	9
128	"1_0"	10
129	"1_0"	11
130	"1_0"	12
131	"1_0"	13
132	"1_0"	14
133	"1_0"	15
134	"1_0"	16
135	"1_0"	17
136	"1_0"	18
137	"1_0"	19
138	"2"	0
139	"2"	1
140	"2"	2
141	"2"	3
142	"2"	4
143	"2"	5
144	"2"	6
145	"2"	7
146	"2"	8
147	"2"	9
148	"2"	10
149	"2"	11
150	"2_0"	0
151	"2_0"	1
152	"2_0"	2
153	"2_0"	3
154	"2_0"	4
155	"2_0"	5
156	"2_0"	6
157	"2_0"	7
158	"2_0"	8
159	"2_0"	9
160	"2_0"	10
161	"2_0"	11
162	"2_0_0"	0
163	"2_0_0"	1
164	"2_0_0"	2
165	"2_0_0"	3
166	"2_0_0"	4
167	"2_0_0"	5
168	"2_0_0"	6
169	"2_0_0"	7
170	"2_0_0"	8
171	"2_0_0"	9
172	"2_0_0"	10
173	"2_0_0"	11
174	"2_1"	0
175	"2_1"	1
176	"2_1"	2
177	"2_1"	3
178	"2_1"	4
179	"2_1"	5
180	"2_1"	6
181	"2_1"	7
182	"2_1"	8
183	"2_1"	9
184	"2_1"	10
185	"2_1"	11
186	"3"	0
187	"3"	1
188	"3"	2
189	"3"	3
190	"3"	4
191	"3"	5
192	"3"	6
193	"3"	7
194	"3"	8
195	"3"	9
196	"3"	10
197	"3"	11
198	"3"	12
199	"3"	13
200	"3"	14
201	"3"	15
202	"3"	16
203	"3"	17
204	"3"	18
205	"3"	19
206	"4"	0
207	"4"	1
208	"4"	2
209	"4"	3
210	"4"	4
211	"4"	5
212	"4"	6
213	"4"	7
214	"4"	8
215	"4"	9
216	"4"	11
217	"4_0"	0
218	"4_0"	1
219	"4_0"	2
220	"4_0"	3
221	"4_0"	4
222	"4_0"	5
223	"4_0"	6
224	"4_0"	7
225	"4_0"	8
226	"4_0"	9
227	"4_0"	11
228	"4_1"	0
229	"4_1"	1
230	"4_1"	2
231	"4_1"	3
232	"4_1"	4
233	"4_1"	5
234	"4_1"	6
235	"4_1"	7
236	"4_1"	8
237	"4_1"	9
238	"4_1"	11
239	"5"	0
240	"5"	1
241	"5"	2
242	"5"	3
243	"5"	4
244	"5"	5
245	"5"	6
246	"5"	7
247	"5"	8
248	"5"	9
249	"5"	10
250	"5"	11
251	"5"	12
252	"5"	13
253	"5"	14
254	"5"	15

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.
"agency.txt"	"agency_name"	"SNT SUMA"	2
"stops.txt"	"stop_name"	"PORT GRIMAUD 1 PLAGE"	2
"stops.txt"	"stop_name"	"CAMPING CHARLEMAGNE"	3
"stops.txt"	"stop_name"	"HAMEAU DE LA TOURRE"	4
"stops.txt"	"stop_name"	"HAMEAU VAL DE GILLY"	5
"stops.txt"	"stop_name"	"PORT GRIMAUD POTERNE"	6
"stops.txt"	"stop_name"	"PORT GRIMAUD ECHANGEUR"	7
"stops.txt"	"stop_name"	"LES BLAQUIERES"	8
"stops.txt"	"stop_name"	"LA RINE"	10
"stops.txt"	"stop_name"	"COOPERATIVE/GENDARMERIE"	11
"stops.txt"	"stop_name"	"VILLAGE MAIRIE CABRE D’OR"	12
"stops.txt"	"stop_name"	"OFFICE DE TOURISME"	13
"stops.txt"	"stop_name"	"CAMP MARIN"	15
"stops.txt"	"stop_name"	"ROND POINT COOPERATIVE"	16
"stops.txt"	"stop_name"	"LA PINEDE"	18
"stops.txt"	"stop_name"	"LA QUESTE"	19
"stops.txt"	"stop_name"	"LES BASTIDES"	20
"stops.txt"	"stop_name"	"LES CAGNIGNONS"	21
"stops.txt"	"stop_name"	"LES COUZES"	22
"stops.txt"	"stop_name"	"LES MÛRIERS"	23
"stops.txt"	"stop_name"	"MAISON COMMUNE"	25

non_ascii_or_non_printable_char

Non ascii or non printable char in ID field.

A value of a field with type ID contains non ASCII or non printable characters. This is not recommended.

You can see more about this notice here.

filename (?) Name of the faulty file.	csvRowNumber (?) Row number of the faulty record.	columnName (?) Name of the column where the error occurred.	fieldValue (?) Faulty value.
"stops.txt"	23	"stop_id"	"LES MÛRIERS"
"stop_times.txt"	25	"stop_id"	"LES MÛRIERS"
"stop_times.txt"	37	"stop_id"	"LES MÛRIERS"
"stop_times.txt"	49	"stop_id"	"LES MÛRIERS"
"stop_times.txt"	61	"stop_id"	"LES MÛRIERS"
"stop_times.txt"	78	"stop_id"	"LES MÛRIERS"
"stop_times.txt"	90	"stop_id"	"LES MÛRIERS"
"stop_times.txt"	102	"stop_id"	"LES MÛRIERS"
"stop_times.txt"	114	"stop_id"	"LES MÛRIERS"

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`.
"1"	2	"1"	"1 Navette GRIMAUD"

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.
"20250516"	"20240701"	"20240831"

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.
"7"	4721
"8"	5012

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"	"ext_pis_code"	4