GTFS Schedule Validation Report

duplicate_route_name

Two distinct routes have either the same route_short_name, the same route_long_name, or the same combination of route_short_name and route_long_name.

All routes of the same route_type with the same agency_id should have unique combinations of route_short_name and route_long_name.

Note that there may be valid cases where routes have the same short and long name, e.g., if they serve different areas. However, different directions must be modeled as the same route.

Example of bad data:

route_id	route_short_name	route_long_name
route1	U1	Southern
route2	U1	Southern

You can see more about this notice here.

csvRowNumber1 (?) The row number of the first occurrence.	routeId1 (?) The id of the the first occurrence.	csvRowNumber2 (?) The row number of the other occurrence.	routeId2 (?) The id of the the other occurrence.	routeShortName (?) Common `routes.route_short_name`.	routeLongName (?) Common `routes.route_long_name`.	routeTypeValue (?) Common `routes.route_type`.	agencyId (?) Common `routes.agency_id`.
2	"19251B"	62	"19587B"	"MLB"	"MetroLink Blue Line"	2	"70006"
3	"19251R"	63	"19587R"	"MLR"	"MetroLink Red Line"	2	"70006"

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.
4	"303-T3"

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.

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

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"	"THEKLA @ EMERSON SB"	2
"stops.txt"	"stop_name"	"WEST FLORISSANT @ BUZZ WESTFALL SB"	3
"stops.txt"	"stop_name"	"SKINKER @ FOREST PARK PARKWAY SB"	4
"stops.txt"	"stop_name"	"MERCY HOSPITAL SOUTH NB"	5
"stops.txt"	"stop_name"	"CIVIC CENTER TRANSIT CENTER"	6
"stops.txt"	"stop_name"	"STLCC FLORISSANT VALLEY"	7
"stops.txt"	"stop_name"	"175 BOULDER INDUSTRIAL"	8
"stops.txt"	"stop_name"	"DEPAUL @ DEPAUL HOSPITAL SB"	9
"stops.txt"	"stop_name"	"ATHLETIC WAY @ RIDER TRAIL SOUTH EB"	10
"stops.txt"	"stop_name"	"CATALAN TRANSIT CENTER"	11
"stops.txt"	"stop_name"	"BROADWAY @ GASCONADE NB"	12
"stops.txt"	"stop_name"	"CATALAN TRANSIT CENTER"	13
"stops.txt"	"stop_name"	"TELEGRAPH @ KINGSTON SB"	14
"stops.txt"	"stop_name"	"LINDBERGH @ ST. FERDINAND WB"	15
"stops.txt"	"stop_name"	"GRAND @ CHOUTEAU SB"	16
"stops.txt"	"stop_name"	"MISSOURI BOTTOM @ OFF RAMP 22B-A I-270 EB"	17
"stops.txt"	"stop_name"	"LUCAS-HUNT @ NATURAL BRIDGE NB"	18
"stops.txt"	"stop_name"	"VIRGINIA @ BATES NB"	19
"stops.txt"	"stop_name"	"VIRGINIA @ BATES SB"	20
"stops.txt"	"stop_name"	"WEST FLORISSANT @ BUZZ WESTFALL PLAZA NB"	21
"stops.txt"	"stop_name"	"14TH STREET @ WASHINGTON SB"	22
"stops.txt"	"stop_name"	"GRAVOIS-HAMPTON TRANSIT CENTER"	23
"stops.txt"	"stop_name"	"GRAVOIS @ HAMPTON WB"	24
"stops.txt"	"stop_name"	"KINGSHIGHWAY @ EICHELBERGER NB"	25
"stops.txt"	"stop_name"	"WATERFORD @ PARKER SB"	26
"stops.txt"	"stop_name"	"FOREST PARK TRANSIT CENTER NB"	27
"stops.txt"	"stop_name"	"FOREST PARK TRANSIT CENTER SB"	28
"stops.txt"	"stop_name"	"OLIVE @ 6TH STREET EB"	29
"stops.txt"	"stop_name"	"LOCUST @ TUCKER WB"	30
"stops.txt"	"stop_name"	"14TH STREET @ LOCUST SB"	31
"stops.txt"	"stop_name"	"MARKET @ 16TH STREET WB"	32
"stops.txt"	"stop_name"	"MARKET @ 20TH STREET EB"	33
"stops.txt"	"stop_name"	"MARKET @ 16TH STREET EB"	34
"stops.txt"	"stop_name"	"CARR @ SELBY PLACE WB"	35
"stops.txt"	"stop_name"	"CHOUTEAU @ 7TH STREET EB"	36
"stops.txt"	"stop_name"	"4TH STREET @ LOCUST NB"	37
"stops.txt"	"stop_name"	"4TH STREET @ WASHINGTON NB"	38
"stops.txt"	"stop_name"	"TUCKER @ CHOUTEAU NB"	39
"stops.txt"	"stop_name"	"TUCKER @ CLARK NB"	40
"stops.txt"	"stop_name"	"TUCKER @ PINE NB"	41
"stops.txt"	"stop_name"	"TUCKER @ COLE NB"	42
"stops.txt"	"stop_name"	"TUCKER @ ST. CHARLES SB"	43
"stops.txt"	"stop_name"	"TUCKER @ PINE SB"	44
"stops.txt"	"stop_name"	"TUCKER @ MARKET NB"	45
"stops.txt"	"stop_name"	"TUCKER @ SPRUCE SB"	46
"stops.txt"	"stop_name"	"BROADWAY @ COLE SB"	47
"stops.txt"	"stop_name"	"BROADWAY @ CONVENTION PLAZA SB"	48
"stops.txt"	"stop_name"	"LOCUST @ 6TH STREET WB"	49
"stops.txt"	"stop_name"	"BROADWAY @ HICKORY SB"	50
"stops.txt"	"stop_name"	"SHAW @ 39TH STREET WB"	51

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.
5066	"117222"	"3348227"	233993	"6049"	"SAINT FRANCOIS @ BOONE WB"	[38.79126,-90.32246]	104.14881511366067
5190	"117224"	"3348351"	237427	"16251"	"NORTH COUNTY TRANSIT CENTER"	[38.77072,-90.27523000000001]	102.53804707063402
5182	"117225"	"3348343"	236995	"16251"	"NORTH COUNTY TRANSIT CENTER"	[38.77072,-90.27523000000001]	102.53804707063402
8386	"117311"	"3351547"	442510	"14263"	"LINCOLN @ 2ND STREET NB"	[38.58983081310934,-89.91035312272926]	130.2186978217995
8375	"117313"	"3351536"	441817	"14263"	"LINCOLN @ 2ND STREET NB"	[38.58983081310934,-89.91035312272926]	130.2186978217995
6610	"117266"	"3349771"	328280	"16414"	"TRADE ACCESS @ TRADEPORT NB"	[38.7979306384037,-90.40644699061934]	164.6508712494172
6606	"117265"	"3349767"	328139	"16414"	"TRADE ACCESS @ TRADEPORT NB"	[38.7979306384037,-90.40644699061934]	164.6508712494172
6631	"117268"	"3349792"	328986	"16417"	"TRADE ACCESS @ TRADEPORT SB"	[38.79788785756712,-90.40667429344477]	164.16833267684552
6645	"117267"	"3349806"	329406	"16417"	"TRADE ACCESS @ TRADEPORT SB"	[38.79788785756712,-90.40667429344477]	164.16833267684552
5971	"117255"	"3349132"	291071	"2456"	"PAGE @ WARSON WB"	[38.69214000000001,-90.395489]	169.51616629093053
5960	"117250"	"3349121"	290202	"2573"	"PAGE @ WARSON EB"	[38.69189,-90.393009]	183.8515337214555
5607	"117238"	"3348768"	263043	"3302"	"DEBALIVIERE @ DEBALIVIERE GARAGE NB"	[38.65158,-90.28466]	242.18046608525734
5787	"117245"	"3348948"	276570	"14133"	"SWINGLEY RIDGE @ CHESTERFIELD CITY HALL SB"	[38.661366726718185,-90.5642736473955]	147.93325564957925
1847	"117126"	"3344701"	68527	"3772"	"WEST FLORISSANT @ UNION SB"	[38.694259,-90.240449]	129.8010330591843
5351	"117231"	"3348512"	246293	"16251"	"NORTH COUNTY TRANSIT CENTER"	[38.77071911741051,-90.27518145186697]	102.45158434581556
5459	"117233"	"3348620"	252853	"16251"	"NORTH COUNTY TRANSIT CENTER"	[38.77072,-90.27523000000001]	102.53804707063402
5458	"117232"	"3348619"	252780	"16251"	"NORTH COUNTY TRANSIT CENTER"	[38.77072,-90.27523000000001]	102.53804707063402
5464	"117234"	"3348625"	253191	"16251"	"NORTH COUNTY TRANSIT CENTER"	[38.77072,-90.27523000000001]	102.53804707063402

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.
1319	"117115"	"3344173"	42964	"8155"	"TELEGRAPH @ BAUMGARTNER NB"	[38.47119601286639,-90.30470666314149]	42963	"15614"	"GEBHARDT @ DELOAK SB"	[38.46965219455664,-90.30853873174655]

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.
"115807"	9503