GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 5.0.1 at 2024-06-17T14:21:07Z,
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.txt
  3. calendar_dates.txt
  4. routes.txt
  5. stop_times.txt
  6. stops.txt
  7. transfers.txt
  8. trips.txt

Counts

  • Agencies: 1
  • Blocks: 841
  • Routes: 173
  • Shapes: 0
  • Stops: 1415
  • Trips: 841

Specification Compliance report

631 notices reported (1 errors, 630 warnings, 0 infos)

Notice Code Severity Total
stop_time_with_arrival_before_previous_departure_time ERROR 1

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.
5893 5892 "1024119-1030969" "00:00:00" "13:03:00"
fast_travel_between_far_stops WARNING 1

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.
622 "1024119-1030969" "1001641" 629.4131610020698 10.490219350034497 5888 3 "70416" "Bras sur Meuse - Mairie" "12:45:00" 5893 8 "70921" "Regnéville sur Meuse - Place" "00:00:00"
leading_or_trailing_whitespaces WARNING 5

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" 40 "stop_name" "COMMERCY- SNCF "
"stops.txt" 295 "stop_name" "Mairie "
"stops.txt" 296 "stop_name" "Mairie "
"stops.txt" 1247 "stop_name" "Hameau de Aubercy "
"stops.txt" 1248 "stop_name" "Hameau de Aubercy "
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 352

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 352 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_long_name" "BAR LE DUC - VERDUN" 2
"routes.txt" "route_long_name" "VOID - COMMERCY - VERDUN" 3
"routes.txt" "route_long_name" "SERMAIZE LES BAINS - BAR LE DUC" 4
"routes.txt" "route_long_name" "STE MENEHOULD - VERDUN" 5
"routes.txt" "route_long_name" "MONTMEDY - VERDUN" 6
"routes.txt" "route_long_name" "SAINT DIZIER - BAR LE DUC" 7
"routes.txt" "route_long_name" "GONDRECOURT LE CHATEAU - BAR LE DUC" 8
"routes.txt" "route_long_name" "DAMVILLERS - CONSENVOYE" 9
"routes.txt" "route_short_name" "55S-STENAY03" 10
"routes.txt" "route_long_name" "JAMETZ - STENAY" 10
"routes.txt" "route_short_name" "55S-STMIHIEL01" 11
"routes.txt" "route_long_name" "COUROUVRE - SAINT MIHIEL" 11
"routes.txt" "route_short_name" "55S-STENAY14" 12
"routes.txt" "route_long_name" "FLASSIGNY - STENAY" 12
"routes.txt" "route_short_name" "55S-STENAY01" 13
"routes.txt" "route_long_name" "BREUX - STENAY" 13
"routes.txt" "route_short_name" "55S-STENAY02" 14
"routes.txt" "route_long_name" "ECOUVIEZ - STENAY" 14
"routes.txt" "route_short_name" "55S-STENAY04" 15
"routes.txt" "route_long_name" "MOULINS ST HUBERT - STENAY" 15
"routes.txt" "route_short_name" "55S-STMIHIEL02" 16
"routes.txt" "route_long_name" "BISLEE - SAINT MIHIEL" 16
"routes.txt" "route_short_name" "55S-STENAY18" 17
"routes.txt" "route_long_name" "LUZY SAINT MARTIN - STENAY" 17
"routes.txt" "route_short_name" "55S-STENAY06" 18
"routes.txt" "route_long_name" "ST LAURENT SUR OTHAIN - STENAY" 18
"routes.txt" "route_short_name" "55S-STENAY17" 19
"routes.txt" "route_long_name" "LAMOUILLY - STENAY" 19
"routes.txt" "route_short_name" "55S-MONTMEDY01" 20
"routes.txt" "route_long_name" "REMOIVILLE - MONTMEDY" 20
"routes.txt" "route_short_name" "55S-STMIHIEL03" 21
"routes.txt" "route_long_name" "LAMORVILLE - SAINT MIHIEL" 21
"routes.txt" "route_short_name" "55S-MONTMEDY02" 22
"routes.txt" "route_long_name" "FLASSIGNY - MONTMEDY" 22
"routes.txt" "route_short_name" "55S-MONTMEDY03" 23
"routes.txt" "route_long_name" "THONELLE - MONTMEDY" 23
"routes.txt" "route_short_name" "55S-STENAY15" 24
"routes.txt" "route_long_name" "SIVRY SUR MEUSE - STENAY" 24
"routes.txt" "route_short_name" "55S-STENAY07" 25
"routes.txt" "route_long_name" "NANTILLOIS - STENAY" 25
"routes.txt" "route_short_name" "55S-STENAY05" 26
"routes.txt" "route_long_name" "BEAUFORT EN ARGONNE - STENAY" 26
"routes.txt" "route_short_name" "55S-STENAY19" 27
"routes.txt" "route_long_name" "LINY DEVANT DUN - STENAY" 27
"routes.txt" "route_short_name" "55S-STENAY20" 28
"routes.txt" "route_long_name" "DOULCON - STENAY" 28
"routes.txt" "route_short_name" "55S-ANCERVILLE13" 29
"routes.txt" "route_long_name" "COUSANCES LES FORGES - SAINT DIZIER" 29
"routes.txt" "route_short_name" "55S-STENAY13" 30
"routes.txt" "route_long_name" "DAMVILLERS - STENAY" 30
route_short_name_too_long WARNING 97

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.

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

routeId (?) The id of the faulty record. csvRowNumber (?) The row number of the faulty record. routeShortName (?) The faulty record's `route_short_name`.
"1001426" 11 "55S-STMIHIEL01"
"1001437" 16 "55S-STMIHIEL02"
"1001445" 20 "55S-MONTMEDY01"
"1001446" 21 "55S-STMIHIEL03"
"1001449" 22 "55S-MONTMEDY02"
"1001451" 23 "55S-MONTMEDY03"
"1001466" 29 "55S-ANCERVILLE13"
"1001476" 31 "55S-STMIHIEL04"
"1001477" 32 "55S-DAMVILLERS10"
"1001483" 35 "55S-ANCERVILLE14"
"1001484" 36 "55S-STMIHIEL05"
"1001486" 37 "55S-LONGUYON01"
"1001489" 38 "55S-LONGUYON02"
"1001490" 39 "55S-BARLEDUC09"
"1001493" 40 "55S-BOULIGNY01"
"1001495" 41 "55S-BOULIGNY02"
"1001496" 42 "55S-STMIHIEL06"
"1001499" 43 "55S-INTERNE01"
"1001500" 44 "55S-INTERNE04"
"1001501" 45 "55S-INTERNE12"
"1001506" 46 "55S-STMIHIEL07"
"1001509" 47 "55S-BARLEDUC13"
"1001511" 48 "55S-BARLEDUC12"
"1001512" 49 "55S-COMMERCY01"
"1001514" 50 "55S-BARLEDUC11"
"1001522" 51 "55S-BARLEDUC10"
"1001526" 52 "55S-COMMERCY02"
"1001529" 53 "55S-COMMERCY04"
"1001530" 54 "55S-COMMERCY03"
"1001531" 55 "55S-COMMERCY05"
"1001533" 56 "55S-COMMERCY06"
"1001535" 57 "55S-COMMERCY07"
"1001536" 58 "55S-COMMERCY08"
"1001537" 59 "55S-COMMERCY09"
"1001538" 60 "55S-COMMERCY10"
"1001539" 61 "55S-ANCERVILLE01"
"1001541" 62 "55S-ANCERVILLE02"
"1001542" 63 "55S-COMMERCY12"
"1001545" 64 "55S-ANCERVILLE03"
"1001547" 65 "55S-COMMERCY11"
"1001549" 66 "55S-ANCERVILLE04"
"1001551" 67 "55S-COMMERCY22"
"1001553" 68 "55S-BARLEDUC01"
"1001555" 69 "55S-BARLEDUC05"
"1001557" 70 "55S-BARLEDUC17"
"1001558" 71 "55S-REVIGNY05"
"1001559" 72 "55S-REVIGNY02"
"1001560" 73 "55S-REVIGNY06"
"1001562" 74 "55S-REVIGNY03"
"1001563" 75 "55S-FRESNES01"
unexpected_enum_value WARNING 173

unexpected_enum_value

An enum has an unexpected value.

You can see more about this notice here.

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

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" 2 "route_type" 204
"routes.txt" 3 "route_type" 204
"routes.txt" 4 "route_type" 204
"routes.txt" 5 "route_type" 204
"routes.txt" 6 "route_type" 204
"routes.txt" 7 "route_type" 204
"routes.txt" 8 "route_type" 204
"routes.txt" 9 "route_type" 715
"routes.txt" 10 "route_type" 712
"routes.txt" 11 "route_type" 712
"routes.txt" 12 "route_type" 712
"routes.txt" 13 "route_type" 712
"routes.txt" 14 "route_type" 712
"routes.txt" 15 "route_type" 712
"routes.txt" 16 "route_type" 712
"routes.txt" 17 "route_type" 712
"routes.txt" 18 "route_type" 712
"routes.txt" 19 "route_type" 712
"routes.txt" 20 "route_type" 712
"routes.txt" 21 "route_type" 712
"routes.txt" 22 "route_type" 712
"routes.txt" 23 "route_type" 712
"routes.txt" 24 "route_type" 712
"routes.txt" 25 "route_type" 712
"routes.txt" 26 "route_type" 712
"routes.txt" 27 "route_type" 712
"routes.txt" 28 "route_type" 712
"routes.txt" 29 "route_type" 712
"routes.txt" 30 "route_type" 712
"routes.txt" 31 "route_type" 712
"routes.txt" 32 "route_type" 712
"routes.txt" 33 "route_type" 712
"routes.txt" 34 "route_type" 712
"routes.txt" 35 "route_type" 712
"routes.txt" 36 "route_type" 712
"routes.txt" 37 "route_type" 712
"routes.txt" 38 "route_type" 712
"routes.txt" 39 "route_type" 712
"routes.txt" 40 "route_type" 712
"routes.txt" 41 "route_type" 712
"routes.txt" 42 "route_type" 712
"routes.txt" 43 "route_type" 712
"routes.txt" 44 "route_type" 712
"routes.txt" 45 "route_type" 712
"routes.txt" 46 "route_type" 712
"routes.txt" 47 "route_type" 712
"routes.txt" 48 "route_type" 712
"routes.txt" 49 "route_type" 712
"routes.txt" 50 "route_type" 712
"routes.txt" 51 "route_type" 712