GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 5.0.1 at 2024-06-07T16:42: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:
GTFS.pro
Publisher URL:
https://gtfs.pro
Feed Language:
French
Feed Start Date:
2022-09-01
Feed End Date:
2024-08-31

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. feed_info.txt
  5. routes.txt
  6. shapes.txt
  7. stop_times.txt
  8. stops.txt
  9. trips.txt

Counts

  • Agencies: 3
  • Blocks: 1
  • Routes: 89
  • Shapes: 307
  • Stops: 2266
  • Trips: 5286

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

ShapesFeed InformationRoute ColorsHeadsignsWheelchair AccessibilityBikes AllowanceLocation Types

Specification Compliance report

99 notices reported (0 errors, 99 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.
13 "878-1089"
mixed_case_recommended_field WARNING 90

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 90 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_short_name" "10EX" 17
"routes.txt" "route_short_name" "11EX" 19
"routes.txt" "route_short_name" "12EX" 21
"routes.txt" "route_desc" "02 31 15 55 55 au plus tard 2h avant le départ, sauf dimanche et lundi matin : le samedi avant 17h" 71
"routes.txt" "route_desc" "02 31 15 55 55 au plus tard 2h avant le départ, sauf dimanche et lundi matin : le samedi avant 17h" 72
"trips.txt" "trip_headsign" "CAEN CHU" 3145
"trips.txt" "trip_headsign" "CAEN CHU" 3146
"trips.txt" "trip_headsign" "CAEN CHU" 3147
"trips.txt" "trip_headsign" "CAEN CHU" 3148
"trips.txt" "trip_headsign" "CAEN CHU" 3149
"trips.txt" "trip_headsign" "CAEN CHU" 3150
"trips.txt" "trip_headsign" "CAEN CHU" 3151
"trips.txt" "trip_headsign" "CAEN CHU" 3152
"trips.txt" "trip_headsign" "CAEN CHU" 3153
"trips.txt" "trip_headsign" "CAEN CHU" 3154
"trips.txt" "trip_headsign" "CAEN CHU" 3155
"trips.txt" "trip_headsign" "CAEN CHU" 3156
"trips.txt" "trip_headsign" "CAEN CHU" 3157
"trips.txt" "trip_headsign" "CAEN CHU" 3158
"trips.txt" "trip_headsign" "CAEN CHU" 3159
"trips.txt" "trip_headsign" "CAEN CHU" 3160
"trips.txt" "trip_headsign" "CAEN CHU" 3161
"trips.txt" "trip_headsign" "CAEN CHU" 3162
"trips.txt" "trip_headsign" "CAEN CHU" 3163
"trips.txt" "trip_headsign" "CAEN CHU" 3164
"trips.txt" "trip_headsign" "CAEN CHU" 3165
"trips.txt" "trip_headsign" "CAEN CHU" 3166
"trips.txt" "trip_headsign" "CAEN CHU" 3167
"trips.txt" "trip_headsign" "CAEN CHU" 3168
"trips.txt" "trip_headsign" "CAEN CHU" 3169
"trips.txt" "trip_headsign" "CAEN CHU" 3170
"trips.txt" "trip_headsign" "CAEN CHU" 3171
"trips.txt" "trip_headsign" "CAEN CHU" 3172
"trips.txt" "trip_headsign" "CAEN CHU" 3173
"trips.txt" "trip_headsign" "CAEN CHU" 3174
"trips.txt" "trip_headsign" "CAEN CHU" 3175
"trips.txt" "trip_headsign" "CAEN CHU" 3176
"trips.txt" "trip_headsign" "CAEN CHU" 3177
"trips.txt" "trip_headsign" "CAEN CHU" 3178
"trips.txt" "trip_headsign" "CAEN CHU" 3179
"trips.txt" "trip_headsign" "CAEN CHU" 3180
"trips.txt" "trip_headsign" "CAEN CHU" 3181
"trips.txt" "trip_headsign" "CAEN CHU" 3182
"trips.txt" "trip_headsign" "CAEN CHU" 3183
"trips.txt" "trip_headsign" "CAEN CHU" 3184
"trips.txt" "trip_headsign" "CAEN CHU" 3185
"trips.txt" "trip_headsign" "CAEN CHU" 3186
"trips.txt" "trip_headsign" "CAEN CHU" 3187
"trips.txt" "trip_headsign" "CAEN CHU" 3188
"trips.txt" "trip_headsign" "CAEN CHU" 3189
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`.
"878-6A" 11 "6A" "6A Hérouville Saint-Clair"
"878-6B" 12 "6B" "6B Hérouville Saint-Clair"
"878-137A" 67 "137A" "137a IFS Collège Senghor - Grentheville le Hameau"
"878-137B" 68 "137B" "137b IFS Collège Senghor - Bourguebus La Hogue"
"878-137C" 69 "137C" "137c IFS Collège Senghor - Bourguebus Centre"
"878-137D" 70 "137D" "137d IFS Collège Senghor - Soliers Hameau du Four"
"878-CAENav465" 71 "RESAGO 2" "Resago 2 Secteur Colleville"
"878-CAENav506" 72 "RESAGO 5" "Resago 5 Secteur Ouistreham"