reseau-urbain-lislenbus-commune — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-09-02T19:17:40Z,
for the dataset file:///shared/reseau-urbain-lislenbus-commune_53ac9def.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. stop_times.txt
  6. stops.txt
  7. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 2
  • Shapes: 0
  • Stops: 62
  • Trips: 21

Specification Compliance report

142 notices reported (21 errors, 37 warnings, 84 infos)

Notice Code Severity Total
foreign_key_violation ERROR 21

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.
"trips.txt" "shape_id" "shapes.txt" "shape_id" "1" 2
"trips.txt" "shape_id" "shapes.txt" "shape_id" "1" 3
"trips.txt" "shape_id" "shapes.txt" "shape_id" "1" 4
"trips.txt" "shape_id" "shapes.txt" "shape_id" "1" 5
"trips.txt" "shape_id" "shapes.txt" "shape_id" "1" 6
"trips.txt" "shape_id" "shapes.txt" "shape_id" "1" 7
"trips.txt" "shape_id" "shapes.txt" "shape_id" "1" 8
"trips.txt" "shape_id" "shapes.txt" "shape_id" "8" 9
"trips.txt" "shape_id" "shapes.txt" "shape_id" "8" 10
"trips.txt" "shape_id" "shapes.txt" "shape_id" "8" 11
"trips.txt" "shape_id" "shapes.txt" "shape_id" "8" 12
"trips.txt" "shape_id" "shapes.txt" "shape_id" "8" 13
"trips.txt" "shape_id" "shapes.txt" "shape_id" "8" 14
"trips.txt" "shape_id" "shapes.txt" "shape_id" "14" 15
"trips.txt" "shape_id" "shapes.txt" "shape_id" "14" 16
"trips.txt" "shape_id" "shapes.txt" "shape_id" "14" 17
"trips.txt" "shape_id" "shapes.txt" "shape_id" "14" 18
"trips.txt" "shape_id" "shapes.txt" "shape_id" "18" 19
"trips.txt" "shape_id" "shapes.txt" "shape_id" "18" 20
"trips.txt" "shape_id" "shapes.txt" "shape_id" "18" 21
"trips.txt" "shape_id" "shapes.txt" "shape_id" "18" 22
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 31

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.
"routes.txt" "route_long_name" "LISLE SUR TARN 1" 2
"routes.txt" "route_long_name" "LISLE SUR TARN 2" 3
"trips.txt" "trip_headsign" "LISLE SUR TARN - COLLEGE" 2
"trips.txt" "trip_headsign" "LISLE SUR TARN - COLLEGE" 3
"trips.txt" "trip_headsign" "LISLE SUR TARN - COLLEGE" 4
"trips.txt" "trip_headsign" "LISLE SUR TARN - COLLEGE" 5
"trips.txt" "trip_headsign" "LISLE SUR TARN - COLLEGE" 6
"trips.txt" "trip_headsign" "LISLE SUR TARN - COLLEGE" 7
"trips.txt" "trip_headsign" "LISLE SUR TARN - COLLEGE" 8
"trips.txt" "trip_headsign" "LISLE SUR TARN - LES ROBERTES URBAIN" 9
"trips.txt" "trip_headsign" "LISLE SUR TARN - LES ROBERTES URBAIN" 10
"trips.txt" "trip_headsign" "LISLE SUR TARN - LES ROBERTES URBAIN" 11
"trips.txt" "trip_headsign" "LISLE SUR TARN - LES ROBERTES URBAIN" 12
"trips.txt" "trip_headsign" "LISLE SUR TARN - LES ROBERTES URBAIN" 13
"trips.txt" "trip_headsign" "LISLE SUR TARN - LES ROBERTES URBAIN" 14
"trips.txt" "trip_headsign" "MONTANS - PECH DU TAUR" 15
"trips.txt" "trip_headsign" "MONTANS - PECH DU TAUR" 16
"trips.txt" "trip_headsign" "MONTANS - PECH DU TAUR" 17
"trips.txt" "trip_headsign" "MONTANS - PECH DU TAUR" 18
"trips.txt" "trip_headsign" "LISLE SUR TARN - LES ROBERTES URBAIN" 19
"trips.txt" "trip_headsign" "LISLE SUR TARN - LES ROBERTES URBAIN" 20
"trips.txt" "trip_headsign" "LISLE SUR TARN - LES ROBERTES URBAIN" 21
"trips.txt" "trip_headsign" "LISLE SUR TARN - LES ROBERTES URBAIN" 22
"stops.txt" "stop_name" "LISLE SUR TARN - NOYERE" 42
"stops.txt" "stop_name" "LISLE SUR TARN - NOYERE" 43
"stops.txt" "stop_name" "LISLE SUR TARN - NOYERE" 44
"stops.txt" "stop_name" "LISLE SUR TARN - NOYERE" 45
"stops.txt" "stop_name" "LISLE SUR TARN - POLE D'ECHANGES MULTIMODAL" 52
"stops.txt" "stop_name" "LISLE SUR TARN - POLE D'ECHANGES MULTIMODAL" 53
"stops.txt" "stop_name" "LISLE SUR TARN - POLE D'ECHANGES MULTIMODAL" 54
"stops.txt" "stop_name" "LISLE SUR TARN - POLE D'ECHANGES MULTIMODAL" 55
stop_without_stop_time WARNING 5

stop_without_stop_time

A stop in stops.txt is not referenced by any stop_times.stop_id.

Such stops are not used by any trip and normally do not provide user value. This notice may indicate a typo in stop_times.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record. stopId (?) The id of the faulty stop. stopName (?) The name of the faulty stop.
4 "242103" "Barbara"
10 "122503" "Bellevue"
42 "122903" "LISLE SUR TARN - NOYERE"
48 "301703" "Plaine des sports"
52 "122603" "LISLE SUR TARN - POLE D'ECHANGES MULTIMODAL"
big_gap_in_service INFO 84

big_gap_in_service

A service has a gap of more than 13 days between active service dates.

You can see more about this notice here.

Only the first 50 of 84 affected records are displayed below.

serviceId (?) The service_id that has the gap. gapStartDate (?) The first day of the gap. gapEndDate (?) The last day of the gap. gapDurationDays (?) The number of days in the gap.
"3844" "2026-10-16" "2026-11-02" 16
"3844" "2026-12-18" "2027-01-04" 16
"3844" "2027-02-05" "2027-02-22" 16
"3844" "2027-04-02" "2027-04-19" 16
"3845" "2026-10-16" "2026-11-02" 16
"3845" "2026-12-18" "2027-01-04" 16
"3845" "2027-02-05" "2027-02-22" 16
"3845" "2027-04-02" "2027-04-19" 16
"3846" "2026-10-16" "2026-11-02" 16
"3846" "2026-12-18" "2027-01-04" 16
"3846" "2027-02-05" "2027-02-22" 16
"3846" "2027-04-02" "2027-04-19" 16
"3847" "2026-10-14" "2026-11-04" 20
"3847" "2026-12-16" "2027-01-06" 20
"3847" "2027-02-03" "2027-02-24" 20
"3847" "2027-03-31" "2027-04-21" 20
"3848" "2026-10-14" "2026-11-04" 20
"3848" "2026-12-16" "2027-01-06" 20
"3848" "2027-02-03" "2027-02-24" 20
"3848" "2027-03-31" "2027-04-21" 20
"3849" "2026-10-16" "2026-11-02" 16
"3849" "2026-12-18" "2027-01-04" 16
"3849" "2027-02-05" "2027-02-22" 16
"3849" "2027-04-02" "2027-04-19" 16
"3850" "2026-10-16" "2026-11-02" 16
"3850" "2026-12-18" "2027-01-04" 16
"3850" "2027-02-05" "2027-02-22" 16
"3850" "2027-04-02" "2027-04-19" 16
"3851" "2026-10-16" "2026-11-02" 16
"3851" "2026-12-18" "2027-01-04" 16
"3851" "2027-02-05" "2027-02-22" 16
"3851" "2027-04-02" "2027-04-19" 16
"3852" "2026-10-16" "2026-11-02" 16
"3852" "2026-12-18" "2027-01-04" 16
"3852" "2027-02-05" "2027-02-22" 16
"3852" "2027-04-02" "2027-04-19" 16
"3853" "2026-10-16" "2026-11-02" 16
"3853" "2026-12-18" "2027-01-04" 16
"3853" "2027-02-05" "2027-02-22" 16
"3853" "2027-04-02" "2027-04-19" 16
"3854" "2026-10-16" "2026-11-02" 16
"3854" "2026-12-18" "2027-01-04" 16
"3854" "2027-02-05" "2027-02-22" 16
"3854" "2027-04-02" "2027-04-19" 16
"3855" "2026-10-16" "2026-11-02" 16
"3855" "2026-12-18" "2027-01-04" 16
"3855" "2027-02-05" "2027-02-22" 16
"3855" "2027-04-02" "2027-04-19" 16
"3856" "2026-10-14" "2026-11-04" 20
"3856" "2026-12-16" "2027-01-06" 20