GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 5.0.1 at 2024-06-08T07:18:33Z,
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. shapes.txt
  6. stop_times.txt
  7. stops.txt
  8. trips.txt
  9. trips_extensions.txt

Counts

  • Agencies: 1
  • Blocks: 40
  • Routes: 9
  • Shapes: 469
  • Stops: 172
  • Trips: 469

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

9334 notices reported (76 errors, 9257 warnings, 1 infos)

Notice Code Severity Total
block_trips_with_overlapping_stop_times ERROR 3

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.
184 "549" "LMCJV VAC SCO" 294 "40614c79-e0e4-4bf5-9dd0-b915b2d330f6" "LMCJV VAC SCO" "2 PV" "20221024"
443 "455" "LMCJV VAC SCO" 312 "d0f98c08-2906-4b26-a472-f5e4e5f85808" "LMCJV VAC SCO" "2 PV" "20221024"
185 "143" "LMCJV PER SCO 2" 112 "159" "LMCJV PER SCO 2" "2" "20220901"
duplicate_key ERROR 6

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.
"stop_times.txt" 237 236 "trip_id,stop_sequence" "60,18"
"stop_times.txt" 239 238 "trip_id,stop_sequence" "60,19"
"stop_times.txt" 2303 2302 "trip_id,stop_sequence" "153,26"
"shapes.txt" 237 236 "shape_id,shape_pt_sequence" "60,18"
"shapes.txt" 239 238 "shape_id,shape_pt_sequence" "60,19"
"shapes.txt" 2303 2302 "shape_id,shape_pt_sequence" "153,26"
start_and_end_range_out_of_order ERROR 4

start_and_end_range_out_of_order

Two date or time fields are out of order.

Date or time fields have been found out of order in calendar.txt, feed_info.txt and stop_times.txt.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row number of the faulty record. startFieldName (?) The start value's field name. startValue (?) The start value. endFieldName (?) The end value's field name. endValue (?) The end value.
"stop_times.txt" 2944 "arrival_time" "13:31:00" "departure_time" "13:30:00"
"stop_times.txt" 2956 "arrival_time" "15:21:00" "departure_time" "15:20:00"
"stop_times.txt" 3034 "arrival_time" "09:15:00" "departure_time" "09:14:00"
"stop_times.txt" 8540 "arrival_time" "11:41:00" "departure_time" "11:40:00"
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.
8605 8604 "971fd179-a09f-4f44-9090-00f89e61494f" "17:29:00" "17:30:00"
wrong_parent_location_type ERROR 62

wrong_parent_location_type

Incorrect type of the parent location.

Value of field location_type of parent found in field parent_station is invalid.

According to spec

  • Stop/platform can only have Station as parent
  • Station can NOT have a parent
  • Entrance/exit or generic node can only have Station as parent
  • Boarding Area can only have Platform as parent

Any other combination raise this error.

You can see more about this notice here.

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

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty record. stopName (?) The faulty record's `stops.stop_name`. locationType (?) The faulty record's `stops.location_type`. parentCsvRowNumber (?) The row number of the faulty record's parent. parentStation (?) The id of the faulty record's parent station. parentStopName (?) The stop name of the faulty record's parent. parentLocationType (?) The location type of the faulty record's parent. expectedLocationType (?) The expected location type of the faulty record.
4 "STP-CA0200" "BEAUREGARD" 0 52 "12" "BEAUREGARD" 0 1
5 "STP-CA0201" "BERNAUDIN LE HAUT" 0 76 "118" "BERNAUDIN LE HAUT" 0 1
6 "STP-CA0208" "CROIX DE FER" 0 97 "173" "CROIX DE FER" 0 1
7 "STP-CR0202" "BOUCIEU" 0 169 "412" "BOUCIEU" 0 1
8 "STP-CR0203" "CHAMP DE MARS" 0 147 "324" "CHAMP DE MARS" 0 1
9 "STP-CR0204" "CHAMPLONG" 0 167 "410" "CHAMPLONG" 0 1
10 "STP-CR0205" "CLAIR LOGIS" 0 138 "304" "CLAIR LOGIS" 0 1
11 "STP-CR0206" "CORDELIERS" 0 70 "112" "CORDELIERS" 0 1
12 "STP-CR0207" "COTE BARLET" 0 165 "388" "COTE BARLET" 0 1
13 "STP-CR0209" "FERDINAND JANVIER" 0 69 "111" "FERDINAND JANVIER" 0 1
14 "STP-CR0210" "GRAND MURIER" 0 55 "15" "GRAND MURIER" 0 1
15 "STP-CR0211" "LA CROZE" 0 49 "9" "LA CROZE" 0 1
16 "STP-CR0212" "LES PERRETTES" 0 168 "411" "LES PERRETTES" 0 1
17 "STP-CR0213" "LES VIGNES" 0 162 "385" "LES VIGNES" 0 1
18 "STP-CR0214" "LYCEES" 0 43 "3" "LYCEES" 0 1
19 "STP-CR0215" "MAISON DE RETRAITE" 0 95 "171" "MAISON DE RETRAITE" 0 1
20 "STP-CR0216" "MARENTON" 0 125 "291" "MARENTON" 0 1
21 "STP-CR0217" "MICHELET" 0 65 "39" "MICHELET" 0 1
22 "STP-CR0218" "MUETTE" 0 96 "172" "MUETTE" 0 1
23 "STP-CR0219" "PEUPLIERS" 0 46 "6" "PEUPLIERS" 0 1
24 "STP-CR0220" "ANNONAY PONT ARNAUD" 0 72 "114" "ANNONAY PONT ARNAUD" 0 1
25 "STP-CR0221" "PONT CHEVALIER" 0 74 "116" "PONT CHEVALIER" 0 1
26 "STP-CR0222" "MIGNOT" 0 48 "8" "MIGNOT" 0 1
27 "STP-CR0223" "PRADE" 0 51 "11" "PRADE" 0 1
28 "STP-CR0224" "ROUTE DE ROIFFIEUX" 0 75 "117" "ROUTE DE ROIFFIEUX" 0 1
29 "STP-CR0225" "RIMBAUD" 0 104 "180" "RIMBAUD" 0 1
30 "STP-CR0226" "RUE DES ALPES" 0 99 "175" "RUE DES ALPES" 0 1
31 "STP-CR0227" "ANNONAY VARAGNES" 0 67 "109" "ANNONAY VARAGNES" 0 1
32 "STP-CR0228" "VERLAINE" 0 103 "179" "VERLAINE" 0 1
33 "STP-CR0229" "VILLEDIEU" 0 100 "176" "VILLEDIEU" 0 1
34 "STP-CR0230" "VISSENTY" 0 163 "386" "VISSENTY" 0 1
35 "STP-CR0231" "ASSOMPTIONNISTE" 0 129 "295" "ASSOMPTIONNISTE" 0 1
36 "STP-CR0232" "EGLISE" 0 109 "185" "EGLISE" 0 1
37 "STP-CR0233" "POULET" 0 128 "294" "POULET" 0 1
38 "STP-CR0235" "SAINTE EMILIE CENTRE" 0 105 "181" "SAINTE EMILIE CENTRE" 0 1
39 "STP-CR0237" "PECHE MOREL" 0 77 "119" "PECHE MOREL" 0 1
40 "STP-CR0502" "BEL AIR" 0 45 "5" "BEL AIR" 0 1
41 "STP-CR0503" "MONTALIVET" 0 94 "170" "MONTALIVET" 0 1
47 "7" "FONT CHEVALIER" 0 57 "31" "FONT CHEVALIER" 0 1
50 "10" "LA COLLINE" 0 58 "32" "LA COLLINE" 0 1
61 "35" "BOULIEU CENTRE" 0 64 "38" "BOULIEU CENTRE" 0 1
66 "108" "BOULIEU CHEMIN" 0 60 "34" "BOULIEU CHEMIN" 0 1
68 "110" "CHAMPAGNE" 0 87 "130" "CHAMPAGNE" 0 1
71 "113" "PONT MONTGOLFIER" 0 86 "129" "PONT MONTGOLFIER" 0 1
73 "115" "ANNONAY PARC RIBOULON" 0 85 "128" "ANNONAY PARC RIBOULON" 0 1
80 "123" "LES SIX CHEMINS" 0 88 "164" "LES SIX CHEMINS" 0 1
81 "124" "ZODIAQUE" 0 120 "196" "ZODIAQUE" 0 1
89 "165" "JEAN MOULIN" 0 44 "4" "JEAN MOULIN" 0 1
93 "169" "LEP" 0 118 "194" "LEP" 0 1
98 "174" "GONOTTES" 0 117 "193" "GONOTTES" 0 1
expired_calendar WARNING 2

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.
6 "MERCREDI VAC SCO"
3 "LMCJV VAC SCO"
leading_or_trailing_whitespaces WARNING 2

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" 110 "stop_name" "DAVEZIEUX MAIRIE "
"trips.txt" 304 "block_id" " 9 PV"
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"
missing_timepoint_value WARNING 8666

missing_timepoint_value

stop_times.timepoint value is missing for a record.

Even though the column timepoint is optional in stop_times.txt according to the specification, stop_times.timepoint should not be empty when provided.

You can see more about this notice here.

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

csvRowNumber (?) The row number of the faulty record. tripId (?) The faulty record's `stop_times.trip_id`. stopSequence (?) The faulty record's `stop_times.stop_sequence`.
2 "a9fd0639-a6f0-48fe-b319-d910a4a1cfdd" 1
3 "a9fd0639-a6f0-48fe-b319-d910a4a1cfdd" 2
4 "a9fd0639-a6f0-48fe-b319-d910a4a1cfdd" 3
5 "a9fd0639-a6f0-48fe-b319-d910a4a1cfdd" 4
6 "a9fd0639-a6f0-48fe-b319-d910a4a1cfdd" 5
7 "a9fd0639-a6f0-48fe-b319-d910a4a1cfdd" 6
8 "a9fd0639-a6f0-48fe-b319-d910a4a1cfdd" 7
9 "a9fd0639-a6f0-48fe-b319-d910a4a1cfdd" 8
10 "a9fd0639-a6f0-48fe-b319-d910a4a1cfdd" 9
11 "a9fd0639-a6f0-48fe-b319-d910a4a1cfdd" 10
12 "a9fd0639-a6f0-48fe-b319-d910a4a1cfdd" 11
13 "a9fd0639-a6f0-48fe-b319-d910a4a1cfdd" 12
14 "26" 1
15 "26" 2
16 "26" 3
17 "26" 6
18 "26" 7
19 "26" 8
20 "26" 9
21 "26" 10
22 "26" 11
23 "26" 12
24 "26" 13
25 "26" 14
26 "26" 15
27 "27" 1
28 "27" 2
29 "27" 5
30 "27" 6
31 "27" 7
32 "27" 8
33 "27" 9
34 "27" 10
35 "27" 11
36 "27" 12
37 "27" 13
38 "27" 14
39 "27" 15
40 "50" 1
41 "50" 2
42 "50" 3
43 "50" 6
44 "50" 7
45 "50" 8
46 "50" 9
47 "50" 10
48 "50" 11
49 "50" 12
50 "50" 13
51 "50" 14
mixed_case_recommended_field WARNING 575

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 575 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" "ST-CLAIR MONUMENT" 2
"stops.txt" "stop_name" "ST-CLAIR MONUMENT" 3
"stops.txt" "stop_name" "BERNAUDIN LE HAUT" 5
"stops.txt" "stop_name" "CROIX DE FER" 6
"stops.txt" "stop_name" "CHAMP DE MARS" 8
"stops.txt" "stop_name" "CLAIR LOGIS" 10
"stops.txt" "stop_name" "COTE BARLET" 12
"stops.txt" "stop_name" "FERDINAND JANVIER" 13
"stops.txt" "stop_name" "GRAND MURIER" 14
"stops.txt" "stop_name" "LA CROZE" 15
"stops.txt" "stop_name" "LES PERRETTES" 16
"stops.txt" "stop_name" "LES VIGNES" 17
"stops.txt" "stop_name" "MAISON DE RETRAITE" 19
"stops.txt" "stop_name" "ANNONAY PONT ARNAUD" 24
"stops.txt" "stop_name" "PONT CHEVALIER" 25
"stops.txt" "stop_name" "ROUTE DE ROIFFIEUX" 28
"stops.txt" "stop_name" "RUE DES ALPES" 30
"stops.txt" "stop_name" "ANNONAY VARAGNES" 31
"stops.txt" "stop_name" "SAINTE EMILIE CENTRE" 38
"stops.txt" "stop_name" "PECHE MOREL" 39
"stops.txt" "stop_name" "BEL AIR" 40
"stops.txt" "stop_name" "ANNONAY GARE ROUTIERE" 42
"stops.txt" "stop_name" "JEAN MOULIN" 44
"stops.txt" "stop_name" "BEL AIR" 45
"stops.txt" "stop_name" "FONT CHEVALIER" 47
"stops.txt" "stop_name" "LA CROZE" 49
"stops.txt" "stop_name" "LA COLLINE" 50
"stops.txt" "stop_name" "ANNONAY LAPRAS" 53
"stops.txt" "stop_name" "GRAND MURIER" 55
"stops.txt" "stop_name" "FONT CHEVALIER" 57
"stops.txt" "stop_name" "LA COLLINE" 58
"stops.txt" "stop_name" "COLLEGE PERRIERES" 59
"stops.txt" "stop_name" "BOULIEU CHEMIN" 60
"stops.txt" "stop_name" "BOULIEU CENTRE" 61
"stops.txt" "stop_name" "BOULIEU PLACE DES ECOLES" 62
"stops.txt" "stop_name" "JOSEPH BESSET" 63
"stops.txt" "stop_name" "BOULIEU CENTRE" 64
"stops.txt" "stop_name" "BOULIEU CHEMIN" 66
"stops.txt" "stop_name" "ANNONAY VARAGNES" 67
"stops.txt" "stop_name" "FERDINAND JANVIER" 69
"stops.txt" "stop_name" "PONT MONTGOLFIER" 71
"stops.txt" "stop_name" "ANNONAY PONT ARNAUD" 72
"stops.txt" "stop_name" "ANNONAY PARC RIBOULON" 73
"stops.txt" "stop_name" "PONT CHEVALIER" 74
"stops.txt" "stop_name" "ROUTE DE ROIFFIEUX" 75
"stops.txt" "stop_name" "BERNAUDIN LE HAUT" 76
"stops.txt" "stop_name" "PECHE MOREL" 77
"stops.txt" "stop_name" "ROIFFIEUX MAIRIE" 78
"stops.txt" "stop_name" "ROIFFIEUX VILLAGE" 79
"stops.txt" "stop_name" "LES SIX CHEMINS" 80
route_color_contrast WARNING 1

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.
"313" 5 "#180BA1" "#000000"
route_long_name_contains_short_name WARNING 8

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`.
"17" 2 "LIGNE 2" "LIGNE 2 GARE ROUTIERE <> LAPRAS"
"131" 3 "LIGNE 3" "LIGNE 3 BOULIEU ECOLES <> ROIFFIEUX"
"197" 4 "LIGNE 1" "LIGNE 1 VARAGNES <> CHANTEBISE"
"313" 5 "LIGNE 5" "LIGNE 5 GARE ROUTIERE <> ST-CYR LE ROND"
"330" 6 "LIGNE 7" "LIGNE 7 GARE ROUTIERE <> TOISSIEU"
"389" 8 "LIGNE 4" "LIGNE 4 GARE ROUTIERE <> RIBOULON"
"414" 9 "LIGNE 8" "LIGNE 8 GARE ROUTIERE <> CHATINAIS"
"429" 10 "LIGNE 6" "LIGNE 6 GARE ROUTIERE <> PONT ARNAUD"
stop_without_stop_time WARNING 1

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty stop. stopName (?) The name of the faulty stop.
51 "11" "PRADE"
trip_coverage_not_active_for_next7_days WARNING 1

trip_coverage_not_active_for_next7_days

Trips data should be valid for at least the next seven days.

This notice is triggered if the date range where a significant number of trips are running ends in less than 7 days.

You can see more about this notice here.

currentDate (?) Current date (YYYYMMDD format). serviceWindowStartDate (?) The start date of the majority service window. serviceWindowEndDate (?) The end date of the majority service window.
"20240608" "20221024" "20240510"
unknown_file INFO 1

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"trips_extensions.txt"