GTFS Schedule Validation Report

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`.
"35d81f7b-03dc-4204-9867-1231b1111a12"	3592	63.84	2	4050	63.84	1
"f7e30266-76a6-4fbe-a103-8dd831f3d37b"	1462	7508.43	65	1721	7508.43	64
"7b6088e0-750a-41e6-834c-bf231fd30b4a"	1460	41.02	2	794	41.02	1
"7b6088e0-750a-41e6-834c-bf231fd30b4a"	345	41.02	3	1460	41.02	2

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	"094c008f-aa12-4faf-a438-5b0a4d08e331"
5	"4558a8d1-2d5b-4fba-ab94-438d40590d35"
8	"b2c22fd6-2f16-48cb-b3ca-3c455fcb11e8"
25	"ff9c01f2-ddfd-4ac8-8f71-836f11d34094"

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"	265	"stop_name"	"4936 Raeford Rd/Glensford Cir K "
"stops.txt"	310	"stop_name"	"987 Glensford Dr Raeford Rd Circle K "
"stops.txt"	342	"stop_name"	"1855 Cedar Creek Rd "

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"	"CVS/CFVMC"	368
"routes.txt"	"route_short_name"	"14WKE"	14

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"	"20231113"	"20231229"