GTFS Schedule Validation Report

stop_time_timepoint_without_times

arrival_time or departure_time not specified for timepoint.

Any records with stop_times.timepoint set to 1 must define a value for stop_times.arrival_time and stop_times.departure_time fields.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	tripId (?) The faulty record's id.	stopSequence (?) The faulty record's `stops.stop_sequence`.	specifiedField (?) Either `departure_time` or `arrival_time`.
265	"Glasgow_Connection_loop2_T01"	12	"arrival_time"
265	"Glasgow_Connection_loop2_T01"	12	"departure_time"
266	"Glasgow_Connection_loop2_T01"	13	"arrival_time"
266	"Glasgow_Connection_loop2_T01"	13	"departure_time"
267	"Glasgow_Connection_loop2_T01"	14	"arrival_time"
267	"Glasgow_Connection_loop2_T01"	14	"departure_time"
279	"Glasgow_Connection_loop2_T01"	26	"arrival_time"
279	"Glasgow_Connection_loop2_T01"	26	"departure_time"
283	"Glasgow_Connection_loop2_T01"	30	"arrival_time"
283	"Glasgow_Connection_loop2_T01"	30	"departure_time"

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	"34636"
3	"34638"

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	"20251212"	"20210826"	"20251219"

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.

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

filename (?) The name of the faulty file.	csvRowNumber (?) The row of the faulty record.	fieldName (?) Faulty record's field name.	fieldValue (?) Faulty value.
"shapes.txt"	13178	"shape_id"	" 169699"
"shapes.txt"	13179	"shape_id"	" 169699"
"shapes.txt"	13180	"shape_id"	" 169699"
"shapes.txt"	13181	"shape_id"	" 169699"
"shapes.txt"	13182	"shape_id"	" 169699"
"shapes.txt"	13183	"shape_id"	" 169699"
"shapes.txt"	13184	"shape_id"	" 169699"
"shapes.txt"	13185	"shape_id"	" 169699"
"shapes.txt"	13186	"shape_id"	" 169699"
"shapes.txt"	13187	"shape_id"	" 169699"
"shapes.txt"	13188	"shape_id"	" 169699"
"shapes.txt"	13189	"shape_id"	" 169699"
"shapes.txt"	13190	"shape_id"	" 169699"
"shapes.txt"	13191	"shape_id"	" 169699"
"shapes.txt"	13192	"shape_id"	" 169699"
"shapes.txt"	13193	"shape_id"	" 169699"
"shapes.txt"	13194	"shape_id"	" 169699"
"shapes.txt"	13195	"shape_id"	" 169699"
"shapes.txt"	13196	"shape_id"	" 169699"
"shapes.txt"	13197	"shape_id"	" 169699"
"shapes.txt"	13198	"shape_id"	" 169699"
"shapes.txt"	13199	"shape_id"	" 169699"
"shapes.txt"	13200	"shape_id"	" 169699"
"shapes.txt"	13201	"shape_id"	" 169699"
"shapes.txt"	13202	"shape_id"	" 169699"
"shapes.txt"	13203	"shape_id"	" 169699"
"shapes.txt"	13204	"shape_id"	" 169699"
"shapes.txt"	13205	"shape_id"	" 169699"
"shapes.txt"	13206	"shape_id"	" 169699"
"shapes.txt"	13207	"shape_id"	" 169699"
"shapes.txt"	13208	"shape_id"	" 169699"
"shapes.txt"	13209	"shape_id"	" 169699"
"shapes.txt"	13210	"shape_id"	" 169699"
"shapes.txt"	13211	"shape_id"	" 169699"
"shapes.txt"	13212	"shape_id"	" 169699"
"shapes.txt"	13213	"shape_id"	" 169699"
"shapes.txt"	13214	"shape_id"	" 169699"
"shapes.txt"	13215	"shape_id"	" 169699"
"shapes.txt"	13216	"shape_id"	" 169699"
"shapes.txt"	13217	"shape_id"	" 169699"
"shapes.txt"	13218	"shape_id"	" 169699"
"shapes.txt"	13219	"shape_id"	" 169699"
"shapes.txt"	13220	"shape_id"	" 169699"
"shapes.txt"	13221	"shape_id"	" 169699"
"shapes.txt"	13222	"shape_id"	" 169699"
"shapes.txt"	13223	"shape_id"	" 169699"
"shapes.txt"	13224	"shape_id"	" 169699"
"shapes.txt"	13225	"shape_id"	" 169699"
"shapes.txt"	13226	"shape_id"	" 169699"
"shapes.txt"	13227	"shape_id"	" 169699"

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.
"agency.txt"	2	"agency_id"
"routes.txt"	2	"agency_id"
"routes.txt"	3	"agency_id"
"routes.txt"	4	"agency_id"
"routes.txt"	5	"agency_id"
"routes.txt"	6	"agency_id"

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.
"trips.txt"	"trip_short_name"	"run 1"	2
"trips.txt"	"trip_short_name"	"run 2"	3
"trips.txt"	"trip_short_name"	"run 3"	4
"trips.txt"	"trip_short_name"	"run 4"	5
"trips.txt"	"trip_short_name"	"run 5"	6
"trips.txt"	"trip_short_name"	"run 8"	7
"trips.txt"	"trip_short_name"	"run 9"	8
"trips.txt"	"trip_short_name"	"run 10"	9
"trips.txt"	"trip_short_name"	"run 11"	10
"trips.txt"	"trip_short_name"	"run 6"	11
"trips.txt"	"trip_short_name"	"run 12"	12
"trips.txt"	"trip_short_name"	"run 7"	13
"trips.txt"	"trip_short_name"	"5:25am"	14
"trips.txt"	"trip_short_name"	"6:25am"	15
"trips.txt"	"trip_short_name"	"6:15pm"	16
"trips.txt"	"trip_short_name"	"8:27pm"	17
"trips.txt"	"trip_short_name"	"5:40am"	18
"trips.txt"	"trip_short_name"	"7:10am"	19
"trips.txt"	"trip_short_name"	"5:30pm"	20
"trips.txt"	"trip_short_name"	"7:00pm"	21
"trips.txt"	"trip_short_name"	"run 1"	22
"trips.txt"	"trip_short_name"	"run 2"	23
"trips.txt"	"trip_short_name"	"run 3"	24
"trips.txt"	"trip_short_name"	"run 4"	25
"trips.txt"	"trip_short_name"	"run 5"	26
"trips.txt"	"trip_short_name"	"run 6"	27
"trips.txt"	"trip_short_name"	"run 7"	28
"trips.txt"	"trip_short_name"	"run 8"	29
"trips.txt"	"trip_short_name"	"run 9"	30
"trips.txt"	"trip_short_name"	"run 10"	31
"trips.txt"	"trip_short_name"	"run 11"	32
"trips.txt"	"trip_short_name"	"8:10am"	33
"trips.txt"	"trip_short_name"	"530AM"	34
"trips.txt"	"trip_short_name"	"724PM"	35
"trips.txt"	"trip_short_name"	"904PM"	36

stop_has_too_many_matches_for_shape

Stop entry that has many potential matches to the trip's path of travel, as defined by the shape entry in shapes.txt.

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.	matchCount (?) The number of matches for the stop that is referred to.
33	"169699"	"4947468"	704	"107"	"Cecil College - Main Campus"	[39.641040000000004,-75.95702]	25
18	"114725 169690"	"4947461"	242	"107"	"Cecil College - Main Campus"	[39.641040000000004,-75.95702]	25
15	"114724 169689"	"4947462"	233	"107"	"Cecil College - Main Campus"	[39.641040000000004,-75.95702]	25

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.
34	"Route2"	"7058473"	707	"1000"	"214 North St."	[39.610200000015425,-75.83046]	706	"2569564"	"Union Hospital"	[39.60896688225466,-75.83110977730347]
24	"77110 169695"	"2361457"	345	"6"	"Redner's - Whitehall Rd. (Call in stop)"	[39.58952351427624,-75.82551038996455]	344	"26"	"Skipjack Court (3)"	[39.58945432147793,-75.82875932745618]

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"	"20190812"	"20210930"

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.
"114726 169691"	6254
"114727 169692"	7212
"77111 169696"	10638

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.
"trips.txt"	"block_name"	11