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`.
15	"1529"	100	"28"	"104"	"Słowiańska - Bora-Komorowskiego -104"	3	"1"
12	"8"	101	"2540"	"104"	"Bora-Komorowskiego - Słowiańska -104"	3	"1"
72	"343"	145	"2533"	"104"	"Bora-Komorowskiego - TPV przez ul. Mosiężną-104"	3	"1"
80	"844"	152	"2532"	"104"	"Bora-Komorowskiego - Rondo Szczecińskie przystanek końc. kier. Centrum -104"	3	"1"

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 greater than 0 but 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 (greater than 0 but 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.
"113"	28387	14.6057	244	28386	14.6057	243	0.024189098813356104
"12"	2858	5.0442	128	2857	5.0442	127	0.024189098813356104
"16"	3875	10.2807	147	3874	10.2807	146	0.024189098813356104
"18"	4306	8.6486	139	4305	8.6486	138	0.024189098813356104
"5"	1213	4.8159	87	1212	4.8159	86	0.024189098813356104
"23"	5296	1.2802	49	5295	1.2802	48	0.024189098813356104
"27"	6177	5.0442	128	6176	5.0442	127	0.024189098813356104
"29"	6676	1.2802	49	6675	1.2802	48	0.024189098813356104
"137"	32169	1.2802	49	32168	1.2802	48	0.024189098813356104
"138"	32538	11.0863	218	32537	11.0863	217	0.024189098813356104
"31"	7358	4.7895	102	7357	4.7895	101	0.024189098813356104
"33"	7840	1.2802	49	7839	1.2802	48	0.024189098813356104
"35"	8584	11.0863	218	8583	11.0863	217	0.024189098813356104
"37"	9302	15.1259	212	9301	15.1259	211	0.024189098813356104
"39"	9755	5.0442	128	9754	5.0442	127	0.024189098813356104
"148"	35151	11.0863	218	35150	11.0863	217	0.024189098813356104
"44"	10773	4.8159	87	10772	4.8159	86	0.024189098813356104
"150"	35627	4.7895	102	35626	4.7895	101	0.024189098813356104
"153"	36444	12.1206	190	36443	12.1206	189	0.024189098813356104
"160"	37621	12.6506	194	37620	12.6506	193	0.024189098813356104
"163"	38412	4.7895	102	38411	4.7895	101	0.024189098813356104
"167"	39270	12.1206	190	39269	12.1206	189	0.024189098813356104
"169"	39954	12.6506	194	39953	12.6506	193	0.024189098813356104
"62"	15286	1.2802	49	15285	1.2802	48	0.024189098813356104
"67"	16598	8.0824	137	16597	8.0824	136	0.024189098813356104
"69"	17239	13.2285	241	17238	13.2285	240	0.024189098813356104
"170"	40206	4.8159	87	40205	4.8159	86	0.024189098813356104
"177"	41796	4.7895	102	41795	4.7895	101	0.024189098813356104
"179"	42216	4.7895	102	42215	4.7895	101	0.024189098813356104
"187"	43796	4.7895	102	43795	4.7895	101	0.024189098813356104
"80"	19585	4.7895	102	19584	4.7895	101	0.024189098813356104
"87"	21432	4.7895	102	21431	4.7895	101	0.024189098813356104
"88"	21685	4.7895	102	21684	4.7895	101	0.024189098813356104
"92"	22739	4.7895	102	22738	4.7895	101	0.024189098813356104
"94"	23714	11.0863	218	23713	11.0863	217	0.024189098813356104
"97"	24513	4.7895	102	24512	4.7895	101	0.024189098813356104
"200"	46900	14.8687	271	46899	14.8687	270	0.024189098813356104
"201"	47259	5.8979	73	47258	5.8979	72	0.024189098813356104
"204"	48758	14.8687	271	48757	14.8687	270	0.024189098813356104
"206"	49269	8.6486	139	49268	8.6486	138	0.024189098813356104
"211"	50401	4.7895	102	50400	4.7895	101	0.024189098813356104
"213"	50828	1.2802	49	50827	1.2802	48	0.024189098813356104
"102"	25566	4.7895	102	25565	4.7895	101	0.024189098813356104
"105"	26540	11.0863	218	26539	11.0863	217	0.024189098813356104
"108"	26942	1.1815	34	26941	1.1815	33	0.024189098813356104
"109"	27330	4.7895	102	27329	4.7895	101	0.024189098813356104

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`.
"112"	27837	1.4572	22	27836	1.4572	21
"112"	28093	12.605	278	28092	12.605	277
"114"	28588	5.7325	142	28587	5.7325	141
"115"	28878	5.6646	142	28877	5.6646	141
"15"	3547	1.4572	22	3546	1.4572	21
"17"	3956	1.4572	22	3955	1.4572	21
"124"	30294	1.4572	22	30293	1.4572	21
"126"	30916	5.5956	39	30915	5.5956	38
"7"	1760	14.0729	259	1759	14.0729	258
"131"	31608	8.4858	169	31607	8.4858	168
"132"	31710	5.5956	39	31709	5.5956	38
"34"	8316	17.8261	325	8315	17.8261	324
"141"	33272	5.7325	142	33271	5.7325	141
"144"	34100	17.8167	290	34099	17.8167	289
"45"	11084	5.6646	142	11083	5.6646	141
"47"	11707	5.6646	142	11706	5.6646	141
"49"	12116	5.6646	142	12115	5.6646	141
"53"	12869	1.4572	22	12868	1.4572	21
"55"	13415	1.4572	22	13414	1.4572	21
"59"	14618	24.5425	357	14617	24.5425	356
"166"	39026	4.9917	89	39025	4.9917	88
"64"	15915	14.4123	258	15914	14.4123	257
"66"	16295	1.4572	22	16294	1.4572	21
"68"	16679	1.4572	22	16678	1.4572	21
"68"	16935	12.5371	278	16934	12.5371	277
"178"	41966	0.862	30	41965	0.862	29
"71"	17809	17.9831	290	17808	17.9831	289
"78"	19226	17.6512	359	19225	17.6512	358
"182"	43121	8.2516	201	43120	8.2516	200
"185"	43459	4.9917	89	43458	4.9917	88
"189"	44221	0.862	30	44220	0.862	29
"82"	20376	5.7325	142	20375	5.7325	141
"84"	20841	14.4802	258	20840	14.4802	257
"190"	44438	5.6646	142	44437	5.6646	141
"192"	44698	4.9917	89	44697	4.9917	88
"93"	23446	21.3617	436	23445	21.3617	435
"220"	52374	5.6646	142	52373	5.6646	141
"104"	26272	19.1911	346	26271	19.1911	345

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

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

feed_expiration_date7_days

Dataset should be valid for at least the next 7 days.

The dataset expiration date defined in feed_info.txt is in seven days or less. At any time, the published GTFS dataset should be valid for at least the next 7 days.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	currentDate (?) Current date (YYYYMMDD format).	feedEndDate (?) Feed end date (YYYYMMDD format).	suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2	"20260203"	"20240903"	"20260210"

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_version"

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"	"_PTC_2023"	104
"routes.txt"	"route_desc"	"przez SP-4 PTC'23"	106
"routes.txt"	"route_desc"	"_PTC"	107
"routes.txt"	"route_desc"	"przez zawarcie_PTC22"	109
"routes.txt"	"route_desc"	"_PTC'23"	157
"routes.txt"	"route_desc"	"_PTC22'"	167
"routes.txt"	"route_desc"	"przez (SP-4) PTC'23"	178
"routes.txt"	"route_desc"	"_PTC22'"	182
"routes.txt"	"route_desc"	"_PTC22'"	186
"routes.txt"	"route_desc"	"#ROLNIK"	187
"routes.txt"	"route_desc"	"przez SP-4 PTC'23"	188
"routes.txt"	"route_long_name"	"AWF - TPV # ROLNIK-117"	191
"routes.txt"	"route_desc"	"# ROLNIK"	191
"routes.txt"	"route_long_name"	"TPV - AWF # ROLNIK-117"	192
"routes.txt"	"route_desc"	"# ROLNIK"	192
"routes.txt"	"route_desc"	"_PTC22'"	193
"routes.txt"	"route_desc"	"_PTC22'"	194
"routes.txt"	"route_desc"	"#ROLNIK"	221

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.
495	"119"	"494"	9587	"158"	"Rondo Sybiraków"	[52.74121789001939,15.2684050798416]	451.10551815820037
495	"119"	"494"	9588	"273"	"Rondo Sybiraków"	[52.74121789001939,15.2684050798416]	381.1976003541388
695	"127"	"694"	13649	"1255"	"Fieldorfa\"\"Nila\"\""	[52.7625086973834,15.2753600478172]	109.4605406349161
697	"129"	"696"	13694	"1255"	"Fieldorfa\"\"Nila\"\""	[52.7625086973834,15.2753600478172]	109.4605406349161
974	"135"	"973"	19194	"454"	"Piaski"	[52.7535095295557,15.233826041221597]	124.70004633515677
128	"43"	"127"	2450	"158"	"Rondo Sybiraków"	[52.74121789001939,15.2684050798416]	451.10551815820037
128	"43"	"127"	2451	"273"	"Rondo Sybiraków"	[52.74121789001939,15.2684050798416]	381.1976003541388
2345	"183"	"2344"	47186	"1255"	"Fieldorfa\"\"Nila\"\""	[52.7625086973834,15.2753600478172]	109.4605406349161

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.
975	"136"	"974"	19202	"68"	"Pluty"	[52.758317695832986,15.253007164287208]	19201	"90"	"Pluty"	[52.758274742612805,15.255424529314004]
1048	"142"	"1047"	20519	"113"	"AWF"	[52.7308570876652,15.22807008711889]	20518	"5"	"AWF"	[52.73114072217399,15.2291496098042]
134	"48"	"133"	2596	"113"	"AWF"	[52.7308570876652,15.22807008711889]	2595	"5"	"AWF"	[52.73114072217399,15.2291496098042]
136	"50"	"135"	2635	"113"	"AWF"	[52.7308570876652,15.22807008711889]	2634	"5"	"AWF"	[52.73114072217399,15.2291496098042]
1560	"165"	"1559"	30707	"164"	"Łagodzin"	[52.68392812061949,15.2496269345284]	30706	"227"	"Łagodzin"	[52.6841026897143,15.2498086971796]
314	"98"	"313"	6327	"164"	"Łagodzin"	[52.68392812061949,15.2496269345284]	6326	"227"	"Łagodzin"	[52.6841026897143,15.2498086971796]

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.
"20260203"	"20240822"	"20240903"

transfer_distance_above_2_km

The transfer distance from stop to stop in transfers.txt is larger than 2 km.

You can see more about this notice here.

csvRowNumber (?) The row number from `transfers.txt` for the faulty entry.	fromStopId (?) The ID of the stop in `from_stop_id`.	toStopId (?) The ID of the stop in `to_stop_id`.	distanceKm (?) The distance between the two stops in km.
271	"1086"	"463"	2.023919299185224
275	"466"	"467"	2.3357500688999426
350	"202"	"1245"	2.6758555856321617
353	"1244"	"485"	2.6595345222704188
421	"293"	"294"	2.3874280333037627
422	"294"	"518"	2.373257995057766
623	"598"	"600"	2.8120462698857374
624	"600"	"597"	3.547962428436728
625	"597"	"577"	3.625596534944048
626	"577"	"608"	2.879167702258207

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"[Content_Types].xml"