GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 5.0.1 at 2024-06-07T16:39:28Z,
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:
2024-05-28
Feed End Date:
2024-07-07

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: 1457
  • Routes: 83
  • Shapes: 336
  • Stops: 1107
  • Trips: 5887

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

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

Notice Code Severity Total
feed_expiration_date30_days WARNING 1

feed_expiration_date30_days

Dataset should cover at least the next 30 days of service.

At any time, the GTFS dataset should cover at least the next 30 days of service, and ideally for as long as the operator is confident that the schedule will continue to be operated.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. currentDate (?) Current date (YYYYMMDD format). feedEndDate (?) Feed end date (YYYYMMDD format). suggestedExpirationDate (?) Suggested expiration date (YYYYMMDD format).
2 "20240607" "20240707" "20240707"
mixed_case_recommended_field WARNING 3481

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 3481 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.
"stops.txt" "stop_name" "8 MAI 1945" 6
"trips.txt" "trip_headsign" "VILLE ACTIVE" 3
"trips.txt" "trip_headsign" "VILLE ACTIVE" 4
"trips.txt" "trip_headsign" "VILLE ACTIVE" 5
"trips.txt" "trip_headsign" "VILLE ACTIVE" 6
"trips.txt" "trip_headsign" "VILLE ACTIVE" 7
"trips.txt" "trip_headsign" "VILLE ACTIVE" 8
"trips.txt" "trip_headsign" "VILLE ACTIVE" 9
"trips.txt" "trip_headsign" "VILLE ACTIVE" 10
"trips.txt" "trip_headsign" "VILLE ACTIVE" 11
"trips.txt" "trip_headsign" "VILLE ACTIVE" 21
"trips.txt" "trip_headsign" "VILLE ACTIVE" 22
"trips.txt" "trip_headsign" "VILLE ACTIVE" 23
"trips.txt" "trip_headsign" "VILLE ACTIVE" 24
"trips.txt" "trip_headsign" "VILLE ACTIVE" 25
"trips.txt" "trip_headsign" "VILLE ACTIVE" 26
"trips.txt" "trip_headsign" "VILLE ACTIVE" 27
"trips.txt" "trip_headsign" "VILLE ACTIVE" 28
"trips.txt" "trip_headsign" "VILLE ACTIVE" 29
"trips.txt" "trip_headsign" "VILLE ACTIVE" 30
"trips.txt" "trip_headsign" "VILLE ACTIVE" 31
"trips.txt" "trip_headsign" "VILLE ACTIVE" 32
"trips.txt" "trip_headsign" "VILLE ACTIVE" 33
"trips.txt" "trip_headsign" "VILLE ACTIVE" 34
"trips.txt" "trip_headsign" "VILLE ACTIVE" 35
"trips.txt" "trip_headsign" "VILLE ACTIVE" 36
"trips.txt" "trip_headsign" "VILLE ACTIVE" 37
"trips.txt" "trip_headsign" "VILLE ACTIVE" 38
"trips.txt" "trip_headsign" "VILLE ACTIVE" 39
"trips.txt" "trip_headsign" "VILLE ACTIVE" 40
"trips.txt" "trip_headsign" "VILLE ACTIVE" 41
"trips.txt" "trip_headsign" "VILLE ACTIVE" 42
"trips.txt" "trip_headsign" "VILLE ACTIVE" 43
"trips.txt" "trip_headsign" "VILLE ACTIVE" 44
"trips.txt" "trip_headsign" "VILLE ACTIVE" 69
"trips.txt" "trip_headsign" "VILLE ACTIVE" 73
"trips.txt" "trip_headsign" "VILLE ACTIVE" 74
"trips.txt" "trip_headsign" "VILLE ACTIVE" 76
"trips.txt" "trip_headsign" "VILLE ACTIVE" 77
"trips.txt" "trip_headsign" "ROUTE D'ARLES" 101
"trips.txt" "trip_headsign" "ROUTE D'ARLES" 102
"trips.txt" "trip_headsign" "ROUTE D'ARLES" 103
"trips.txt" "trip_headsign" "ROUTE D'ARLES" 104
"trips.txt" "trip_headsign" "ROUTE D'ARLES" 105
"trips.txt" "trip_headsign" "ROUTE D'ARLES" 106
"trips.txt" "trip_headsign" "ROUTE D'ARLES" 107
"trips.txt" "trip_headsign" "ROUTE D'ALES" 108
"trips.txt" "trip_headsign" "ROUTE D'ALES" 109
"trips.txt" "trip_headsign" "ROUTE D'ALES" 110
"trips.txt" "trip_headsign" "ROUTE D'ALES" 111
unexpected_enum_value WARNING 2

unexpected_enum_value

An enum has an unexpected value.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row number of the faulty record. fieldName (?) The name of the field where the error occurred. fieldValue (?) Faulty value.
"routes.txt" 34 "route_type" 715
"routes.txt" 71 "route_type" 715