GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-13T04:14:38Z,
for the dataset file:///shared/transvilles2.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

Feed Info

Publisher Name:
N/A
Publisher URL:
N/A
Feed Email:
N/A
Feed Language:
N/A

Files included

  1. agency.txt
  2. calendar.txt
  3. calendar_dates.txt
  4. routes.txt
  5. shapes.txt
  6. stop_times.txt
  7. stops.txt
  8. trips.txt

Counts

  • Agencies: 4
  • Blocks: 3952
  • Routes: 97
  • Shapes: 385
  • Stops: 1893
  • Trips: 11533

Specification Compliance report

12532 notices reported (2 errors, 12530 warnings, 0 infos)

Notice Code Severity Total
foreign_key_violation ERROR 2

foreign_key_violation

Wrong foreign key.

A foreign key references the primary key of another file. A foreign key violation means that the foreign key referenced from a given row (the child file) cannot be found in the corresponding file (the parent file). The Foreign keys are defined in the specification under "Type" for each file.

You can see more about this notice here.

childFilename (?) The name of the file from which reference is made. childFieldName (?) The name of the field that makes reference. parentFilename (?) The name of the file that is referred to. parentFieldName (?) The name of the field that is referred to. fieldValue (?) The faulty record's value. csvRowNumber (?) The row of the faulty record.
"stop_times.txt" "trip_id" "trips.txt" "trip_id" "6256760-NS2526-LUN_NS-Semaine-03" 104967
"stop_times.txt" "trip_id" "trips.txt" "trip_id" "6282560-NS2526-LUN_NS-Semaine-04" 130682
duplicate_route_name WARNING 18

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`.
2 "1-28449" 3 "1-28453" "L1" "Marly - Petite-Forêt" 3 "7"
4 "2-28449" 5 "2-28453" "L2" "St Waast - Crespin / Quiévrechain" 3 "7"
6 "3-28449" 7 "3-28453" "3" "M Peruwelz - Condé hotel de ville" 3 "7"
8 "4-28449" 9 "4-28453" "4" "DOUCHY E Littré-ROEULX/ESCAUDAIN" 3 "7"
10 "5-28449" 11 "5-28453" "5" "BRUAY Place-VALENCIENNES Gare" 3 "7"
12 "7-28449" 13 "7-28453" "CRL" "Corol - P F Ctre Cc /Beuvrages-Anzin" 3 "7"
16 "11-28449" 17 "11-28453" "11" "TRITH de Vinci - VALENCIENNES G" 3 "7"
18 "12-28449" 19 "12-28453" "12" "Anzin Hôtel de Ville - Saint Amand Elnon" 3 "7"
23 "16-28449" 24 "16-28453" "16" "DENAIN E Villars-VALENCIENNES G" 3 "7"
33 "102-28449" 34 "102-28453" "102" "Maing - THIANT Collège - P F Ctre Ccial" 3 "7"
41 "113-28449" 42 "113-28453" "113" "BEUVRAGES R d droit-Valenciennes Gare" 3 "7"
43 "115-28449" 44 "115-28453" "115" "P F Ctre Ccial - Valenciennes Gare" 3 "7"
52 "187-28449" 53 "187-28453" "C2" "Navette centre ville CORDON 2" 3 "7"
54 "188-28449" 55 "188-28453" "C3" "Navette centre ville CORDON 3" 3 "7"
58 "194-28451" 59 "194-28453" "AMD" "Navette AMANDITOUR" 3 "7"
60 "197-28449" 61 "197-28453" "C1" "Navette centre ville CORDON 1" 3 "7"
62 "198-28449" 63 "198-28453" "VLX" "Navette DENAIN / VILLARS EXPRESS" 3 "7"
64 "200-28449" 65 "200-28453" "SCO" "Scolaire Transvilles" 3 "7"
expired_calendar WARNING 17

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.
2 "AN2526-ALUN-Semaine-00"
3 "AN2526-ALUN-Semaine-00-1111100"
4 "AN2526-ALUN-Semaine-00-1111000"
5 "AN2526-ALUN-Semaine-00-0000100"
6 "AN2526-ASAN-Samedi-00"
7 "AN2526-ASAN-Samedi-00-0000010"
8 "AS2526-ALUS-L-Ma-J-V-00"
9 "AS2526-ALUS-L-Ma-J-V-00-1101100"
10 "AS2526-ALUS-L-Ma-J-V-00-1101000"
11 "AS2526-ALUS-L-Ma-J-V-00-0000100"
12 "AS2526-AMES-Mercredi-00"
13 "AS2526-AMES-Mercredi-00-0010000"
14 "AS2526-ASAS-Samedi-00"
28 "NS2526-LUN_NS-Semaine-03"
29 "NS2526-SAN_NS-Samedi-05"
30 "NS2526-SAN_NS-Samedi-05-0000010"
32 "NS2526-LUN_NS-Semaine-04"
missing_recommended_file WARNING 1

missing_recommended_file

A recommended file is missing.

You can see more about this notice here.

filename (?) The name of the faulty file.
"feed_info.txt"
mixed_case_recommended_field WARNING 12492

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 12492 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" "VALENCIENNES GARE" 2
"trips.txt" "trip_headsign" "VALENCIENNES GARE" 5
"trips.txt" "trip_headsign" "ST-AMAND L. COUTEAUX" 6
"trips.txt" "trip_headsign" "WALLERS GARE" 7
"trips.txt" "trip_headsign" "WALLERS GARE" 8
"trips.txt" "trip_headsign" "ST-AMAND L. COUTEAUX" 9
"trips.txt" "trip_headsign" "WALLERS GARE" 10
"trips.txt" "trip_headsign" "WALLERS GARE" 11
"trips.txt" "trip_headsign" "ST-AMAND L. COUTEAUX" 12
"trips.txt" "trip_headsign" "DENAIN ESP. VILLARS" 13
"trips.txt" "trip_headsign" "DENAIN ESP. VILLARS" 14
"trips.txt" "trip_headsign" "DENAIN ESP. VILLARS" 15
"trips.txt" "trip_headsign" "DENAIN ESP. VILLARS" 16
"trips.txt" "trip_headsign" "DENAIN ESP. VILLARS" 17
"trips.txt" "trip_headsign" "DENAIN ESP. VILLARS" 18
"trips.txt" "trip_headsign" "DENAIN ESP. VILLARS" 19
"trips.txt" "trip_headsign" "DENAIN ESP. VILLARS" 20
"trips.txt" "trip_headsign" "WALLERS GARE" 21
"trips.txt" "trip_headsign" "CONDE/PISCINE ST AMD" 22
"trips.txt" "trip_headsign" "SAINT AMAND SNCF" 23
"trips.txt" "trip_headsign" "ST AMAND PAR PISCINE" 24
"trips.txt" "trip_headsign" "SAINT AMAND SNCF" 25
"trips.txt" "trip_headsign" "SEBOURG TRIEZ" 26
"trips.txt" "trip_headsign" "SEBOURG TRIEZ" 27
"trips.txt" "trip_headsign" "SEBOURG TRIEZ" 28
"trips.txt" "trip_headsign" "VALS ESPLANADE" 29
"trips.txt" "trip_headsign" "VALS ESPLANADE" 30
"trips.txt" "trip_headsign" "VALS ESPLANADE" 31
"trips.txt" "trip_headsign" "VALS ESPLANADE" 32
"trips.txt" "trip_headsign" "SEBOURG TRIEZ" 33
"trips.txt" "trip_headsign" "ABSCON REPUBLIQUE" 34
"trips.txt" "trip_headsign" "DENAIN ESPACE VILLARS" 35
"trips.txt" "trip_headsign" "DENAIN ESPACE VILLARS" 36
"trips.txt" "trip_headsign" "DENAIN ESPACE VILLARS" 37
"trips.txt" "trip_headsign" "DENAIN ESPACE VILLARS" 38
"trips.txt" "trip_headsign" "ABSCON REPUBLIQUE" 39
"trips.txt" "trip_headsign" "ABSCON REPUBLIQUE" 40
"trips.txt" "trip_headsign" "ABSCON REPUBLIQUE" 41
"trips.txt" "trip_headsign" "NEUVILLE CIMETIERE" 42
"trips.txt" "trip_headsign" "NEUVILLE CIMETIERE" 43
"trips.txt" "trip_headsign" "NEUVILLE CIMETIERE" 44
"trips.txt" "trip_headsign" "NEUVILLE CIMETIERE" 45
"trips.txt" "trip_headsign" "NEUVILLE CIMETIERE" 46
"trips.txt" "trip_headsign" "NEUVILLE CIMETIERE" 47
"trips.txt" "trip_headsign" "NEUVILLE CIMETIERE" 48
"trips.txt" "trip_headsign" "NEUVILLE CIMETIERE" 49
"trips.txt" "trip_headsign" "NEUVILLE CIMETIERE" 50
"trips.txt" "trip_headsign" "NEUVILLE CIMETIERE" 51
"trips.txt" "trip_headsign" "NEUVILLE CIMETIERE" 52
"trips.txt" "trip_headsign" "NEUVILLE CIMETIERE" 53
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.
"20251213" "20251024" "20251219"
unused_shape WARNING 1

unused_shape

Shape is not used in GTFS file trips.txt.

All records defined by GTFS shapes.txt should be used in trips.txt.

You can see more about this notice here.

shapeId (?) The faulty record's id. csvRowNumber (?) The row number of the faulty record.
"CAR0002" 241982