GTFS Schedule Validation Report

equal_shape_distance_diff_coordinates

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 the 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 different coordinates indicate an error.

You can see more about this notice here.

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

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.
"shp_route_3"	303	0.0	2	302	0.0	1	66.85425029591616
"shp_route_3"	311	0.7	10	310	0.7	9	70.02392550858983
"shp_route_3"	321	1.8	20	320	1.8	19	57.643501002136375
"shp_route_3"	322	1.8	21	321	1.8	20	33.25954355068874
"shp_route_3"	323	1.8	22	322	1.8	21	32.54631601162976
"shp_route_3"	324	1.8	23	323	1.8	22	25.718801059285333
"shp_route_3"	325	1.8	24	324	1.8	23	34.58894137056891
"shp_route_3"	326	1.8	25	325	1.8	24	44.294773363543065
"shp_route_3"	327	1.8	26	326	1.8	25	36.0331094687608
"shp_route_3"	328	1.8	27	327	1.8	26	54.69759193717777
"shp_route_3"	329	1.8	28	328	1.8	27	75.75194603157352
"shp_route_3"	340	2.9	39	339	2.9	38	57.05880760030659
"shp_route_3"	341	2.9	40	340	2.9	39	23.313162427396698
"shp_route_3"	342	2.9	41	341	2.9	40	35.39310955090253
"shp_route_3"	343	2.9	42	342	2.9	41	26.755580087959984
"shp_route_3"	344	2.9	43	343	2.9	42	37.91560649400656
"shp_route_3"	345	2.9	44	344	2.9	43	36.98292337526034
"shp_route_3"	352	3.5	51	351	3.5	50	38.70885027990761
"shp_route_3"	354	3.6	53	353	3.6	52	25.985930382252086
"shp_route_3"	359	4.0	58	358	4.0	57	37.9097656947191
"shp_route_3"	360	4.0	59	359	4.0	58	26.461479171680608
"shp_route_3"	361	4.0	60	360	4.0	59	19.501604339068226
"shp_route_3"	362	4.0	61	361	4.0	60	36.2926843365753
"shp_route_3"	363	4.0	62	362	4.0	61	33.70155186934421
"shp_route_3"	364	4.0	63	363	4.0	62	29.927335768973233
"shp_route_3"	365	4.0	64	364	4.0	63	60.06816549706614
"shp_route_3"	367	4.1	66	366	4.1	65	26.729642839984667
"shp_route_3"	371	4.5	70	370	4.5	69	73.62130229279045
"shp_route_3"	376	4.9	75	375	4.9	74	20.719957764647667
"shp_route_3"	390	6.2	89	389	6.2	88	11.490412594070888
"shp_route_3"	400	7.1	99	399	7.1	98	48.111959908457166
"shp_route_3"	402	7.2	101	401	7.2	100	74.42134629146516
"shp_route_3"	403	7.2	102	402	7.2	101	34.949920768036456
"shp_route_3"	404	7.2	103	403	7.2	102	28.922775491088338
"shp_route_3"	405	7.2	104	404	7.2	103	31.12420189958122
"shp_route_3"	406	7.2	105	405	7.2	104	36.3484110738934
"shp_route_3"	407	7.2	106	406	7.2	105	34.48520908466014
"shp_route_3"	408	7.2	107	407	7.2	106	27.673508684137627
"shp_route_3"	409	7.2	108	408	7.2	107	36.07137060828895
"shp_route_3"	410	7.2	109	409	7.2	108	68.14396632245973
"shp_route_3"	425	8.6	124	424	8.6	123	74.67906144301477
"shp_route_2"	228	0.4	6	227	0.4	5	63.90521123738617
"shp_route_2"	232	0.7	10	231	0.7	9	19.393447323909506
"shp_route_2"	233	0.7	11	232	0.7	10	43.10197886322431
"shp_route_2"	234	0.7	12	233	0.7	11	10.47687330344968
"shp_route_2"	235	0.7	13	234	0.7	12	9.210679371617042
"shp_route_2"	236	0.7	14	235	0.7	13	66.75237490530539
"shp_route_2"	255	2.9	33	254	2.9	32	41.54666228257498
"shp_route_2"	266	3.9	44	265	3.9	43	66.01113853638932
"shp_route_2"	267	3.9	45	266	3.9	44	15.342718434354552

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.
"shp_route_6"	848	6.4	97	847	6.4	96	0.5928402398428576

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

leading_or_trailing_whitespaces

The value in CSV file has leading or trailing whitespaces.

This notice is emitted for values protected with double quotes since whitespaces for non-protected values are trimmed automatically by CSV parser.

The validator strips whitespaces from protected values. We do not see any use case when such a whitespace may be needed. On the other hand, some real-world feeds use trailing whitespaces for some values and omit them for the others. This is causing the largest problem when a primary key and a foreign key differ just by a whitespace: it is clear that they are intended to be the same, that is why we always strip whitespaces.

You can see more about this notice here.

filename (?) The name of the faulty file.	csvRowNumber (?) The row of the faulty record.	fieldName (?) Faulty record's field name.	fieldValue (?) Faulty value.
"stops.txt"	10	"stop_name"	"Jefferson & E.12th "
"stops.txt"	28	"stop_name"	"W. 14th & Olive "
"stops.txt"	118	"stop_desc"	"Catfish King, Patterson's Camera Shop, "
"stops.txt"	150	"stop_desc"	"Southwest Center, W&W Auto Sales, "
"stops.txt"	172	"stop_name"	"Arkansas Blvd & Meadowview "
"stops.txt"	177	"stop_name"	"New Boston & Waymeadow "
"stops.txt"	216	"stop_desc"	"Wake Village Elementary School, Wake Village Fire Dept. "
"stops.txt"	218	"stop_name"	"Richmond West Side & Corporate "
"stops.txt"	228	"stop_name"	"Kings Hwy & New Boston "

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"

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"	"MLK & E. 9th"	2
"stops.txt"	"stop_name"	"SUPER WALMART"	206

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.
132	"shp_route_6"	"TRP5A1"	203	"STMICHAELRICHMOND"	"St. Michael & Richmond"	[33.45660187078544,-94.0871362743395]	202	"RICHMONDSTMICHAELDR"	"Richmond & St. Michael Dr."	[33.45654470369504,-94.08708033184365]

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"	"20231201"	"20251231"