GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 5.0.1 at 2024-06-08T07:18:25Z,
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-09-30

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: 1
  • Blocks: 32
  • Routes: 9
  • Shapes: 55
  • Stops: 171
  • Trips: 295

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

ShapesFeed InformationRoute ColorsHeadsignsWheelchair AccessibilityLocation Types

Specification Compliance report

304 notices reported (1 errors, 303 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.
123 "100870-b8338ccdc502bac98f69" "100870-LMCJV-PER-SCO-2" 67 "100870-3dbb3eb138380f0e3951" "100870-LMCJV-PER-SCO-2" "2" "20220901"
mixed_case_recommended_field WARNING 295

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 295 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.
"trips.txt" "trip_headsign" "LIGNE 8 ANNONAY GARE ROUTIERE" 2
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY MIRECOULY" 3
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY MIRECOULY" 4
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY LAPRAS" 5
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY MIRECOULY" 6
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY LAPRAS" 7
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY MIRECOULY" 8
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY LAPRAS" 9
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY MIRECOULY" 10
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY GOLA" 11
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY GRAND MURIER" 12
"trips.txt" "trip_headsign" "LIGNE 3 BOULIEU LES ANNONAY ECOLES" 13
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY MIRECOULY" 14
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY LAPRAS" 15
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY LA VALETTE" 16
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY GARE ROUTIERE" 17
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY GARE ROUTIERE" 18
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY GARE ROUTIERE" 19
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY GARE ROUTIERE" 20
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY GARE ROUTIERE" 21
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY GARE ROUTIERE" 22
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY GARE ROUTIERE" 23
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY GARE ROUTIERE" 24
"trips.txt" "trip_headsign" "LIGNE 2 ANNONAY GARE ROUTIERE" 25
"trips.txt" "trip_headsign" "LIGNE 3 BOULIEU LES ANNONAY ECOLES" 26
"trips.txt" "trip_headsign" "LIGNE 3 ROIFFIEUX VILLAGE" 27
"trips.txt" "trip_headsign" "LIGNE 3 ROIFFIEUX VILLAGE" 28
"trips.txt" "trip_headsign" "LIGNE 3 ROIFFIEUX VILLAGE" 29
"trips.txt" "trip_headsign" "LIGNE 3 ROIFFIEUX VILLAGE" 30
"trips.txt" "trip_headsign" "LIGNE 3 BOULIEU LES ANNONAY ECOLES" 31
"trips.txt" "trip_headsign" "LIGNE 1 DAVEZIEUX CHANTEBISE" 32
"trips.txt" "trip_headsign" "LIGNE 1 DAVEZIEUX CHANTEBISE" 33
"trips.txt" "trip_headsign" "LIGNE 1 DAVEZIEUX CHANTEBISE" 34
"trips.txt" "trip_headsign" "LIGNE 1 DAVEZIEUX CHANTEBISE" 35
"trips.txt" "trip_headsign" "LIGNE 1 DAVEZIEUX CHANTEBISE" 36
"trips.txt" "trip_headsign" "LIGNE 1 DAVEZIEUX CHANTEBISE" 37
"trips.txt" "trip_headsign" "LIGNE 1 DAVEZIEUX CHANTEBISE" 38
"trips.txt" "trip_headsign" "LIGNE 1 DAVEZIEUX CHANTEBISE" 39
"trips.txt" "trip_headsign" "LIGNE 1 ANNONAY VARAGNES" 40
"trips.txt" "trip_headsign" "LIGNE 1 ANNONAY VARAGNES" 41
"trips.txt" "trip_headsign" "LIGNE 1 ANNONAY VARAGNES" 42
"trips.txt" "trip_headsign" "LIGNE 1 ANNONAY VARAGNES" 43
"trips.txt" "trip_headsign" "LIGNE 1 ANNONAY VARAGNES" 44
"trips.txt" "trip_headsign" "LIGNE 1 ANNONAY VARAGNES" 45
"trips.txt" "trip_headsign" "LIGNE 1 ANNONAY VARAGNES" 46
"trips.txt" "trip_headsign" "LIGNE 1 ANNONAY VARAGNES" 47
"trips.txt" "trip_headsign" "LIGNE 1 ANNONAY VARAGNES" 48
"trips.txt" "trip_headsign" "LIGNE 1 ANNONAY VARAGNES" 49
"trips.txt" "trip_headsign" "LIGNE 1 ANNONAY VARAGNES" 50
"trips.txt" "trip_headsign" "LIGNE 1 ANNONAY VARAGNES" 51
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`.
"100870-17" 2 "LIGNE 2" "Ligne 2 Gare Routiere <> Lapras"
"100870-131" 3 "LIGNE 3" "Ligne 3 Boulieu Ecoles <> Roiffieux"
"100870-197" 4 "LIGNE 1" "Ligne 1 Varagnes <> Chantebise"
"100870-313" 5 "LIGNE 5" "Ligne 5 Gare Routiere <> ST-CYR LE Rond"
"100870-330" 6 "LIGNE 7" "Ligne 7 Gare Routiere <> Toissieu"
"100870-389" 8 "LIGNE 4" "Ligne 4 Gare Routiere <> Riboulon"
"100870-414" 9 "LIGNE 8" "Ligne 8 Gare Routiere <> Chatinais"
"100870-429" 10 "LIGNE 6" "Ligne 6 Gare Routiere <> Pont Arnaud"