GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 5.0.1 at 2024-06-08T09:03:44Z,
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-01
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. stop_times.txt
  7. stops.txt
  8. trips.txt

Counts

  • Agencies: 1
  • Blocks: 1
  • Routes: 14
  • Shapes: 0
  • Stops: 305
  • Trips: 381

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

Feed InformationRoute ColorsHeadsignsWheelchair AccessibilityLocation Types

Specification Compliance report

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

Notice Code Severity Total
duplicate_route_name WARNING 2

duplicate_route_name

Two distinct routes have either the same route_short_name, the same route_long_name, or the same combination of route_short_name and route_long_name.

All routes of the same route_type with the same agency_id should have unique combinations of route_short_name and route_long_name.

Note that there may be valid cases where routes have the same short and long name, e.g., if they serve different areas. However, different directions must be modeled as the same route.

Example of bad data:

route_id route_short_name route_long_name
route1 U1 Southern
route2 U1 Southern

You can see more about this notice here.

csvRowNumber1 (?) The row number of the first occurrence. routeId1 (?) The id of the the first occurrence. csvRowNumber2 (?) The row number of the other occurrence. routeId2 (?) The id of the the other occurrence. routeShortName (?) Common `routes.route_short_name`. routeLongName (?) Common `routes.route_long_name`. routeTypeValue (?) Common `routes.route_type`. agencyId (?) Common `routes.agency_id`.
3 "101105-MXUY00034018740310" 7 "101105-MXUY00314018740310" "3" "3 Soustons - Moliets ET Maa" 3 "101105-9"
9 "101105-MXUY00914030440304" 10 "101105-MXUY00924030440304" "H" "H Hossegor Office DE Tourisme - Plages" 3 "101105-9"
expired_calendar WARNING 8

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.
22 "101105-44981"
23 "101105-44983"
29 "101105-45176"
30 "101105-45177"
25 "101105-44996"
2 "101105-39245"
28 "101105-45160"
19 "101105-44759"
mixed_case_recommended_field WARNING 381

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 381 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" "SOORTS HOSSEGOR - OFFICE DE TOURISME" 2
"trips.txt" "trip_headsign" "SOORTS HOSSEGOR - OFFICE DE TOURISME" 3
"trips.txt" "trip_headsign" "SOORTS HOSSEGOR - OFFICE DE TOURISME" 4
"trips.txt" "trip_headsign" "SOORTS HOSSEGOR - OFFICE DE TOURISME" 5
"trips.txt" "trip_headsign" "SOORTS HOSSEGOR - OFFICE DE TOURISME" 6
"trips.txt" "trip_headsign" "SOORTS HOSSEGOR - OFFICE DE TOURISME" 7
"trips.txt" "trip_headsign" "SEIGNOSSE - BOURG ECOLE / ARRET YEGO" 8
"trips.txt" "trip_headsign" "SEIGNOSSE - BOURG ECOLE / ARRET YEGO" 9
"trips.txt" "trip_headsign" "SEIGNOSSE - BOURG ECOLE / ARRET YEGO" 10
"trips.txt" "trip_headsign" "SEIGNOSSE - BOURG ECOLE / ARRET YEGO" 11
"trips.txt" "trip_headsign" "SEIGNOSSE - BOURG ECOLE / ARRET YEGO" 12
"trips.txt" "trip_headsign" "SEIGNOSSE - BOURG ECOLE / ARRET YEGO" 13
"trips.txt" "trip_headsign" "SEIGNOSSE - BOURG ECOLE / ARRET YEGO" 14
"trips.txt" "trip_headsign" "MESSANGES - PLAGE" 15
"trips.txt" "trip_headsign" "AZUR - CAMPING LANDES AZUR" 16
"trips.txt" "trip_headsign" "SOORTS HOSSEGOR - OFFICE DE TOURISME" 17
"trips.txt" "trip_headsign" "SEIGNOSSE - BOURG ECOLE / ARRET YEGO" 18
"trips.txt" "trip_headsign" "ST VINCENT DE TYROSSE - LYCEE" 19
"trips.txt" "trip_headsign" "ST VINCENT DE TYROSSE - LYCEE" 20
"trips.txt" "trip_headsign" "ST VINCENT DE TYROSSE - LYCEE" 21
"trips.txt" "trip_headsign" "ST VINCENT DE TYROSSE - LYCEE" 22
"trips.txt" "trip_headsign" "ST VINCENT DE TYROSSE - LYCEE" 23
"trips.txt" "trip_headsign" "ST VINCENT DE TYROSSE - LYCEE" 24
"trips.txt" "trip_headsign" "ST VINCENT DE TYROSSE - LYCEE" 25
"trips.txt" "trip_headsign" "ST VINCENT DE TYROSSE - LYCEE" 26
"trips.txt" "trip_headsign" "ST VINCENT DE TYROSSE - LYCEE" 27
"trips.txt" "trip_headsign" "LABENNE - GARE SNCF" 28
"trips.txt" "trip_headsign" "LABENNE - GARE SNCF" 29
"trips.txt" "trip_headsign" "LABENNE - GARE SNCF" 30
"trips.txt" "trip_headsign" "LABENNE - GARE SNCF" 31
"trips.txt" "trip_headsign" "LABENNE - GARE SNCF" 32
"trips.txt" "trip_headsign" "LABENNE - GARE SNCF" 33
"trips.txt" "trip_headsign" "ST VINCENT DE TYROSSE - LYCEE" 34
"trips.txt" "trip_headsign" "ST VINCENT DE TYROSSE - LYCEE" 35
"trips.txt" "trip_headsign" "ST VINCENT DE TYROSSE - LYCEE" 36
"trips.txt" "trip_headsign" "ST VINCENT DE TYROSSE - LYCEE" 37
"trips.txt" "trip_headsign" "ST VINCENT DE TYROSSE - LYCEE" 38
"trips.txt" "trip_headsign" "LABENNE - GARE SNCF" 39
"trips.txt" "trip_headsign" "LABENNE - GARE SNCF" 40
"trips.txt" "trip_headsign" "LABENNE - GARE SNCF" 41
"trips.txt" "trip_headsign" "LABENNE - GARE SNCF" 42
"trips.txt" "trip_headsign" "LABENNE - GARE SNCF" 43
"trips.txt" "trip_headsign" "SOORTS HOSSEGOR - OFFICE DE TOURISME" 44
"trips.txt" "trip_headsign" "ST VINCENT DE TYROSSE - LYCEE" 45
"trips.txt" "trip_headsign" "ST VINCENT DE TYROSSE - LYCEE" 46
"trips.txt" "trip_headsign" "ST VINCENT DE TYROSSE - LYCEE" 47
"trips.txt" "trip_headsign" "ST VINCENT DE TYROSSE - LYCEE" 48
"trips.txt" "trip_headsign" "LABENNE - GARE SNCF" 49
"trips.txt" "trip_headsign" "LABENNE - GARE SNCF" 50
"trips.txt" "trip_headsign" "ST VINCENT DE TYROSSE - LYCEE" 51
route_long_name_contains_short_name WARNING 10

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`.
"101105-MXUY00024031040261" 2 "2" "2 ST Geours DE Maremne - Soustons"
"101105-MXUY00034018740310" 3 "3" "3 Soustons - Moliets ET Maa"
"101105-MXUY001A4013340284" 4 "1A" "1A Labenne - ST Vincent DE Tyrosse"
"101105-MXUY001B4003640284" 5 "1B" "1B Benesse Maremne - ST Vincent DE Tyrosse"
"101105-MXUY00304018140310" 6 "3P" "3P Soustons - Messanges Plage"
"101105-MXUY00314018740310" 7 "3" "3 Soustons - Moliets ET Maa"
"101105-MXUY00354002140181" 8 "A" "A Azur - Messanges"
"101105-MXUY00914030440304" 9 "H" "H Hossegor Office DE Tourisme - Plages"
"101105-MXUY00924030440304" 10 "H" "H Hossegor Office DE Tourisme - Plages"
"101105-MXUY00974027140065" 15 "E" "E STE Marie DE Gosse - Capbreton Plage"
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" "20230102" "20240525"