GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 5.0.1 at 2024-06-17T13:57: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. stop_times.txt
  6. stops.txt
  7. trips.txt

Counts

  • Agencies: 28
  • Blocks: 11589
  • Routes: 19
  • Shapes: 0
  • Stops: 29
  • Trips: 22521

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

Route ColorsHeadsignsWheelchair AccessibilityBikes Allowance

Specification Compliance report

399 notices reported (1 errors, 398 warnings, 0 infos)

Notice Code Severity Total
block_trips_with_overlapping_stop_times ERROR 1

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.
16802 "90357|241147|6" "90357|241147|6" 16808 "90357|241147|5" "90357|241147|5" "241147:011H2 - TGH" "20240824"
expired_calendar WARNING 271

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.

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

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
15858 "91322|229070|1"
13662 "88039|228019|1"
15341 "88069||0"
3527 "88500|235086|1"
236 "88082||0"
2224 "91637|234382|1"
7677 "85262|215698|1"
4540 "91240||0"
11534 "85285||0"
1949 "88161|234534|1"
1601 "88141||0"
8458 "85260||0"
18916 "91228||0"
14853 "85296||0"
1164 "91345|233500|1"
8057 "88028|227374|1"
11111 "91649|236201|1"
20428 "91611||0"
17877 "91635||0"
9264 "88019||0"
9504 "85259||0"
9920 "92719|227647|1"
9758 "88032||0"
12254 "92782||3"
12253 "92782||0"
12256 "92782||1"
12262 "92782||6"
12255 "92782||4"
6678 "85257|215520|1"
10571 "85277|216197|1"
14757 "90762|242007|1"
3524 "88500||0"
10389 "85271||0"
10384 "85271|216067|1"
20858 "88226|231902|1"
7025 "92675||0"
17347 "91330|229341|1"
2388 "89946||0"
10928 "91592|236098|1"
18689 "88188||0"
13353 "92784||0"
8559 "92709|227585|1"
830 "88115||0"
12416 "92529||0"
12947 "92783||0"
7448 "88031||0"
10929 "91592||0"
8564 "92709||0"
15577 "91314||0"
12417 "92529|227932|1"
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 25

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.
"agency.txt" "agency_name" "DB ICE" 11
"routes.txt" "route_short_name" "GS: BEBMI-FRPNO" 7
"routes.txt" "route_long_name" "GS: BEBMI-FRPNO" 7
"routes.txt" "route_short_name" "GS: FRPNO-BEBMI" 8
"routes.txt" "route_long_name" "GS: FRPNO-BEBMI" 8
"routes.txt" "route_short_name" "GS: BEBMI-NLAMA" 9
"routes.txt" "route_long_name" "GS: BEBMI-NLAMA" 9
"routes.txt" "route_short_name" "DEDTM-FRPNO" 10
"routes.txt" "route_long_name" "GS: DEDTM-FRPNO" 10
"routes.txt" "route_short_name" "GS: FRMLV-NLAMA" 11
"routes.txt" "route_long_name" "GS: FRMLV-NLAMA" 11
"routes.txt" "route_short_name" "GS: NLAMA -FRMLV" 12
"routes.txt" "route_long_name" "GS: NLAMA -FRMLV" 12
"routes.txt" "route_short_name" "GS: NLAMA-FRPNO" 13
"routes.txt" "route_long_name" "GS: NLAMA-FRPNO" 13
"routes.txt" "route_short_name" "GS: FRPNO-NLAMA" 14
"routes.txt" "route_long_name" "GS: FRPNO-NLAMA" 14
"routes.txt" "route_short_name" "GS: FRPNO-DEDTM" 15
"routes.txt" "route_long_name" "GS: FRPNO-DEDTM" 15
"routes.txt" "route_short_name" "GS: NLAMA - FRMSC" 16
"routes.txt" "route_long_name" "GS: NLAMA - FRMSC" 16
"routes.txt" "route_short_name" "GS: FRMSC-NLAMA" 17
"routes.txt" "route_long_name" "GS: FRMSC-NLAMA" 17
"routes.txt" "route_short_name" "GS: NLAMA-BEBMI" 18
"routes.txt" "route_long_name" "GS: NLAMA-BEBMI" 18
route_long_name_contains_short_name WARNING 18

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`.
"FRPNO-GBSPX" 2 "Paris-London" "Paris-London"
"GBSPX-FRPNO" 3 "London-Paris" "London-Paris"
"GBSPX-NLAMA" 4 "London-Amsterdam" "London-Amsterdam"
"GBSPX-BEBMI" 5 "London-Brussels" "London-Brussels"
"BEBMI-GBSPX-FAST" 6 "Brussels-London FAST - Calais omitted" "Brussels-London FAST - Calais omitted"
"BEBMI-FRPNO" 7 "GS: BEBMI-FRPNO" "GS: BEBMI-FRPNO"
"FRPNO-BEBMI" 8 "GS: FRPNO-BEBMI" "GS: FRPNO-BEBMI"
"BEBMI-NLAMA" 9 "GS: BEBMI-NLAMA" "GS: BEBMI-NLAMA"
"FRMLV-NLAMA" 11 "GS: FRMLV-NLAMA" "GS: FRMLV-NLAMA"
"NLAMA-FRMLV" 12 "GS: NLAMA -FRMLV" "GS: NLAMA -FRMLV"
"NLAMA-FRPNO" 13 "GS: NLAMA-FRPNO" "GS: NLAMA-FRPNO"
"FRPNO-NLAMA" 14 "GS: FRPNO-NLAMA" "GS: FRPNO-NLAMA"
"FRPNO-DEDTM" 15 "GS: FRPNO-DEDTM" "GS: FRPNO-DEDTM"
"NLAMA-FRMSC" 16 "GS: NLAMA - FRMSC" "GS: NLAMA - FRMSC"
"FRMSC-NLAMA" 17 "GS: FRMSC-NLAMA" "GS: FRMSC-NLAMA"
"NLAMA-BEBMI" 18 "GS: NLAMA-BEBMI" "GS: NLAMA-BEBMI"
"BEBMI-FRMSC" 19 "Brussels-Marseille" "Brussels-Marseille"
"FRMSC-BEBMI" 20 "Marseille-Brussels" "Marseille-Brussels"
route_short_name_too_long WARNING 16

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`.
"GBSPX-NLAMA" 4 "London-Amsterdam"
"GBSPX-BEBMI" 5 "London-Brussels"
"BEBMI-GBSPX-FAST" 6 "Brussels-London FAST - Calais omitted"
"BEBMI-FRPNO" 7 "GS: BEBMI-FRPNO"
"FRPNO-BEBMI" 8 "GS: FRPNO-BEBMI"
"BEBMI-NLAMA" 9 "GS: BEBMI-NLAMA"
"FRMLV-NLAMA" 11 "GS: FRMLV-NLAMA"
"NLAMA-FRMLV" 12 "GS: NLAMA -FRMLV"
"NLAMA-FRPNO" 13 "GS: NLAMA-FRPNO"
"FRPNO-NLAMA" 14 "GS: FRPNO-NLAMA"
"FRPNO-DEDTM" 15 "GS: FRPNO-DEDTM"
"NLAMA-FRMSC" 16 "GS: NLAMA - FRMSC"
"FRMSC-NLAMA" 17 "GS: FRMSC-NLAMA"
"NLAMA-BEBMI" 18 "GS: NLAMA-BEBMI"
"BEBMI-FRMSC" 19 "Brussels-Marseille"
"FRMSC-BEBMI" 20 "Marseille-Brussels"
stop_without_stop_time WARNING 7

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.
19 "8772319" "Lyon Part-Dieu"
20 "8774100" "Chambery - Challes-les-Eaux"
21 "8774164" "Albertville"
22 "8774172" "Moutiers Salins Brides Les Bains"
23 "8774176" "Aime - La Plagne"
24 "8774177" "Landry"
25 "8774179" "Bourg-Saint-Maurice"
unusable_trip WARNING 46

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.
10935 "91984|236106|2"
11003 "91632|236161|12"
11298 "92560||3"
11299 "92560|216424|6"
11300 "92560||5"
11301 "92560|216423|4"
11302 "92560||1"
11303 "92560|216422|2"
11304 "92560|216421|0"
11305 "92560||7"
11306 "92560|216425|8"
11388 "87322||1"
11389 "87322|225412|0"
11392 "87322|225413|4"
11396 "92796|225420|9"
11397 "92796|225416|0"
11399 "92796|225418|5"
11400 "92796|225417|3"
11401 "92796||1"
11402 "92796||6"
11403 "92796|225419|7"
11404 "92796||4"
11405 "92796||8"
11409 "92798||1"
11410 "92798|225426|7"
11411 "92798|225427|9"
11412 "92798|225425|5"
11413 "92798||4"
11415 "92798||8"
11416 "92798|225424|3"
11417 "92798||6"
11418 "92798|225423|0"
14898 "92633|240456|10"
15235 "90647|240474|5"
16534 "92226||4"
16540 "92226||6"
19680 "92123||4"
19682 "92123||6"
20319 "92131||6"
20321 "92131||4"
21054 "92128||6"
21057 "92128||4"
22029 "92137||30"
22035 "92137||28"
22148 "92142||14"
22151 "92142||11"
unused_trip WARNING 13

unused_trip

Trip is not be used in stop_times.txt

Trips should be referred to at least once in stop_times.txt.

You can see more about this notice here.

tripId (?) The faulty record's id. csvRowNumber (?) The row number of the faulty record.
"91984|236106|2" 10935
"91632|236161|12" 11003
"92560||3" 11298
"92560|216424|6" 11299
"92560||5" 11300
"92560|216423|4" 11301
"92560||1" 11302
"92560|216422|2" 11303
"92560|216421|0" 11304
"92560||7" 11305
"92560|216425|8" 11306
"92633|240456|10" 14898
"90647|240474|5" 15235