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 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.
"TVX_IB_89_32_AM"	6136	0.0	1	6135	0.0	0	0.3078682218606421
"TVX_IB_89_32_AM"	6139	16.0	4	6138	16.0	3	0.48528839504624977
"TVS_IB_89_60"	2174	0.0	1	2173	0.0	0	0.3078682218606421
"TVS_IB_89_60"	2177	16.0	4	2176	16.0	3	0.48528839504624977
"TVL_IB_89_32_PM"	3965	0.0	1	3964	0.0	0	0.3078682218606421
"TVL_IB_89_32_PM"	3968	16.0	4	3967	16.0	3	0.48528839504624977
"TVL_IB_89_32_PM"	4512	23392.0	548	4511	23392.0	547	0.33363482910902514
"TVX_IB_89_32_PM"	6524	0.0	1	6523	0.0	0	0.3078682218606421
"TVX_IB_89_32_PM"	6527	16.0	4	6526	16.0	3	0.48528839504624977
"TVL_IB_89_32_AM"	4594	0.0	1	4593	0.0	0	0.3078682218606421
"TVL_IB_89_32_AM"	4597	16.0	4	4596	16.0	3	0.48528839504624977
"TVL_IB_89_32_AM"	5141	23392.0	548	5140	23392.0	547	0.33363482910902514

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	"weekend_light"
3	"weekday_light"

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.
"routes.txt"	"route_desc"	"30 IDA"	2
"routes.txt"	"route_desc"	"40 SV"	3

same_name_and_description_for_stop

Same name and description for stop.

The GTFS spec defines stops.txt stop_description as:

Description of the location that provides useful, quality information. Do not simply duplicate the name of the location.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	stopId (?) The id of the faulty record.	stopDesc (?) The faulty record's `stop_desc`.
88	"1:Pearl & Jean"	"Pearl & Jean"
94	"1:Maple Way"	"Maple Way"

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	stopId (?) The id of the faulty stop.	stopName (?) The name of the faulty stop.
22	"0:Barn_Jackson"	"Barn"
73	"0:Barn_Etna"	"Barn"
74	"0:Barn_Driggs"	"Barn"

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.
"20251212"	"20230125"	"20230131"

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.
"TVS_DH_BARN_60"	2
"TVC_DH_BARN_8"	80
"TVL_DH_BARN_32"	138
"TVL_DH_32_BARN"	175
"TVS_DH_60_BARN"	243
"TVC_DH_9_BARN"	401
"SVC_DH_9_BARN"	459
"SVC_DH_BARN_8"	517
"TOS_32_49"	3118

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.
"stops.txt"	"vehicle_type"	9