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.
50	"191092-2020-MultScol-Mercredi-00"	"3-1-127"	51	"191095-2020-MultScol-Mercredi-00"	"3-1-127"	"LMZ4"	"20231129"
52	"191098-2020-MulScol-L-Ma-J-V-00"	"2-1-127"	53	"191101-2020-MulScol-L-Ma-J-V-00"	"2-1-127"	"LMZ4"	"20231123"

stop_time_with_arrival_before_previous_departure_time

Backwards time travel between stops in stop_times.txt

For a given trip_id, the arrival_time of (n+1)-th stoptime in sequence must not precede the departure_time of n-th stoptime in sequence in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	prevCsvRowNumber (?) The row of the previous stop time.	tripId (?) The trip_id associated to the faulty record.	arrivalTime (?) Arrival time at the faulty record.	departureTime (?) Departure time at the previous stop time.
9064	9063	"190954-2020-MultScol-Mercredi-00"	"08:00:00"	"08:17:00"

fast_travel_between_consecutive_stops

A transit vehicle moves too fast between two consecutive stops.

The speed threshold depends on route type:

Route type	Description	Threshold, km/h
0	Light rail	100
1	Subway	150
2	Rail	500
3	Bus	150
4	Ferry	80
5	Cable tram	30
6	Aerial lift	50
7	Funicular	50
11	Trolleybus	150
12	Monorail	150
-	Unknown	200

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the problematic trip.	tripId (?) `trip_id` of the problematic trip.	routeId (?) `route_id` of the problematic trip.	speedKph (?) Travel speed (km/h).	distanceKm (?) Distance between stops (km).	csvRowNumber1 (?) The row number of the first stop time.	stopSequence1 (?) `stop_sequence` of the first stop.	stopId1 (?) `stop_id` of the first stop.	stopName1 (?) `stop_name` of the first stop.	departureTime1 (?) `departure_time` of the first stop.	csvRowNumber2 (?) The row number of the second stop time.	stopSequence2 (?) `stop_sequence` of the second stop.	stopId2 (?) `stop_id` of the second stop.	stopName2 (?) `stop_name` of the second stop.	arrivalTime2 (?) `arrival_time` of the second stop.
27	"b5009c9e-609a-490d-9a64-6d593466f0d7"	"ECOLE-CHENIERES-LAIX"	244.80202730538153	12.240101365269076	772	1	"stp-2224a-r"	"Place G.Mohy"	"08:30:00"	773	2	"stp-2219ar"	"Château"	"08:32:00"

fast_travel_between_far_stops

A transit vehicle moves too fast between two far stops.

Two stops are considered "far" if they are more than 10 km apart. This normally indicates a more serious problem than too fast travel between consecutive stops.

The speed threshold depends on route type and are the same as fast_travel_between_consecutive_stops.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the problematic trip.	tripId (?) `trip_id` of the problematic trip.	routeId (?) `route_id` of the problematic trip.	speedKph (?) Travel speed (km/h).	distanceKm (?) Distance between stops (km).	csvRowNumber1 (?) The row number of the first stop time.	stopSequence1 (?) `stop_sequence` of the first stop.	stopId1 (?) `stop_id` of the first stop.	stopName1 (?) `stop_name` of the first stop.	departureTime1 (?) `departure_time` of the first stop.	csvRowNumber2 (?) The row number of the second stop time.	stopSequence2 (?) `stop_sequence` of the second stop.	stopId2 (?) `stop_id` of the second stop.	stopName2 (?) `stop_name` of the second stop.	arrivalTime2 (?) `arrival_time` of the second stop.
27	"b5009c9e-609a-490d-9a64-6d593466f0d7"	"ECOLE-CHENIERES-LAIX"	244.80202730538153	12.240101365269076	772	1	"stp-2224a-r"	"Place G.Mohy"	"08:30:00"	773	2	"stp-2219ar"	"Château"	"08:32:00"

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"	184	"stop_name"	"Haut Place Darche "

missing_recommended_column

A recommended column is missing in the input file.

You can see more about this notice here.

filename (?) The name of the faulty file.	fieldName (?) The name of the missing column.
"stop_times.txt"	"timepoint"

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.

filename (?) Name of the faulty file.	fieldName (?) Name of the faulty field.	fieldValue (?) Faulty value.	csvRowNumber (?) The row number of the faulty record.
"routes.txt"	"route_short_name"	"CEG2 bis"	36
"stops.txt"	"stop_name"	"LE FAIL"	29
"stops.txt"	"stop_name"	"LE FAIL"	30
"stops.txt"	"stop_name"	"LE FAIL"	31
"stops.txt"	"stop_name"	"centre"	294
"stops.txt"	"stop_name"	"centre"	295
"stops.txt"	"stop_name"	"centre"	296
"stops.txt"	"stop_name"	"centre"	324
"stops.txt"	"stop_name"	"centre"	325
"stops.txt"	"stop_name"	"centre"	326
"stops.txt"	"stop_name"	"centre"	336
"stops.txt"	"stop_name"	"centre"	337
"stops.txt"	"stop_name"	"centre"	338
"stops.txt"	"stop_name"	"131ème RI"	534
"stops.txt"	"stop_name"	"131ème RI"	535
"stops.txt"	"stop_name"	"131ème RI"	536
"trips.txt"	"trip_headsign"	"ECOLE LAIX-CHENIERES"	27
"trips.txt"	"trip_headsign"	"ECOLE LAIX-CHENIERES"	248

non_ascii_or_non_printable_char

Non ascii or non printable char in ID field.

A value of a field with type ID contains non ASCII or non printable characters. This is not recommended.

You can see more about this notice here.

filename (?) Name of the faulty file.	csvRowNumber (?) Row number of the faulty record.	columnName (?) Name of the column where the error occurred.	fieldValue (?) Faulty value.
"trips.txt"	64	"block_id"	"Navette Récollets"
"trips.txt"	65	"block_id"	"Navette Récollets"
"trips.txt"	296	"block_id"	"Navette Récollets"
"trips.txt"	297	"block_id"	"Navette Récollets"

route_color_contrast

Insufficient route color contrast.

A route's color and route_text_color should be contrasting.

You can see more about this notice here.

routeId (?) The id of the faulty record.	csvRowNumber (?) The row number of the faulty record.	routeColor (?) The faulty record's HTML route color.	routeTextColor (?) The faulty record's HTML route text color.
"STA"	31	"#2B0000"	"#1B1A1A"
"TAD1"	32	"#000000"	"#1E1D1D"
"TAD2"	33	"#000000"	"#1E1C1C"

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`.
"STA"	31	"STA"	"STA"

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`.
"ECOLE-CHENIERES-LAIX"	41	"Ecole chenieres laix"