GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 5.0.1 at 2024-06-08T02:56:46Z,
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. ExportService.checksum.md5
  2. agency.txt
  3. calendar.txt
  4. calendar_dates.txt
  5. routes.txt
  6. stop_times.txt
  7. stops.txt
  8. transfers.txt
  9. trips.txt

Counts

  • Agencies: 1
  • Blocks: 1
  • Routes: 118
  • Shapes: 0
  • Stops: 2656
  • Trips: 23939

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

TransfersRoute ColorsHeadsignsWheelchair AccessibilityLocation Types

Specification Compliance report

198 notices reported (0 errors, 197 warnings, 1 infos)

Notice Code Severity Total
expired_calendar WARNING 11

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.
4 "CAL:AUTO_1-14-127"
12 "CAL:AUTO_9-14-127"
6 "CAL:AUTO_13-14-127"
7 "CAL:AUTO_14-14-127"
11 "CAL:AUTO_6-14-127"
8 "CAL:AUTO_2-14-127"
9 "CAL:AUTO_3-14-127"
3 "CAL:AUTO_11-14-127"
10 "CAL:AUTO_4-14-127"
2 "CAL:AUTO_10-14-127"
5 "CAL:AUTO_12-14-127"
leading_or_trailing_whitespaces WARNING 3

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.
"routes.txt" 21 "route_long_name" "Métro La Rose - La Parade "
"routes.txt" 26 "route_long_name" "Métro La Rose - La Fève "
"routes.txt" 87 "route_long_name" "Gèze - Sainte-Marguerite Dromel "
missing_bike_allowance WARNING 156

missing_bike_allowance

Ferry trips should include bike allowance information.

All ferry trips should have a valid value in the bikes_allowed field in trips.txt.

You can see more about this notice here.

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

csvRowNumber (?) The row number of the faulty record. routeId (?) The faulty record's route id. tripId (?) The faulty record's trip id.
23785 "FERRY" "34676168"
23786 "FERRY" "34676169"
23787 "FERRY" "34676170"
23788 "FERRY" "34676171"
23789 "FERRY" "34676172"
23790 "FERRY" "34676173"
23791 "FERRY" "34676174"
23792 "FERRY" "34676175"
23793 "FERRY" "34676176"
23794 "FERRY" "34676177"
23795 "FERRY" "34676178"
23796 "FERRY" "34676179"
23797 "FERRY" "34676180"
23798 "FERRY" "34676181"
23799 "FERRY" "34676182"
23800 "FERRY" "34676183"
23801 "FERRY" "34676184"
23802 "FERRY" "34676185"
23803 "FERRY" "34676186"
23804 "FERRY" "34676187"
23805 "FERRY" "34676188"
23806 "FERRY" "34676189"
23807 "FERRY" "34676190"
23808 "FERRY" "34676191"
23809 "FERRY" "34676192"
23810 "FERRY" "34676193"
23811 "FERRY" "34676194"
23812 "FERRY" "34676195"
23813 "FERRY" "34676196"
23814 "FERRY" "34676197"
23815 "FERRY" "34676198"
23816 "FERRY" "34676199"
23817 "FERRY" "34676200"
23818 "FERRY" "34676201"
23819 "FERRY" "34676202"
23820 "FERRY" "34676203"
23821 "FERRY" "34676204"
23822 "FERRY" "34676205"
23823 "FERRY" "34676206"
23824 "FERRY" "34676207"
23825 "FERRY" "34676208"
23826 "FERRY" "34676209"
23827 "FERRY" "34676210"
23828 "FERRY" "34676211"
23829 "FERRY" "34676212"
23830 "FERRY" "34676213"
23831 "FERRY" "34676214"
23832 "FERRY" "34676215"
23833 "FERRY" "34676216"
23834 "FERRY" "34676217"
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 2

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.
"routes.txt" "route_short_name" "21JET" 35
"routes.txt" "route_short_name" "97JET" 115
stop_without_stop_time WARNING 22

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.
58 "10229" "Canebière Bourse"
64 "3206" "Euroméditerranée Gantès"
65 "3281" "Euroméditerranée Gantès"
69 "3209" "Joliette"
70 "3279" "Joliette"
78 "10232" "Joliette"
80 "3210" "République Dames"
81 "3278" "République Dames"
85 "3211" "Sadi Carnot"
86 "3277" "Sadi Carnot"
150 "2584" "Collège Yves Montand"
1206 "4124" "Castellane"
1292 "3585" "Métro Rond Point du Prado"
1500 "4361" "Lycée Simone Veil"
1501 "4362" "Lycée Simone Veil"
1557 "3554" "Arenc Le Silo"
1558 "3556" "Arenc Le Silo"
1604 "3213" "Belsunce Alcazar"
1605 "3275" "Belsunce Alcazar"
2138 "3474" "Noailles"
2656 "10230" "Euroméditerranée Gantès"
2657 "10231" "Euroméditerranée Gantès"
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" "20240226" "20240309"
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.
"ExportService.checksum.md5"