GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 5.0.1 at 2024-06-12T03:52: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:
2024-06-08
Feed End Date:
2024-07-10

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. transfers.txt
  9. trips.txt

Counts

  • Agencies: 3
  • Blocks: 1
  • Routes: 41
  • Shapes: 0
  • Stops: 3097
  • Trips: 51506

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

TransfersFeed InformationRoute ColorsHeadsignsWheelchair AccessibilityBikes AllowanceLocation Types

Specification Compliance report

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

Notice Code Severity Total
duplicate_route_name WARNING 5

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`.
5 "921-IDFM:C01746" 16 "921-IDFM:C01863" "TER" "TER Hauts-de-France" 2 "921-IDFM:93"
4 "921-IDFM:C01744" 37 "921-IDFM:C02368" "TER" "TER Centre - Val de Loire" 2 "921-IDFM:93"
14 "921-IDFM:C01748" 38 "921-IDFM:C02370" "TER" "TER Normandie" 2 "921-IDFM:93"
5 "921-IDFM:C01746" 39 "921-IDFM:C02372" "TER" "TER Hauts-de-France" 2 "921-IDFM:93"
14 "921-IDFM:C01748" 40 "921-IDFM:C02375" "TER" "TER Normandie" 2 "921-IDFM:93"
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.
289 "921-IDFM:TN:7246202"
290 "921-IDFM:TN:7164966"
291 "921-IDFM:TN:7138556"
292 "921-IDFM:TN:7111014"
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 "20240612" "20240710" "20240712"
mixed_case_recommended_field WARNING 43

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.

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" "pl.du 19 mars 1962" 1684
"stops.txt" "stop_name" "pl. du 19 mars 1962" 1685
"stops.txt" "stop_name" "voie 1" 1751
"stops.txt" "stop_name" "voie 2" 1752
"stops.txt" "stop_name" "pl. de la gare (côté voie 2 et bâtiment voyageur)" 1757
"stops.txt" "stop_name" "rte départementale" 1761
"stops.txt" "stop_name" "r. du 8 mai 1945" 1811
"stops.txt" "stop_name" "pl. du 8 mai 1945" 1832
"stops.txt" "stop_name" "pl. du 8 mai 1945" 1878
"stops.txt" "stop_name" "r. de la gare" 1894
"stops.txt" "stop_name" "pl. du 8 mai 1945" 1916
"stops.txt" "stop_name" "pl. du 8 mai 1945 (principale)" 1927
"stops.txt" "stop_name" "pl. du 8 mai 1945 (secondaire)" 1928
"stops.txt" "stop_name" "av. kellermann" 1942
"stops.txt" "stop_name" "r. de la petite vitesse" 2003
"stops.txt" "stop_name" "av. de la gare" 2059
"stops.txt" "stop_name" "r. de petit vaux" 2111
"stops.txt" "stop_name" "r. de petit vaux" 2112
"stops.txt" "stop_name" "pl. de la gare" 2128
"stops.txt" "stop_name" "r. de l'aqueduc" 2137
"stops.txt" "stop_name" "r. des deux gares" 2207
"stops.txt" "stop_name" "pl. du 8 mai 1945 (bâtiment voyageur)" 2299
"stops.txt" "stop_name" "pl. du 8 mai 1945" 2300
"stops.txt" "stop_name" "pl. du 8 mai 1945" 2301
"stops.txt" "stop_name" "av. de la gare" 2359
"stops.txt" "stop_name" "pl. du 8 mai 1945" 2394
"stops.txt" "stop_name" "pl. de la gare" 2494
"stops.txt" "stop_name" "av. du 8 mai 45" 2531
"stops.txt" "stop_name" "av. du 8 mai 45" 2532
"stops.txt" "stop_name" "av. du 8 mai 45" 2536
"stops.txt" "stop_name" "pl. du 8 mai 1945" 2544
"stops.txt" "stop_name" "voie 2 (côté gare)" 2607
"stops.txt" "stop_name" "pl. de la gare" 2633
"stops.txt" "stop_name" "pl. de la gare" 2634
"stops.txt" "stop_name" "pl. de la gare" 2657
"stops.txt" "stop_name" "pl. de la gare" 2658
"stops.txt" "stop_name" "24 rue du départ" 2665
"stops.txt" "stop_name" "25 rue de l'arrivée" 2666
"stops.txt" "stop_name" "all. du 8 mai 1945" 2720
"stops.txt" "stop_name" "r. de la porte de buc" 2727
"stops.txt" "stop_name" "pl. de la gare" 2754
"stops.txt" "stop_name" "pl. de la gare" 2971
"stops.txt" "stop_name" "pl. de la gare" 2972
route_long_name_contains_short_name WARNING 11

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`.
"921-IDFM:C01745" 3 "TER" "TER Bourgogne - Franche-Comté"
"921-IDFM:C01744" 4 "TER" "TER Centre - Val de Loire"
"921-IDFM:C01746" 5 "TER" "TER Hauts-de-France"
"921-IDFM:C01748" 14 "TER" "TER Normandie"
"921-IDFM:C01863" 16 "TER" "TER Hauts-de-France"
"921-IDFM:C01747" 29 "TER" "TER Grand-Est"
"921-IDFM:C01857" 33 "TER" "TER Centre - Val-de-Loire"
"921-IDFM:C02368" 37 "TER" "TER Centre - Val de Loire"
"921-IDFM:C02370" 38 "TER" "TER Normandie"
"921-IDFM:C02372" 39 "TER" "TER Hauts-de-France"
"921-IDFM:C02375" 40 "TER" "TER Normandie"