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.
"35590"	6633	10375.3	196	6632	10375.3	195	0.06193557554384503

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`.
"35589"	14561	6857.9	248	14560	6857.9	247

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.
9	"49715"
7	"26015"
22	"250"
26	"251"
27	"252"
25	"253"
8	"254"
24	"24150"
28	"255"
29	"376"
18	"377"
4	"257"
16	"24152"
30	"433"
3	"258"
14	"24153"
21	"434"
2	"259"
13	"26014"
15	"435"
5	"437"
19	"438"
23	"439"
20	"1439"
11	"260"
12	"26285"
17	"266"
6	"1441"
10	"49640"

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"	81	"stop_name"	" Lenkimai II"

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.

Even though the column timepoint is optional in stop_times.txt according to the specification, stop_times.timepoint should not be empty when provided.

You can see more about this notice here.

Only the first 50 of 718 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	"41891"	1
3	"41891"	2
4	"41891"	3
5	"41891"	4
6	"41891"	5
7	"41891"	6
8	"41891"	7
9	"41891"	8
10	"41891"	9
11	"42663"	1
12	"42663"	2
13	"42663"	3
14	"42663"	4
15	"42663"	5
16	"42663"	6
17	"42663"	7
18	"42663"	8
19	"42663"	9
20	"42663"	10
21	"42663"	11
22	"42663"	12
23	"42663"	13
24	"42663"	14
25	"42663"	15
26	"42665"	1
27	"42665"	2
28	"42665"	3
29	"42665"	4
30	"42665"	5
31	"42665"	6
32	"42665"	7
33	"42665"	8
34	"42665"	9
35	"47584"	1
36	"47584"	2
37	"47584"	3
38	"47584"	4
39	"47584"	5
40	"47584"	6
41	"47584"	7
42	"47584"	8
43	"47584"	9
44	"47584"	10
45	"47584"	11
46	"47584"	12
47	"47584"	13
48	"47584"	14
49	"47584"	15
50	"47584"	16
51	"47584"	17

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.
"20250116"	"20150608"	"20240628"

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