GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 5.0.1 at 2025-01-23T12:49:01Z,
for the dataset file:///tmp/1_in.zip. No country code was provided.

Use this report alongside our documentation.

A new version of the Canonical GTFS Schedule validator is available! Please update to get the latest/best validation results.

Summary

Agencies included

Feed Info

Publisher Name:
N/A
Publisher URL:
N/A
Feed Language:
N/A

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. routes.txt
  5. shapes.txt
  6. stop_times.txt
  7. stops.txt
  8. trips.txt

Counts

  • Agencies: 1
  • Blocks: 49
  • Routes: 12
  • Shapes: 34
  • Stops: 545
  • Trips: 386

Specification Compliance report

699 notices reported (0 errors, 699 warnings, 0 infos)

Notice Code Severity Total
expired_calendar WARNING 1

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.
21 "EVI2024-12_FER-7-jours-20"
fast_travel_between_consecutive_stops WARNING 5

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.
293 "10-12-EVI2024-12_SCO-7-jours-20" "12-237" 187.64546233177242 3.127424372196207 9155 38 "55CVN1" "LA VILLE DU NANT" "19:56:00" 9156 39 "55CLE1" "CHATEL EGLISE" "19:56:00"
306 "10-12-EVI2024-12_VAC-7-jours-20" "12-237" 187.64546233177242 3.127424372196207 9664 38 "55CVN1" "LA VILLE DU NANT" "19:56:00" 9665 39 "55CLE1" "CHATEL EGLISE" "19:56:00"
285 "10-12-EVI2024-12_FER-7-jours-20" "12-237" 187.64546233177242 3.127424372196207 8839 38 "55CVN1" "LA VILLE DU NANT" "19:56:00" 8840 39 "55CLE1" "CHATEL EGLISE" "19:56:00"
305 "11-12-EVI2024-12_VAC-7-jours-20-1111100" "12-237" 187.64546233177242 3.127424372196207 9624 38 "55CVN1" "LA VILLE DU NANT" "18:56:00" 9625 39 "55CLE1" "CHATEL EGLISE" "18:56:00"
292 "11-12-EVI2024-12_SCO-7-jours-20-1111100" "12-237" 187.64546233177242 3.127424372196207 9115 38 "55CVN1" "LA VILLE DU NANT" "18:56:00" 9116 39 "55CLE1" "CHATEL EGLISE" "18:56:00"
leading_or_trailing_whitespaces WARNING 46

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.
"trips.txt" 2 "trip_headsign" " P+R STADE - NEUVECELLE MILLY"
"trips.txt" 3 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 4 "trip_headsign" " P+R STADE - NEUVECELLE MILLY"
"trips.txt" 5 "trip_headsign" " P+R STADE - NEUVECELLE MILLY"
"trips.txt" 6 "trip_headsign" " P+R STADE - NEUVECELLE MILLY"
"trips.txt" 7 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 8 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 9 "trip_headsign" " P+R STADE - NEUVECELLE MILLY"
"trips.txt" 10 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 11 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 12 "trip_headsign" " P+R STADE - NEUVECELLE MILLY"
"trips.txt" 13 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 14 "trip_headsign" " P+R STADE - NEUVECELLE MILLY"
"trips.txt" 15 "trip_headsign" " P+R STADE - NEUVECELLE MILLY"
"trips.txt" 16 "trip_headsign" " P+R STADE - NEUVECELLE MILLY"
"trips.txt" 17 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 18 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 19 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 20 "trip_headsign" " P+R STADE - NEUVECELLE MILLY"
"trips.txt" 21 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 168 "trip_headsign" " P+R STADE - NEUVECELLE MILLY"
"trips.txt" 169 "trip_headsign" " P+R STADE - NEUVECELLE MILLY"
"trips.txt" 170 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 171 "trip_headsign" " P+R STADE - NEUVECELLE MILLY"
"trips.txt" 172 "trip_headsign" " P+R STADE - NEUVECELLE MILLY"
"trips.txt" 173 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 174 "trip_headsign" " P+R STADE - NEUVECELLE MILLY"
"trips.txt" 175 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 176 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 177 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 178 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 179 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 180 "trip_headsign" " P+R STADE - NEUVECELLE MILLY"
"trips.txt" 181 "trip_headsign" " P+R STADE - NEUVECELLE MILLY"
"trips.txt" 182 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 183 "trip_headsign" " P+R STADE - NEUVECELLE MILLY"
"trips.txt" 184 "trip_headsign" " P+R STADE - NEUVECELLE MILLY"
"trips.txt" 185 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 186 "trip_headsign" " P+R STADE - NEUVECELLE MILLY"
"trips.txt" 187 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 188 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 189 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 190 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 191 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 192 "trip_headsign" " EMBARCADERE -GARE ROUTIERE - GARE SNCF"
"trips.txt" 193 "trip_headsign" " P+R STADE - NEUVECELLE MILLY"
missing_recommended_column WARNING 1

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_field WARNING 12

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.
"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"
"routes.txt" 7 "agency_id"
"routes.txt" 8 "agency_id"
"routes.txt" 9 "agency_id"
"routes.txt" 10 "agency_id"
"routes.txt" 11 "agency_id"
"routes.txt" 12 "agency_id"
"routes.txt" 13 "agency_id"
missing_recommended_file WARNING 1

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 WARNING 630

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 630 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" "PRE DE L' ABBAYE" 2
"stops.txt" "stop_name" "PRE DE L' ABBAYE" 3
"stops.txt" "stop_name" "LA RIVE" 6
"stops.txt" "stop_name" "LA RIVE" 7
"stops.txt" "stop_name" "CLOS BURDET" 10
"stops.txt" "stop_name" "CLOS BURDET" 11
"stops.txt" "stop_name" "VIEIL AMPHION" 14
"stops.txt" "stop_name" "VIEIL AMPHION" 15
"stops.txt" "stop_name" "RIPAILLE COMBE" 17
"stops.txt" "stop_name" "RIPAILLE COMBE" 18
"stops.txt" "stop_name" "PICARD THONON" 21
"stops.txt" "stop_name" "PICARD THONON" 22
"stops.txt" "stop_name" "GRANDE RIVE" 23
"stops.txt" "stop_name" "GRANDE RIVE" 24
"stops.txt" "stop_name" "CHEZ BRUCHON" 25
"stops.txt" "stop_name" "CHEZ BRUCHON" 26
"stops.txt" "stop_name" "PALAIS DES FESTIVITES" 27
"stops.txt" "stop_name" "PALAIS DES FESTIVITES" 28
"stops.txt" "stop_name" "ROUTE DU STADE" 29
"stops.txt" "stop_name" "ROUTE DU STADE" 30
"stops.txt" "stop_name" "ROUTE DU STADE" 31
"stops.txt" "stop_name" "ROUTE DU STADE" 32
"stops.txt" "stop_name" "COLLEGE CHAMPAGNE" 35
"stops.txt" "stop_name" "COLLEGE CHAMPAGNE" 36
"stops.txt" "stop_name" "CHEZ GRANJUX" 39
"stops.txt" "stop_name" "CHEZ GRANJUX" 40
"stops.txt" "stop_name" "LUGRIN CHEZ CACHAT" 41
"stops.txt" "stop_name" "LUGRIN CHEZ CACHAT" 42
"stops.txt" "stop_name" "THUYSET EST" 43
"stops.txt" "stop_name" "THUYSET EST" 44
"stops.txt" "stop_name" "CIMETIERE D'EVIAN" 45
"stops.txt" "stop_name" "CIMETIERE D'EVIAN" 46
"stops.txt" "stop_name" "SHOP'IN PUBLIER" 47
"stops.txt" "stop_name" "SHOP'IN PUBLIER" 48
"stops.txt" "stop_name" "COLLEGE DES RIVES" 51
"stops.txt" "stop_name" "LES CHAVANNES" 54
"stops.txt" "stop_name" "LES CHAVANNES" 55
"stops.txt" "stop_name" "DUCS DE SAVOIE" 58
"stops.txt" "stop_name" "DUCS DE SAVOIE" 59
"stops.txt" "stop_name" "CITE DE L'EAU" 60
"stops.txt" "stop_name" "CITE DE L'EAU" 61
"stops.txt" "stop_name" "EVIAN - CHEZ BAVOUX" 62
"stops.txt" "stop_name" "EVIAN - CHEZ BAVOUX" 63
"stops.txt" "stop_name" "ECOLE DE MAXILLY" 64
"stops.txt" "stop_name" "ECOLE DE MAXILLY" 65
"stops.txt" "stop_name" "EVIAN EGLISE" 66
"stops.txt" "stop_name" "EVIAN HÔPITAL" 67
"stops.txt" "stop_name" "EVIAN HOPITAL" 68
"stops.txt" "stop_name" "COMTE ROUGE" 78
"stops.txt" "stop_name" "COMTE ROUGE" 79
route_long_name_contains_short_name WARNING 1

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`.
"TAD-237" 12 "TAD" "TAD"
unexpected_enum_value WARNING 1

unexpected_enum_value

An enum has an unexpected value.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row number of the faulty record. fieldName (?) The name of the field where the error occurred. fieldValue (?) Faulty value.
"routes.txt" 12 "route_type" 715
unusable_trip WARNING 1

unusable_trip

Trips must have more than one stop to be usable.

A trip must visit more than one stop in stop_times.txt to be usable by passengers for boarding and alighting.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. tripId (?) The faulty record's id.
375 "1-TAD-EVI2024-TAD-7-jours-20"