GTFS Schedule Validation Report

block_trips_with_overlapping_stop_times

Trips with the same block id have overlapping stop times.

You can see more about this notice here.

csvRowNumberA (?) The row number from `trips.txt` of the first faulty trip.	tripIdA (?) The id of first faulty trip.	serviceIdA (?) The service id of the first faulty trip.	csvRowNumberB (?) The row number from `trips.txt` of the second faulty trip.	tripIdB (?) The id of the other faulty trip.	serviceIdB (?) The service id of the other faulty trip.	blockId (?) The `trips.block_id` of the overlapping trip.	intersection (?) The overlapping period.
210	"800209-SCH-1909-Blocking-Weekday-30"	"SCH-1909-Blocking-Weekday-30"	93	"800091-SCH-1909-Blocking-Weekday-30"	"SCH-1909-Blocking-Weekday-30"	"1"	"20210701"
210	"800209-SCH-1909-Blocking-Weekday-30"	"SCH-1909-Blocking-Weekday-30"	211	"800210-SCH-1909-Blocking-Weekday-30"	"SCH-1909-Blocking-Weekday-30"	"1"	"20210701"
93	"800091-SCH-1909-Blocking-Weekday-30"	"SCH-1909-Blocking-Weekday-30"	211	"800210-SCH-1909-Blocking-Weekday-30"	"SCH-1909-Blocking-Weekday-30"	"1"	"20210701"
222	"800221-SCH-1909-Blocking-Weekday-30"	"SCH-1909-Blocking-Weekday-30"	223	"800222-SCH-1909-Blocking-Weekday-30"	"SCH-1909-Blocking-Weekday-30"	"1"	"20210701"
228	"800227-SCH-1909-Blocking-Weekday-30"	"SCH-1909-Blocking-Weekday-30"	229	"800228-SCH-1909-Blocking-Weekday-30"	"SCH-1909-Blocking-Weekday-30"	"1"	"20210701"
508	"800509-SCH-1909-Blocking-Weekday-30"	"SCH-1909-Blocking-Weekday-30"	749	"800758-SCH-1909-Blocking-Weekday-30"	"SCH-1909-Blocking-Weekday-30"	"2"	"20210701"
218	"800217-SCH-1909-Blocking-Weekday-30"	"SCH-1909-Blocking-Weekday-30"	7	"800004-SCH-1909-Blocking-Weekday-30"	"SCH-1909-Blocking-Weekday-30"	"5"	"20210701"
408	"800407-SCH-1909-Blocking-Weekday-30"	"SCH-1909-Blocking-Weekday-30"	409	"800408-SCH-1909-Blocking-Weekday-30"	"SCH-1909-Blocking-Weekday-30"	"5"	"20210701"
220	"800219-SCH-1909-Blocking-Weekday-30"	"SCH-1909-Blocking-Weekday-30"	114	"800112-SCH-1909-Blocking-Weekday-30"	"SCH-1909-Blocking-Weekday-30"	"10"	"20210701"

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	"SCH-1909-Blocking-Weekday-30"

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.
"feed_info.txt"	2	"feed_start_date"
"feed_info.txt"	2	"feed_end_date"
"fare_attributes.txt"	2	"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.
"stops.txt"	"stop_name"	"70th & SPW"	9

stop_too_far_from_shape

Stop too far from trip shape.

Per GTFS Best Practices, route alignments (in shapes.txt) should be within 100 meters of stop locations which a trip serves. 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.	geoDistanceToShape (?) Distance from stop to shape.
420	"Ylw0001"	"800420-SCH-1909-Blocking-Weekday-30"	923	"755005"	"SPLC North Lot"	[47.670719,-122.271126]	153.13350248032398

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.
2	"25200"	"NE 45th St & Union Bay Pl NE"
4	"29920"	"NE 45th St & Mary Gates Memorial Dr NE"
6	"755003"	"UW Link Station / UW Link Station"
12	"755011"	"SPLC South Lot"

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.
2	"Purp0002"	"799999-SCH-1909-Blocking-Weekday-30"	3	"755000"	"Helen Ln / River Circle"	[47.66354226206545,-122.28296558712456]	2	"755009"	"43rd St / Roosevelt Way"	[47.659847,-122.317473]

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"	"20210701"	"20240701"

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.
"feed_info.txt"	"feed_id"	1
"stop_times.txt"	"departure_buffer"	6
"trips.txt"	"drt_advance_book_min"	8
"trips.txt"	"peak_offpeak"	9
"trips.txt"	"boarding_type"	10
"fare_attributes.txt"	"youth_price"	6
"fare_attributes.txt"	"senior_price"	7