GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 5.0.1 at 2024-06-17T14:42:13Z,
for the dataset file:///tmp/1_in.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

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

Files included

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

Counts

  • Agencies: 1
  • Blocks: 1
  • Routes: 41
  • Shapes: 19
  • Stops: 24
  • Trips: 8417

GTFS Features included (?) GTFS features provide a standardized vocabulary to define and describe features that are officially adopted in GTFS.

ShapesRoute ColorsHeadsignsWheelchair AccessibilityLocation Types

Specification Compliance report

8499 notices reported (19 errors, 8480 warnings, 0 infos)

Notice Code Severity Total
duplicate_key ERROR 12

duplicate_key

Duplicated entity.

The values of the given key and rows are duplicates.

You can see more about this notice here.

filename (?) The name of the faulty file oldCsvRowNumber (?) The row of the first occurrence. newCsvRowNumber (?) The row of the other occurrence. fieldName1 (?) Composite key's first field name. fieldValue1 (?) Composite key's first value.
"calendar_dates.txt" 1538 1537 "service_id,date" "9357-0823,20240823"
"calendar_dates.txt" 6894 6893 "service_id,date" "9457-0823,20240823"
"stop_times.txt" 8480 8474 "trip_id,stop_sequence" "9357-0823,1"
"stop_times.txt" 8481 8475 "trip_id,stop_sequence" "9357-0823,2"
"stop_times.txt" 8482 8476 "trip_id,stop_sequence" "9357-0823,3"
"stop_times.txt" 8483 8477 "trip_id,stop_sequence" "9357-0823,4"
"stop_times.txt" 8484 8478 "trip_id,stop_sequence" "9357-0823,5"
"stop_times.txt" 8485 8479 "trip_id,stop_sequence" "9357-0823,6"
"stop_times.txt" 27188 27186 "trip_id,stop_sequence" "9457-0823,1"
"stop_times.txt" 27189 27187 "trip_id,stop_sequence" "9457-0823,2"
"trips.txt" 1538 1537 "trip_id" "9357-0823"
"trips.txt" 6894 6893 "trip_id" "9457-0823"
stop_time_with_arrival_before_previous_departure_time ERROR 7

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.
8480 8474 "9357-0823" "14:55:00" "15:22:00"
8481 8475 "9357-0823" "16:47:00" "16:52:00"
8482 8476 "9357-0823" "17:27:00" "17:30:00"
8483 8477 "9357-0823" "18:02:00" "18:06:00"
8484 8478 "9357-0823" "18:36:00" "18:38:00"
7760 7759 "9423-0831" "12:09:00" "12:10:00"
27189 27187 "9457-0823" "16:44:00" "16:47:00"
duplicate_route_name WARNING 1

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`.
33 "FRPNO-HPI" 35 "HPI-FRPNO" "thalys" "Paris Nord-Paris Nord" 2 "THALYS"
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_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 8461

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 8461 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.
"routes.txt" "route_short_name" "thalys" 2
"routes.txt" "route_short_name" "thalys" 3
"routes.txt" "route_short_name" "thalys" 4
"routes.txt" "route_short_name" "thalys" 5
"routes.txt" "route_short_name" "thalys" 6
"routes.txt" "route_short_name" "thalys" 7
"routes.txt" "route_short_name" "thalys" 8
"routes.txt" "route_short_name" "thalys" 9
"routes.txt" "route_short_name" "thalys" 10
"routes.txt" "route_short_name" "thalys" 11
"routes.txt" "route_short_name" "thalys" 12
"routes.txt" "route_short_name" "thalys" 13
"routes.txt" "route_short_name" "thalys" 14
"routes.txt" "route_short_name" "thalys" 15
"routes.txt" "route_short_name" "thalys" 16
"routes.txt" "route_short_name" "thalys" 17
"routes.txt" "route_short_name" "thalys" 18
"routes.txt" "route_short_name" "thalys" 19
"routes.txt" "route_short_name" "thalys" 20
"routes.txt" "route_short_name" "thalys" 21
"routes.txt" "route_short_name" "thalys" 22
"routes.txt" "route_short_name" "thalys" 23
"routes.txt" "route_short_name" "thalys" 24
"routes.txt" "route_short_name" "thalys" 25
"routes.txt" "route_short_name" "thalys" 26
"routes.txt" "route_short_name" "thalys" 27
"routes.txt" "route_short_name" "thalys" 28
"routes.txt" "route_short_name" "thalys" 29
"routes.txt" "route_short_name" "thalys" 30
"routes.txt" "route_short_name" "thalys" 31
"routes.txt" "route_short_name" "thalys" 32
"routes.txt" "route_short_name" "thalys" 33
"routes.txt" "route_short_name" "thalys" 34
"routes.txt" "route_short_name" "thalys" 35
"routes.txt" "route_short_name" "thalys" 36
"routes.txt" "route_short_name" "thalys" 37
"routes.txt" "route_short_name" "thalys" 38
"routes.txt" "route_short_name" "thalys" 39
"routes.txt" "route_short_name" "thalys" 40
"routes.txt" "route_short_name" "thalys" 41
"routes.txt" "route_short_name" "thalys" 42
"stops.txt" "stop_name" "BRUXELLES-NORD" 16
"trips.txt" "trip_short_name" "9346 NLAMA -> BEBMI" 2
"trips.txt" "trip_short_name" "9346 NLAMA -> BEBMI" 3
"trips.txt" "trip_short_name" "9346 NLAMA -> BEBMI" 4
"trips.txt" "trip_short_name" "9346 NLAMA -> BEBMI" 5
"trips.txt" "trip_short_name" "9346 NLAMA -> FRPNO" 6
"trips.txt" "trip_short_name" "9346 NLAMA -> BEBMI" 7
"trips.txt" "trip_short_name" "9346 NLAMA -> BEBMI" 8
"trips.txt" "trip_short_name" "9346 NLAMA -> BEBMI" 9
stop_too_far_from_shape WARNING 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.
43 "5776" "9368-0611" 214 "bruxelles-midi/brussel-zuid" "Bruxelles-Midi/Brussel-Zuid" [50.833929299999994,4.3332389] 409.28978392545616
543 "5776" "9322-0630" 2653 "antwerpen-centraal/anvers" "Antwerpen-Centraal/Anvers" [50.833929299999994,4.3332389] 43022.5445436258
1314 "5776" "9310-0831" 7120 "bruxelles-nord" "BRUXELLES-NORD" [50.833929299999994,4.3332389] 3455.972497981715
78 "5820" "9363-0615" 300 "bruxelles-midi/brussel-zuid" "Bruxelles-Midi/Brussel-Zuid" [50.833929299999994,4.3332389] 409.28978392545616
78 "5820" "9363-0615" 301 "antwerpen-centraal/anvers" "Antwerpen-Centraal/Anvers" [50.833929299999994,4.3332389] 43022.5445436258
2503 "5820" "9471-0807" 14071 "liege-guillemins" "Liège-Guillemins" [50.833929299999994,4.3332389] 89754.30024685274
6893 "5820" "9457-0823" 27191 "rotterdam_centraal" "Rotterdam Centraal" [50.833929299999994,4.3332389] 121671.49075971186
6893 "5820" "9457-0823" 27192 "schiphol_aeroport" "Schiphol Aéroport" [50.833929299999994,4.3332389] 166749.01543433964
6893 "5820" "9457-0823" 27193 "amsterdam_centraal" "Amsterdam Centraal" [50.833929299999994,4.3332389] 176223.0614428792
stops_match_shape_out_of_order WARNING 1

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.
3295 "632" "9382-0828" 18217 "schiphol_aeroport" "Schiphol Aéroport" [52.30957995941387,4.762404918989016] 18216 "paris_nord" "Paris Nord" [48.88178,2.35554]
unusable_trip WARNING 6

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.
439 "9302-0812"
6747 "9358-0825"
7524 "9089-0615"
8020 "9090-0616"
8140 "9145-0630"
8142 "9145-0714"