tacoluc-en-provence — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-08-15T09:53:19Z,
for the dataset file:///shared/tacoluc-en-provence_8683e8f6.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: 1
  • Blocks: 0
  • Routes: 1
  • Shapes: 8
  • Stops: 54
  • Trips: 40

Specification Compliance report

1625 notices reported (0 errors, 1585 warnings, 40 infos)

Notice Code Severity Total
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.
6 "F_2526#SCOL#LM_JV__#20260601-20260703"
7 "F_2526#SCOL#_M__V__#20260601-20260703"
8 "F_2526#SCOL#__C____#20260601-20260703"
9 "F_2526#SCOL#_____S_#20260601-20260703"
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"
missing_timepoint_value WARNING 1578

missing_timepoint_value

stop_times.timepoint value is missing for a record.

When at least one of stop_times.arrival_time or stop_times.departure_time are provided, stop_times.timepoint should be defined

You can see more about this notice here.

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

csvRowNumber (?) The row number of the faulty record. tripId (?) The faulty record's `stop_times.trip_id`. stopSequence (?) The faulty record's `stop_times.stop_sequence`.
2 "1" 1
3 "1" 2
4 "1" 3
5 "1" 4
6 "1" 5
7 "1" 6
8 "1" 7
9 "1" 8
10 "1" 9
11 "1" 10
12 "1" 11
13 "1" 12
14 "1" 13
15 "1" 14
16 "1" 15
17 "1" 16
18 "1" 17
19 "1" 18
20 "1" 19
21 "1" 20
22 "1" 21
23 "1" 22
24 "1" 23
25 "10" 1
26 "10" 2
27 "10" 3
28 "10" 4
29 "10" 5
30 "10" 6
31 "10" 7
32 "10" 8
33 "10" 9
34 "10" 10
35 "10" 11
36 "10" 12
37 "10" 13
38 "10" 14
39 "10" 15
40 "10" 16
41 "10" 17
42 "10" 18
43 "10" 19
44 "10" 20
45 "10" 21
46 "10" 22
47 "10" 23
48 "11" 1
49 "11" 2
50 "11" 3
51 "11" 4
mixed_case_recommended_field WARNING 2

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.
"agency.txt" "agency_name" "TRANSDEV VAR" 2
"routes.txt" "route_long_name" "LIGNE TACO" 2
trip_with_shape_dist_traveled_but_no_shape_distances INFO 40

trip_with_shape_dist_traveled_but_no_shape_distances

A trip has shape_dist_traveled values in stop_times.txt but the shape referenced by the trip's shape_id does not have shape_dist_traveled values on all of its points in shapes.txt.

When stop times define distance values but the shape does not carry matching distances on every point, consumers cannot use those distances to align stops to the shape geometry reliably. This inconsistency may cause incorrect routing or display behaviour.

Note: Only the first stop time carrying a shape_dist_traveled value is referenced in the notice; this is a representative row rather than an exhaustive list.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the faulty record in trips.txt. tripId (?) The trip_id of the faulty trip. shapeId (?) The shape_id referenced by the trip. stopTimeCsvRowNumber (?) The row number of the first stop_times.txt record for this trip that contains a shape_dist_traveled value. Provided as a representative location; other stop times for the same trip may also carry distance values.
16 "22" "0" 536
17 "23" "1" 559
18 "24" "2" 595
19 "25" "3" 629
20 "26" "4" 681
21 "27" "1" 731
22 "28" "2" 767
23 "29" "1" 801
25 "30" "5" 873
26 "31" "4" 896
3 "10" "5" 25
27 "32" "3" 946
4 "11" "4" 48
28 "33" "3" 998
5 "12" "3" 98
29 "34" "6" 1050
6 "13" "3" 150
30 "35" "1" 1101
7 "14" "6" 202
31 "36" "7" 1137
8 "15" "1" 253
32 "37" "1" 1176
9 "16" "7" 289
33 "38" "5" 1212
10 "17" "1" 328
34 "39" "3" 1235
11 "18" "5" 364
12 "19" "3" 387
2 "1" "0" 2
13 "2" "0" 439
24 "3" "1" 837
35 "4" "2" 1287
37 "5" "3" 1372
38 "6" "4" 1424
39 "7" "1" 1474
40 "8" "2" 1510
41 "9" "1" 1544
36 "40" "6" 1321
14 "20" "6" 462
15 "21" "0" 513