GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 5.0.1 at 2024-06-08T08:25:57Z,
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: 1
  • Blocks: 1
  • Routes: 9
  • Shapes: 0
  • Stops: 97
  • Trips: 211

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

25 notices reported (0 errors, 25 warnings, 0 infos)

Notice Code Severity Total
expired_calendar WARNING 1

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.
3 "2"
fast_travel_between_consecutive_stops WARNING 4

fast_travel_between_consecutive_stops

A transit vehicle moves too fast between two consecutive stops.

The speed threshold depends on route type:

Route type Description Threshold, km/h
0 Light rail 100
1 Subway 150
2 Rail 500
3 Bus 150
4 Ferry 80
5 Cable tram 30
6 Aerial lift 50
7 Funicular 50
11 Trolleybus 150
12 Monorail 150
- Unknown 200

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.
130 "129" "447" 426.11384169302306 0.11836495602583974 1237 4 "24928" "BANDOL Gymnase O" "08:33:00" 1238 5 "24950" "BANDOL Parc du Cannet" "08:33:01"
171 "170" "447" 426.11384169302306 0.11836495602583974 1843 4 "24928" "BANDOL Gymnase O" "08:33:00" 1844 5 "24950" "BANDOL Parc du Cannet" "08:33:01"
130 "129" "447" 863.3324250706326 0.23981456251962016 1240 7 "18380" "BANDOL Les Lutins E" "08:36:00" 1241 8 "24956" "BANDOL Pont de Fer" "08:36:01"
171 "170" "447" 863.3324250706326 0.23981456251962016 1846 7 "18380" "BANDOL Les Lutins E" "08:36:00" 1847 8 "24956" "BANDOL Pont de Fer" "08:36:01"
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 10

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" "TRANSDEV VAR" 2
"routes.txt" "route_desc" "PETIT TRAIN BANDOL" 3
"routes.txt" "route_long_name" "marche de sanary ETE" 4
"stops.txt" "stop_name" "SANARY SAINT ROCH / CONFERENCE" 7
"stops.txt" "stop_name" "SANARY ALLEE DES PETITS PINS" 12
"stops.txt" "stop_name" "SANARY SAINT ROCH" 14
"stops.txt" "stop_name" "SANARY PLAGE DE BEAUCOURS" 66
"stops.txt" "stop_name" "SANARY jardin d’hiver" 83
"stops.txt" "stop_name" "SANARY LE NID" 86
"stops.txt" "stop_name" "SANARY LA POINTE" 88
route_short_name_too_long WARNING 7

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`.
"453" 2 "Colombus Cir 3"
"447" 5 "UrBan Circ. 1"
"448" 6 "UrBan Circ. 2"
"449" 7 "UrBan Circ. 3"
"450" 8 "UrBan Circ. 4"
"451" 9 "Colombus Cir 1"
"452" 10 "Colombus Cir 2"
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" "20240702" "20240831"