GTFS Schedule Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2025-12-22T11:24:04Z,
for the dataset file:///shared/sanary-sur-mer.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: 9
  • Shapes: 13
  • Stops: 194
  • Trips: 147

Specification Compliance report

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

Notice Code Severity Total
expired_calendar WARNING 106

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.

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

csvRowNumber (?) The row of the faulty record. serviceId (?) The service id of the faulty record.
3 "22491"
4 "22492"
6 "22494"
7 "22495"
8 "22496"
9 "22497"
10 "22498"
11 "22500"
12 "22501"
13 "22502"
14 "22503"
15 "22504"
16 "22505"
17 "22506"
18 "22507"
19 "22508"
20 "22509"
21 "22510"
22 "22511"
24 "22513"
25 "22514"
26 "22515"
27 "22516"
28 "22517"
29 "22518"
30 "22519"
31 "22520"
32 "22521"
33 "22522"
34 "22523"
35 "22524"
36 "22525"
37 "22526"
38 "22527"
39 "22528"
40 "22529"
41 "22530"
42 "22531"
43 "22533"
44 "22534"
45 "22535"
46 "22536"
47 "22537"
48 "22538"
49 "22539"
50 "22540"
51 "22541"
52 "22542"
53 "22544"
54 "22545"
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 351

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 351 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.
"routes.txt" "route_short_name" "COLOMBUS CIR 1" 2
"routes.txt" "route_short_name" "COLOMBUS CIR 2" 3
"routes.txt" "route_short_name" "COLOMBUS CIR 3" 4
"routes.txt" "route_long_name" "LIGNE TOURISTIQUE ESTIVALE - BANDOL" 5
"routes.txt" "route_long_name" "MARCHE DE SANARY ETE" 6
"routes.txt" "route_short_name" "URBAN CIRC. 1" 7
"routes.txt" "route_short_name" "URBAN CIRC. 2" 8
"routes.txt" "route_short_name" "URBAN CIRC. 3" 9
"routes.txt" "route_short_name" "URBAN CIRC. 4" 10
"trips.txt" "trip_headsign" "SANARY GYMNASE S" 2
"trips.txt" "trip_headsign" "SANARY GYMNASE S" 3
"trips.txt" "trip_headsign" "SANARY CENTRE CULTUREL N" 4
"trips.txt" "trip_headsign" "BANDOL EMBARCADERE S" 5
"trips.txt" "trip_headsign" "SANARY CENTRE CULTUREL N" 6
"trips.txt" "trip_headsign" "SANARY JARDIN D’HIVER" 7
"trips.txt" "trip_headsign" "SANARY CENTRE CULTUREL N" 8
"trips.txt" "trip_headsign" "BANDOL EMBARCADERE S" 9
"trips.txt" "trip_headsign" "SANARY CENTRE CULTUREL N" 10
"trips.txt" "trip_headsign" "SANARY JARDIN D’HIVER" 11
"trips.txt" "trip_headsign" "SANARY GYMNASE N" 12
"trips.txt" "trip_headsign" "SANARY GYMNASE S" 13
"trips.txt" "trip_headsign" "BANDOL EMBARCADERE S" 14
"trips.txt" "trip_headsign" "SANARY JARDIN D’HIVER" 15
"trips.txt" "trip_headsign" "SANARY CENTRE CULTUREL N" 16
"trips.txt" "trip_headsign" "BANDOL EMBARCADERE S" 17
"trips.txt" "trip_headsign" "SANARY CENTRE CULTUREL N" 18
"trips.txt" "trip_headsign" "SANARY JARDIN D’HIVER" 19
"trips.txt" "trip_headsign" "BANDOL EMBARCADERE S" 20
"trips.txt" "trip_headsign" "BANDOL EMBARCADERE S" 21
"trips.txt" "trip_headsign" "SANARY GYMNASE S" 22
"trips.txt" "trip_headsign" "SANARY JARDIN D’HIVER" 23
"trips.txt" "trip_headsign" "SANARY CENTRE CULTUREL N" 24
"trips.txt" "trip_headsign" "BANDOL EMBARCADERE S" 25
"trips.txt" "trip_headsign" "BANDOL EMBARCADERE S" 26
"trips.txt" "trip_headsign" "BANDOL EMBARCADERE S" 27
"trips.txt" "trip_headsign" "SANARY CENTRE CULTUREL N" 28
"trips.txt" "trip_headsign" "SANARY JARDIN D’HIVER" 29
"trips.txt" "trip_headsign" "BANDOL EMBARCADERE S" 30
"trips.txt" "trip_headsign" "SANARY GYMNASE S" 31
"trips.txt" "trip_headsign" "SANARY JARDIN D’HIVER" 32
"trips.txt" "trip_headsign" "BANDOL EMBARCADERE S" 33
"trips.txt" "trip_headsign" "BANDOL EMBARCADERE S" 34
"trips.txt" "trip_headsign" "SANARY CENTRE CULTUREL N" 35
"trips.txt" "trip_headsign" "BANDOL EMBARCADERE S" 36
"trips.txt" "trip_headsign" "BANDOL EMBARCADERE S" 37
"trips.txt" "trip_headsign" "SANARY GYMNASE S" 38
"trips.txt" "trip_headsign" "SANARY CENTRE CULTUREL N" 39
"trips.txt" "trip_headsign" "SANARY JARDIN D’HIVER" 40
"trips.txt" "trip_headsign" "BANDOL EMBARCADERE S" 41
"trips.txt" "trip_headsign" "BANDOL EMBARCADERE S" 42
route_short_name_too_long WARNING 7

route_short_name_too_long

Short name of a route is too long (more than 12 characters).

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`.
"COLOMBUS CIR 1" 2 "COLOMBUS CIR 1"
"COLOMBUS CIR 2" 3 "COLOMBUS CIR 2"
"COLOMBUS CIR 3" 4 "COLOMBUS CIR 3"
"URBAN CIRC. 1" 7 "URBAN CIRC. 1"
"URBAN CIRC. 2" 8 "URBAN CIRC. 2"
"URBAN CIRC. 3" 9 "URBAN CIRC. 3"
"URBAN CIRC. 4" 10 "URBAN CIRC. 4"
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.
"20251222" "20250701" "20250830"