Home
France Feeds
calais
Source Data Validation Report

calais — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 8.0.1 at 2026-06-19T15:15:16Z,
for the dataset file:///shared/calais_7b298a19.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

sitac
- website: https://www.sitac-calais-opale-bus.fr/
- phone number:
- email: Not provided

Feed Info

Publisher Name:
sitac: Publisher URL:
https://www.sitac-calais-opale-bus.fr/: Feed Email:
N/A: Feed Language:
French: Feed Start Date:
2026-05-25: Feed End Date:
2026-08-30: Service Window:
2026-05-25 to 2026-08-30 (?) The range of service dates covered by the feed, based on trips with an associated service_id in calendar.txt and/or calendar_dates.txt

Files included

agency.txt
calendar.txt
calendar_dates.txt
feed_info.txt
frequencies.txt
routes.txt
shapes.txt
stop_times.txt
stops.txt
trips.txt

Counts

Agencies: 1
Blocks: 0
Routes: 59
Shapes: 141
Stops: 801
Trips: 2877

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

ShapesFeed InformationRoute ColorsHeadsignsStops Wheelchair AccessibilityLocation TypesContinuous Stops

Specification Compliance report

87896 notices reported (0 errors, 87893 warnings, 3 infos)

Notice Code Severity Total

equal_shape_distance_diff_coordinates_distance_below_threshold WARNING 8

equal_shape_distance_diff_coordinates_distance_below_threshold

Two consecutive points have equal shape_dist_traveled and different lat/lon coordinates in shapes.txt and the distance between the two points is greater than 0 but less than 1.11m.

When sorted by shape.shape_pt_sequence, the values for shape_dist_traveled must increase along a shape. Two consecutive points with equal values for shape_dist_traveled and small difference of coordinates (greater than 0 but less than 1.11 m distance) result in a warning.

You can see more about this notice here.

shapeId (?) The id of the faulty shape.	csvRowNumber (?) The row number from `shapes.txt`.	shapeDistTraveled (?) The faulty record's `shape_dist_traveled` value.	shapePtSequence (?) The faulty record's `shapes.shape_pt_sequence`.	prevCsvRowNumber (?) The row number from `shapes.txt` of the previous shape point.	prevShapeDistTraveled (?) The previous shape point's `shape_dist_traveled` value.	prevShapePtSequence (?) The previous record's `shapes.shape_pt_sequence`.	actualDistanceBetweenShapePoints (?) Actual distance traveled along the shape from the first shape point to the previous shape point.
"zenbus:Route:4793203822690304:LOC"	11268	11239.0	279	11267	11239.0	278	0.7133376195833462
"zenbus:Route:4793203822690304:LOC"	11342	13479.0	353	11341	13479.0	352	0.43474595333173605
"zenbus:Route:5471887971844096:LOC"	10784	11239.0	279	10783	11239.0	278	0.7133376195833462
"zenbus:Route:6576688455483392:LOC"	43919	8432.0	300	43918	8432.0	299	0.7092481749003549
"zenbus:Route:6029885255450624:LOC"	33446	2317.0	90	33445	2317.0	89	0.2803571757715862
"zenbus:Route:6029885255450624:LOC"	33456	2887.0	100	33455	2887.0	99	0.6688682896445282
"zenbus:Route:6029885255450624:LOC"	33665	9335.0	309	33664	9335.0	308	0.3502377140317541
"zenbus:Route:4523129360613376:LOC"	11737	11239.0	279	11736	11239.0	278	0.7133376195833462

expired_calendar WARNING 2

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	"cal1-tue-wed"
15	"cal14-mon"

missing_bike_allowance WARNING 12

missing_bike_allowance

Ferry trips should include bike allowance information.

All ferry trips should have a valid value in the bikes_allowed field in trips.txt.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	routeId (?) The faulty record's route id.	tripId (?) The faulty record's trip id.
2841	"zenbus:Line:570820023:LOC"	"4816598601826304:0"
2842	"zenbus:Line:570820023:LOC"	"4816598601826304:1"
2843	"zenbus:Line:570820023:LOC"	"4816598601826304:2"
2844	"zenbus:Line:570820023:LOC"	"4859262860787712:0"
2845	"zenbus:Line:570820023:LOC"	"4859262860787712:1"
2846	"zenbus:Line:570820023:LOC"	"4859262860787712:2"
2847	"zenbus:Line:570820023:LOC"	"4801767677100032:0"
2848	"zenbus:Line:570820023:LOC"	"4801767677100032:1"
2849	"zenbus:Line:570820023:LOC"	"4801767677100032:2"
2850	"zenbus:Line:570820023:LOC"	"5450860917161984:0"
2851	"zenbus:Line:570820023:LOC"	"5450860917161984:1"
2852	"zenbus:Line:570820023:LOC"	"5450860917161984:2"

missing_feed_contact_email_and_url WARNING 1

missing_feed_contact_email_and_url

Best Practices for feed_info.txt suggest providing at least one of feed_contact_email and feed_contact_url.

You can see more about this notice here.

csvRowNumber (?) The row number of the validated record.
2

missing_recommended_field WARNING 59

missing_recommended_field

A recommended field is missing.

The given field has no value in some input row, even though values are recommended.

You can see more about this notice here.

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

filename (?) The name of the faulty file.	csvRowNumber (?) The row of the faulty record.	fieldName (?) The name of the missing field.
"routes.txt"	2	"agency_id"
"routes.txt"	3	"agency_id"
"routes.txt"	4	"agency_id"
"routes.txt"	5	"agency_id"
"routes.txt"	6	"agency_id"
"routes.txt"	7	"agency_id"
"routes.txt"	8	"agency_id"
"routes.txt"	9	"agency_id"
"routes.txt"	10	"agency_id"
"routes.txt"	11	"agency_id"
"routes.txt"	12	"agency_id"
"routes.txt"	13	"agency_id"
"routes.txt"	14	"agency_id"
"routes.txt"	15	"agency_id"
"routes.txt"	16	"agency_id"
"routes.txt"	17	"agency_id"
"routes.txt"	18	"agency_id"
"routes.txt"	19	"agency_id"
"routes.txt"	20	"agency_id"
"routes.txt"	21	"agency_id"
"routes.txt"	22	"agency_id"
"routes.txt"	23	"agency_id"
"routes.txt"	24	"agency_id"
"routes.txt"	25	"agency_id"
"routes.txt"	26	"agency_id"
"routes.txt"	27	"agency_id"
"routes.txt"	28	"agency_id"
"routes.txt"	29	"agency_id"
"routes.txt"	30	"agency_id"
"routes.txt"	31	"agency_id"
"routes.txt"	32	"agency_id"
"routes.txt"	33	"agency_id"
"routes.txt"	34	"agency_id"
"routes.txt"	35	"agency_id"
"routes.txt"	36	"agency_id"
"routes.txt"	37	"agency_id"
"routes.txt"	38	"agency_id"
"routes.txt"	39	"agency_id"
"routes.txt"	40	"agency_id"
"routes.txt"	41	"agency_id"
"routes.txt"	42	"agency_id"
"routes.txt"	43	"agency_id"
"routes.txt"	44	"agency_id"
"routes.txt"	45	"agency_id"
"routes.txt"	46	"agency_id"
"routes.txt"	47	"agency_id"
"routes.txt"	48	"agency_id"
"routes.txt"	49	"agency_id"
"routes.txt"	50	"agency_id"
"routes.txt"	51	"agency_id"

missing_timepoint_value WARNING 85034

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 85034 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	"5443419148124160:0"	0
3	"5443419148124160:0"	1
4	"5443419148124160:0"	2
5	"5443419148124160:0"	3
6	"5443419148124160:0"	4
7	"5443419148124160:0"	5
8	"5443419148124160:0"	6
9	"5443419148124160:0"	7
10	"5443419148124160:0"	8
11	"5443419148124160:0"	9
12	"5443419148124160:0"	10
13	"5443419148124160:0"	11
14	"5443419148124160:0"	12
15	"5443419148124160:0"	13
16	"5443419148124160:0"	14
17	"5443419148124160:0"	15
18	"5443419148124160:0"	41
19	"5443419148124160:0"	42
20	"6573515372232704:0"	0
21	"6573515372232704:0"	1
22	"6573515372232704:0"	2
23	"6573515372232704:0"	3
24	"6573515372232704:0"	4
25	"6573515372232704:0"	5
26	"6573515372232704:0"	6
27	"6573515372232704:0"	7
28	"6573515372232704:0"	8
29	"6573515372232704:0"	9
30	"6573515372232704:0"	10
31	"6573515372232704:0"	11
32	"6573515372232704:0"	14
33	"6573515372232704:0"	15
34	"6573515372232704:0"	16
35	"6573515372232704:0"	17
36	"6573515372232704:1"	0
37	"6573515372232704:1"	1
38	"6573515372232704:1"	2
39	"6573515372232704:1"	3
40	"6573515372232704:1"	4
41	"6573515372232704:1"	5
42	"6573515372232704:1"	6
43	"6573515372232704:1"	7
44	"6573515372232704:1"	8
45	"6573515372232704:1"	9
46	"6573515372232704:1"	10
47	"6573515372232704:1"	11
48	"6573515372232704:1"	14
49	"6573515372232704:1"	15
50	"6573515372232704:1"	16
51	"6573515372232704:1"	17

mixed_case_recommended_field WARNING 2733

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 2733 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.
"agency.txt"	"agency_name"	"sitac"	2
"stops.txt"	"stop_name"	"PLACE DE CANTORBERY"	2
"stops.txt"	"stop_name"	"CITE EUROPE"	3
"stops.txt"	"stop_name"	"OUTLET STORE"	4
"stops.txt"	"stop_name"	"MEDECINE DU TRAVAIL"	5
"stops.txt"	"stop_name"	"CHARLES DE GAULLE"	8
"stops.txt"	"stop_name"	"LES COTTAGES"	9
"stops.txt"	"stop_name"	"CENTRE CIAL LA FRANCAISE"	10
"stops.txt"	"stop_name"	"PORTE DE PARIS"	11
"stops.txt"	"stop_name"	"LE CHANNEL"	14
"stops.txt"	"stop_name"	"11 NOVEMBRE"	16
"stops.txt"	"stop_name"	"GARE SNCF"	19
"stops.txt"	"stop_name"	"4 BOULEVARDS"	20
"stops.txt"	"stop_name"	"LA FONTAINE"	26
"stops.txt"	"stop_name"	"JULIEN DENIS"	27
"stops.txt"	"stop_name"	"MARCEL DORET"	34
"stops.txt"	"stop_name"	"HOTEL DES ENTREPRISES"	35
"stops.txt"	"stop_name"	"LES DRYADES"	36
"stops.txt"	"stop_name"	"MAIRIE DE MARCK"	43
"stops.txt"	"stop_name"	"MARCK AERODROME"	44
"stops.txt"	"stop_name"	"STADE DU SOUVENIR"	46
"stops.txt"	"stop_name"	"SAINT PIERRE HALTE"	54
"stops.txt"	"stop_name"	"CHEMIN CASTRES"	56
"stops.txt"	"stop_name"	"CLINIQUES DU VIRVAL"	58
"stops.txt"	"stop_name"	"LA ROSELIERE"	60
"stops.txt"	"stop_name"	"EUSTACHE SAINT PIERRE"	62
"stops.txt"	"stop_name"	"LES SAULES"	63
"stops.txt"	"stop_name"	"EGLISE DE COULOGNE"	64
"stops.txt"	"stop_name"	"SAINTE ANNE"	65
"stops.txt"	"stop_name"	"FELIX THORON"	66
"stops.txt"	"stop_name"	"POSTE DE COULOGNE"	67
"stops.txt"	"stop_name"	"PONT DE COULOGNE"	69
"stops.txt"	"stop_name"	"CAFE DES SPORTS"	71
"stops.txt"	"stop_name"	"STADE DU SOUVENIR"	77
"stops.txt"	"stop_name"	"PONT A 3 PLANCHES"	80
"stops.txt"	"stop_name"	"MAIRIE ANNEXE"	81
"stops.txt"	"stop_name"	"DIGUE GASTON BERTHE"	89
"stops.txt"	"stop_name"	"MILIEU DE DIGUE"	90
"stops.txt"	"stop_name"	"CAMPING DE CALAIS"	91
"stops.txt"	"stop_name"	"EGLISE DE BLERIOT"	92
"stops.txt"	"stop_name"	"CHATEAU D'EAU"	95
"stops.txt"	"stop_name"	"BASE DE VOILE"	97
"stops.txt"	"stop_name"	"LES SALINES"	98
"stops.txt"	"stop_name"	"DOS D'ANE"	99
"stops.txt"	"stop_name"	"STADE DE SANGATTE"	100
"stops.txt"	"stop_name"	"LE RELAIS"	101
"stops.txt"	"stop_name"	"MAIRIE SANGATTE"	102
"stops.txt"	"stop_name"	"MAISON PETITE ENFANCE"	103
"stops.txt"	"stop_name"	"CAP BLANC NEZ"	106
"stops.txt"	"stop_name"	"HAUTE-ESCALLES"	108

same_name_and_description_for_route WARNING 44

same_name_and_description_for_route

Same name and description for route.

The GTFS spec defines routes.txt route_desc as:

Description of a route that provides useful, quality information. Do not simply duplicate the name of the route.

See the GTFS and GTFS Best Practices links below for more examples of how to populate the route_short_name, route_long_name, and route_desc fields.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record.	routeId (?) The id of the faulty record.	routeDesc (?) The `routes.routes_desc` of the faulty record.	specifiedField (?) Either `route_short_name` or `route_long_name`.
5	"zenbus:Line:716930001:LOC"	"TS19"	"route_short_name"
9	"zenbus:Line:720820003:LOC"	"TS37"	"route_short_name"
13	"zenbus:Line:4904135695532032:LOC"	"TS30"	"route_short_name"
15	"zenbus:Line:700700001:LOC"	"TS38"	"route_short_name"
16	"zenbus:Line:722830001:LOC"	"TS24"	"route_short_name"
17	"zenbus:Line:706040001:LOC"	"TS31"	"route_short_name"
18	"zenbus:Line:4860024502353920:LOC"	"TS6"	"route_short_name"
19	"zenbus:Line:684470001:LOC"	"TS17"	"route_short_name"
20	"zenbus:Line:4832014604697600:LOC"	"TS27"	"route_short_name"
21	"zenbus:Line:698230001:LOC"	"TS35"	"route_short_name"
22	"zenbus:Line:716920001:LOC"	"TS22"	"route_short_name"
23	"zenbus:Line:4810787299262464:LOC"	"TS29"	"route_short_name"
24	"zenbus:Line:716850003:LOC"	"TS16"	"route_short_name"
25	"zenbus:Line:700690001:LOC"	"TS9"	"route_short_name"
26	"zenbus:Line:722820001:LOC"	"TS13"	"route_short_name"
28	"zenbus:Line:4862956455067648:LOC"	"TS5"	"route_short_name"
29	"zenbus:Line:706050001:LOC"	"TS18"	"route_short_name"
30	"zenbus:Line:716910001:LOC"	"TS40"	"route_short_name"
31	"zenbus:Line:702180001:LOC"	"TS12"	"route_short_name"
33	"zenbus:Line:720860001:LOC"	"TS42"	"route_short_name"
34	"zenbus:Line:698220001:LOC"	"TS1"	"route_short_name"
35	"zenbus:Line:680180001:LOC"	"TS25"	"route_short_name"
37	"zenbus:Line:718830001:LOC"	"TS32"	"route_short_name"
38	"zenbus:Line:676280002:LOC"	"TS8"	"route_short_name"
39	"zenbus:Line:684480001:LOC"	"TS11"	"route_short_name"
40	"zenbus:Line:715040002:LOC"	"TS2"	"route_short_name"
41	"zenbus:Line:722860001:LOC"	"TS34"	"route_short_name"
44	"zenbus:Line:722840001:LOC"	"TS15"	"route_short_name"
45	"zenbus:Line:711080002:LOC"	"TS7"	"route_short_name"
46	"zenbus:Line:692350003:LOC"	"TS14"	"route_short_name"
47	"zenbus:Line:709480008:LOC"	"TS21"	"route_short_name"
48	"zenbus:Line:678580001:LOC"	"TS44"	"route_short_name"
49	"zenbus:Line:698210001:LOC"	"TS4"	"route_short_name"
50	"zenbus:Line:684460002:LOC"	"TS36"	"route_short_name"
51	"zenbus:Line:4815637323972608:LOC"	"TS3"	"route_short_name"
52	"zenbus:Line:703770003:LOC"	"TS20"	"route_short_name"
53	"zenbus:Line:686640002:LOC"	"TS28"	"route_short_name"
54	"zenbus:Line:713110001:LOC"	"TS10"	"route_short_name"
55	"zenbus:Line:722870001:LOC"	"TS39"	"route_short_name"
56	"zenbus:Line:722850001:LOC"	"TS41"	"route_short_name"
57	"zenbus:Line:720870001:LOC"	"TS33"	"route_short_name"
58	"zenbus:Line:715070001:LOC"	"TS23"	"route_short_name"
59	"zenbus:Line:684490001:LOC"	"TS26"	"route_short_name"
60	"zenbus:Line:718820001:LOC"	"TS43"	"route_short_name"

trip_headsign_matches_intermediate_stop INFO 1

trip_headsign_matches_intermediate_stop

Trip headsign matches the name of an intermediate stop, not the last stop.

The trip_headsign matches the stop_name of a stop that is not the last stop of the trip. This may confuse passengers boarding after that stop, since the headsign suggests the vehicle is heading to a stop it has already passed.

You can see more about this notice here.

csvRowNumber (?) The row number of the faulty record in `trips.txt`.	tripId (?) The id of the trip with the problematic headsign.	tripHeadsign (?) The headsign value that matches an intermediate stop name.	stopId1 (?) The id of the intermediate stop whose name matches the headsign.	stopSequence (?) The stop_sequence value of the intermediate stop that matches the headsign.	stopId2 (?) The id of the actual last stop of the trip.
2006	"4816316109160448:0"	"MATISSE"	"zenbus:StopPoint:SP:5081148289974272:LOC"	20	"zenbus:StopPoint:SP:5099057095639040:LOC"

unknown_column INFO 2

unknown_column

A column name is unknown.

You can see more about this notice here.

filename (?) The name of the faulty file.	fieldName (?) The name of the unknown column.	index (?) The index of the faulty column.
"trips.txt"	"zenbus_mission_id"	11
"trips.txt"	"trip_headsign_code"	12