GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 5.0.1 at 2024-06-08T07:25:16Z,
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:
2023-01-03
Feed End Date:
2024-12-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: 1
  • Blocks: 1
  • Routes: 7
  • Shapes: 78
  • Stops: 412
  • Trips: 479

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

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

Notice Code Severity Total
expired_calendar WARNING 4

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.
8 "100878-44246"
12 "100878-44829"
4 "100878-43605"
10 "100878-44787"
mixed_case_recommended_field WARNING 479

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 479 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" "TERCIS LES BAINS - BELLEVUE" 2
"trips.txt" "trip_headsign" "TERCIS LES BAINS - BELLEVUE" 3
"trips.txt" "trip_headsign" "TERCIS LES BAINS - BELLEVUE" 4
"trips.txt" "trip_headsign" "TERCIS LES BAINS - BELLEVUE" 5
"trips.txt" "trip_headsign" "TERCIS LES BAINS - BELLEVUE" 6
"trips.txt" "trip_headsign" "DAX - PEM (GARE SNCF)" 7
"trips.txt" "trip_headsign" "DAX - PEM (GARE SNCF)" 8
"trips.txt" "trip_headsign" "DAX - PEM (GARE SNCF)" 9
"trips.txt" "trip_headsign" "DAX - PEM (GARE SNCF)" 10
"trips.txt" "trip_headsign" "DAX - PEM (GARE SNCF)" 11
"trips.txt" "trip_headsign" "NARROSSE - BEDIOSSE L6" 12
"trips.txt" "trip_headsign" "NARROSSE - BEDIOSSE L6" 13
"trips.txt" "trip_headsign" "NARROSSE - BEDIOSSE L6" 14
"trips.txt" "trip_headsign" "DAX - PEM (GARE SNCF)" 15
"trips.txt" "trip_headsign" "NARROSSE - BEDIOSSE L6" 16
"trips.txt" "trip_headsign" "NARROSSE - BEDIOSSE L6" 17
"trips.txt" "trip_headsign" "DAX - PEM (GARE SNCF)" 18
"trips.txt" "trip_headsign" "NARROSSE - BEDIOSSE L6" 19
"trips.txt" "trip_headsign" "NARROSSE - BEDIOSSE L6" 20
"trips.txt" "trip_headsign" "NARROSSE - BEDIOSSE L6" 21
"trips.txt" "trip_headsign" "NARROSSE - BEDIOSSE L6" 22
"trips.txt" "trip_headsign" "NARROSSE - BEDIOSSE L6" 23
"trips.txt" "trip_headsign" "NARROSSE - BEDIOSSE L6" 24
"trips.txt" "trip_headsign" "NARROSSE - BEDIOSSE L6" 25
"trips.txt" "trip_headsign" "ST VINCENT DE PAUL - BERCEAU" 26
"trips.txt" "trip_headsign" "ST VINCENT DE PAUL - BERCEAU" 27
"trips.txt" "trip_headsign" "ST VINCENT DE PAUL - MAIRIE" 28
"trips.txt" "trip_headsign" "ST VINCENT DE PAUL - MAIRIE" 29
"trips.txt" "trip_headsign" "DAX - PEM (GARE SNCF)" 30
"trips.txt" "trip_headsign" "ST VINCENT DE PAUL - BERCEAU" 31
"trips.txt" "trip_headsign" "ST VINCENT DE PAUL - BERCEAU" 32
"trips.txt" "trip_headsign" "ST VINCENT DE PAUL - BERCEAU" 33
"trips.txt" "trip_headsign" "ST VINCENT DE PAUL - BERCEAU" 34
"trips.txt" "trip_headsign" "ST VINCENT DE PAUL - BUGLOSE ECOLE" 35
"trips.txt" "trip_headsign" "ST VINCENT DE PAUL - BERCEAU" 36
"trips.txt" "trip_headsign" "ST VINCENT DE PAUL - BERCEAU" 37
"trips.txt" "trip_headsign" "ST VINCENT DE PAUL - BERCEAU" 38
"trips.txt" "trip_headsign" "ST VINCENT DE PAUL - BERCEAU" 39
"trips.txt" "trip_headsign" "DAX - VILLAGE LANDAIS" 40
"trips.txt" "trip_headsign" "DAX - VILLAGE LANDAIS" 41
"trips.txt" "trip_headsign" "DAX - VILLAGE LANDAIS" 42
"trips.txt" "trip_headsign" "DAX - VILLAGE LANDAIS" 43
"trips.txt" "trip_headsign" "DAX - VILLAGE LANDAIS" 44
"trips.txt" "trip_headsign" "DAX - VILLAGE LANDAIS" 45
"trips.txt" "trip_headsign" "DAX - VILLAGE LANDAIS" 46
"trips.txt" "trip_headsign" "DAX - VILLAGE LANDAIS" 47
"trips.txt" "trip_headsign" "DAX - PEM (GARE SNCF)" 48
"trips.txt" "trip_headsign" "DAX - VILLAGE LANDAIS" 49
"trips.txt" "trip_headsign" "DAX - VILLAGE LANDAIS" 50
"trips.txt" "trip_headsign" "DAX - VILLAGE LANDAIS" 51
route_long_name_contains_short_name WARNING 7

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`.
"100878-GDUC00014027940202" 2 "1" "1 Barradeau - Bediosse"
"100878-GDUC00024027940088" 3 "2" "2 College Danielle Mitterrand - Lanot"
"100878-GDUC00034027940300" 4 "3" "3 Christus Centre DE Loisirs - VX Bourg"
"100878-GDUC00044027940088" 5 "4" "4 Bruyeres - Village Landais"
"100878-GDUC00054008840314" 6 "5" "5 Bellevue - PEM Gare Sncf"
"100878-GDUC00064028340202" 7 "6" "6 Mairie - Bediosse"
"100878-GDUC00074027940088" 8 "7" "7 Christus Centre DE Loisirs - Bois DE Boulogne"