GTFS Schedule Validation Report

decreasing_or_equal_stop_time_distance

Decreasing or equal shape_dist_traveled in stop_times.txt.

When sorted by stop_times.stop_sequence, two consecutive entries in stop_times.txt should have increasing distance, based on the field shape_dist_traveled. If the values are equal, this is considered as an error.

You can see more about this notice here.

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

tripId (?) The id of the faulty trip.	stopId (?) The id of the faulty stop.	csvRowNumber (?) The row number from `stop_times.txt`.	shapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the faulty record.	stopSequence (?) The faulty record's `stop_times.stop_sequence`.	prevCsvRowNumber (?) The row number from `stop_times.txt` of the previous stop time.	prevShapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the previous stop time.	prevStopSequence (?) The previous record's `stop_times.stop_sequence`.
"36MF-21"	"3981810"	2831	887.6461685641451	2	2830	887.6461685641451	1
"36MF-23"	"3981810"	2879	887.6461685641451	2	2878	887.6461685641451	1
"36MF-11"	"3981810"	2564	887.6461685641451	2	2563	887.6461685641451	1
"36MF-13"	"3981810"	2612	887.6461685641451	2	2611	887.6461685641451	1
"36MF-15"	"3981810"	2660	887.6461685641451	2	2659	887.6461685641451	1
"36MF-17"	"3981810"	2708	887.6461685641451	2	2707	887.6461685641451	1
"36MF-19"	"3981810"	2756	887.6461685641451	2	2755	887.6461685641451	1
"6SAT-18"	"3981810"	4823	887.6461685641451	2	4822	887.6461685641451	1
"6SAT-14"	"3981810"	4781	887.6461685641451	2	4780	887.6461685641451	1
"6SAT-16"	"3981810"	4802	887.6461685641451	2	4801	887.6461685641451	1
"6SAT-20"	"3981810"	4865	887.6461685641451	2	4864	887.6461685641451	1
"6SAT-10"	"3981810"	4739	887.6461685641451	2	4738	887.6461685641451	1
"6SAT-12"	"3981810"	4760	887.6461685641451	2	4759	887.6461685641451	1
"BLUE-28"	"5962867"	7235	0.0	1	7234	3404.4300744147113	0
"BLUE-27"	"5962867"	7222	0.0	1	7221	3404.4300744147113	0
"BLUE-29"	"5962867"	7248	0.0	1	7247	3404.4300744147113	0
"BLUE-20"	"5962867"	7131	0.0	1	7130	3404.4300744147113	0
"BLUE-22"	"5962867"	7157	0.0	1	7156	3404.4300744147113	0
"BLUE-21"	"5962867"	7144	0.0	1	7143	3404.4300744147113	0
"BLUE-24"	"5962867"	7183	0.0	1	7182	3404.4300744147113	0
"BLUE-23"	"5962867"	7170	0.0	1	7169	3404.4300744147113	0
"BLUE-26"	"5962867"	7209	0.0	1	7208	3404.4300744147113	0
"BLUE-25"	"5962867"	7196	0.0	1	7195	3404.4300744147113	0
"BLUE-31"	"5962867"	7287	0.0	1	7286	3404.4300744147113	0
"BLUE-30"	"5962867"	7274	0.0	1	7273	3404.4300744147113	0
"BLUE-33"	"5962867"	7313	0.0	1	7312	3404.4300744147113	0
"BLUE-32"	"5962867"	7300	0.0	1	7299	3404.4300744147113	0
"BLUE-35"	"5962867"	7339	0.0	1	7338	3404.4300744147113	0
"BLUE-34"	"5962867"	7326	0.0	1	7325	3404.4300744147113	0
"BLUE-36"	"5962867"	7352	0.0	1	7351	3404.4300744147113	0
"BLUE-9"	"5962867"	7430	0.0	1	7429	3404.4300744147113	0
"BLUE-7"	"5962867"	7404	0.0	1	7403	3404.4300744147113	0
"BLUE-8"	"5962867"	7417	0.0	1	7416	3404.4300744147113	0
"BLUE-5"	"5962867"	7378	0.0	1	7377	3404.4300744147113	0
"BLUE-6"	"5962867"	7391	0.0	1	7390	3404.4300744147113	0
"BLUE-3"	"5962867"	7261	0.0	1	7260	3404.4300744147113	0
"BLUE-4"	"5962867"	7365	0.0	1	7364	3404.4300744147113	0
"BLUE-1"	"5962867"	6975	0.0	1	6974	3404.4300744147113	0
"BLUE-2"	"5962867"	7118	0.0	1	7117	3404.4300744147113	0
"BLUE-17"	"5962867"	7079	0.0	1	7078	3404.4300744147113	0
"6SAT-4"	"3981810"	4886	887.6461685641451	2	4885	887.6461685641451	1
"BLUE-16"	"5962867"	7066	0.0	1	7065	3404.4300744147113	0
"BLUE-19"	"5962867"	7105	0.0	1	7104	3404.4300744147113	0
"6SAT-2"	"3981810"	4844	887.6461685641451	2	4843	887.6461685641451	1
"BLUE-18"	"5962867"	7092	0.0	1	7091	3404.4300744147113	0
"BLUE-11"	"5962867"	7001	0.0	1	7000	3404.4300744147113	0
"BLUE-10"	"5962867"	6988	0.0	1	6987	3404.4300744147113	0
"BLUE-13"	"5962867"	7027	0.0	1	7026	3404.4300744147113	0
"6SAT-8"	"3981810"	4928	887.6461685641451	2	4927	887.6461685641451	1
"BLUE-12"	"5962867"	7014	0.0	1	7013	3404.4300744147113	0

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.
"routes.txt"	3	"route_short_name"	"Route 7 "
"routes.txt"	10	"route_short_name"	"Route 8 "
"routes.txt"	11	"route_short_name"	"Route 9 "
"routes.txt"	13	"route_short_name"	"Route 2 "

missing_feed_info_date

One of feed_start_date or feed_end_date is specified, but not both.

Even though feed_info.start_date and feed_info.end_date are optional, if one field is provided the second one should also be provided.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	fieldName (?) Either `feed_end_date` or `feed_start_date`.
2	"feed_end_date"

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_end_date"

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_headsign"	"ROUTE 13 UND CAMPUS ALTRU COLUMBIA RD SUPER TARGET MIDTOWN DOWNTOWN"	57
"trips.txt"	"trip_headsign"	"ROUTE 13 UND CAMPUS ALTRU COLUMBIA RD SUPER TARGET MIDTOWN DOWNTOWN"	58
"trips.txt"	"trip_headsign"	"ROUTE 13 UND CAMPUS ALTRU COLUMBIA RD SUPER TARGET MIDTOWN DOWNTOWN"	59
"trips.txt"	"trip_headsign"	"ROUTE 13 UND CAMPUS ALTRU COLUMBIA RD SUPER TARGET MIDTOWN DOWNTOWN"	60
"trips.txt"	"trip_headsign"	"ROUTE 13 UND CAMPUS ALTRU COLUMBIA RD SUPER TARGET MIDTOWN DOWNTOWN"	61

route_long_name_contains_short_name

Long name should not contain short name for a single route.

In routes.txt, route_long_name should not contain the value for route_short_name, because when both are provided, they are often combined by transit applications. Note that only one of the two fields is required. If there is no short name used for a route, use route_long_name only.

Good examples:

route_short_name/route_long_name	Dataset
"N"/"Judah"	Muni San Fransisco
"6"/"ML King Jr Blvd"	Trimet Portland Streetcar
"55"/"Boulevard Saint Laurent"	STM Montreal
"1"/"Rangiora/Cashmere"	Metro Christchurch

Bad examples:

route_short_name/route_long_name
"604"/"604"
"14"/"Route 14"
"2"/"Route 2: Bellows Falls In-Town"

You can see more about this notice here.

routeId (?) The id of the faulty record.	csvRowNumber (?) The row number of the faulty record.	routeShortName (?) The faulty record's `route_short_name`.	routeLongName (?) The faulty record's `route_long_name`.
"3971"	2	"Route 6"	"Route 6"
"3972"	3	"Route 7"	"Route 7"
"3973"	4	"Route 10"	"Route 10"
"3976"	5	"Route 5"	"Route 5"
"3981"	8	"Route 3"	"Route 3"
"3982"	9	"Route 4"	"Route 4"
"3983"	10	"Route 8"	"Route 8"
"3984"	11	"Route 9"	"Route 9"
"3987"	12	"Route 1"	"Route 1"
"3988"	13	"Route 2"	"Route 2"
"4947"	14	"UND Red Route"	"UND Red Route"
"4949"	15	"UND Blue Route"	"UND Blue Route"
"4950"	16	"UND Purple Route"	"UND Purple Route"
"4983"	17	"UND Night Route"	"UND Night Route"

route_short_name_too_long

Short name of a route is too long (more than 12 characters).

You can see more about this notice here.

routeId (?) The id of the faulty record.	csvRowNumber (?) The row number of the faulty record.	routeShortName (?) The faulty record's `route_short_name`.
"4947"	14	"UND Red Route"
"4949"	15	"UND Blue Route"
"4950"	16	"UND Purple Route"
"4983"	17	"UND Night Route"

same_name_and_description_for_route

Same name and description for route.

The GTFS spec defines routes.txt route_desc as:

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

See the GTFS and GTFS Best Practices links below for more examples of how to populate the route_short_name, route_long_name, and route_desc fields.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	routeId (?) The id of the faulty record.	routeDesc (?) The `routes.routes_desc` of the faulty record.	specifiedField (?) Either `route_short_name` or `route_long_name`.
2	"3971"	"Route 6"	"route_short_name"
3	"3972"	"Route 7"	"route_short_name"
4	"3973"	"Route 10"	"route_short_name"
5	"3976"	"Route 5"	"route_short_name"
6	"3977"	"Route 22"	"route_long_name"
8	"3981"	"Route 3"	"route_short_name"
9	"3982"	"Route 4"	"route_short_name"
10	"3983"	"Route 8"	"route_short_name"
11	"3984"	"Route 9"	"route_short_name"
12	"3987"	"Route 1"	"route_short_name"
13	"3988"	"Route 2"	"route_short_name"
14	"4947"	"UND Red Route"	"route_short_name"
15	"4949"	"UND Blue Route"	"route_short_name"
16	"4950"	"UND Purple Route"	"route_short_name"
17	"4983"	"UND Night Route"	"route_short_name"

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.
258	"27550"	"BLUE-1"	6976	"5960009"	"Central Receiving"	[47.920079,-97.082747]	6975	"5962867"	"Odegard"	[47.92136500000001,-97.08601900000001]
258	"27550"	"BLUE-1"	6976	"5960009"	"Central Receiving"	[47.922239,-97.08536400000001]	6975	"5962867"	"Odegard"	[47.92136500000001,-97.08601900000001]

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"calendar_attributes.txt"
"realtime_routes.txt"
"directions.txt"