horaires-des-traversees-brittany-ferries — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-03-23T21:43:47Z,
for the dataset file:///shared/horaires-des-traversees-brittany-ferries_a334debe.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_dates.txt
  3. routes.txt
  4. stop_times.txt
  5. stops.txt
  6. trips.txt

Counts


  • Agencies: 1
  • Blocks: 0
  • Routes: 26
  • Shapes: 0
  • Stops: 12
  • Trips: 5314

Specification Compliance report

96 notices reported (0 errors, 95 warnings, 1 infos)

Notice Code Severity Total
fast_travel_between_consecutive_stops WARNING 7

fast_travel_between_consecutive_stops

A transit vehicle moves too fast between two consecutive stops.

The speed threshold depends on route type:

Route type Description Threshold, km/h
0 Light rail 100
1 Subway 150
2 Rail 500
3 Bus 150
4 Ferry 80
5 Cable tram 30
6 Aerial lift 50
7 Funicular 50
11 Trolleybus 150
12 Monorail 150
- Unknown 200

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the problematic trip. tripId (?) `trip_id` of the problematic trip. routeId (?) `route_id` of the problematic trip. speedKph (?) Travel speed (km/h). distanceKm (?) Distance between stops (km). csvRowNumber1 (?) The row number of the first stop time. stopSequence1 (?) `stop_sequence` of the first stop. stopId1 (?) `stop_id` of the first stop. stopName1 (?) `stop_name` of the first stop. departureTime1 (?) `departure_time` of the first stop. csvRowNumber2 (?) The row number of the second stop time. stopSequence2 (?) `stop_sequence` of the second stop. stopId2 (?) `stop_id` of the second stop. stopName2 (?) `stop_name` of the second stop. arrivalTime2 (?) `arrival_time` of the second stop.
4757 "422682" "PB" 101.93730752860417 842.6817422364611 9337 1 "GB PME" "Portsmouth" "23:45:00" 9557 2 "ES BIO" "Bilbao" "32:00:00"
4664 "422680" "PB" 101.93730752860417 842.6817422364611 9244 1 "GB PME" "Portsmouth" "23:45:00" 9464 2 "ES BIO" "Bilbao" "32:00:00"
4717 "422681" "PB" 101.93730752860417 842.6817422364611 9297 1 "GB PME" "Portsmouth" "23:45:00" 9517 2 "ES BIO" "Bilbao" "32:00:00"
4671 "422679" "PB" 101.93730752860417 842.6817422364611 9251 1 "GB PME" "Portsmouth" "23:45:00" 9471 2 "ES BIO" "Bilbao" "32:00:00"
4421 "422676" "PB" 101.93730752860417 842.6817422364611 8759 1 "GB PME" "Portsmouth" "23:45:00" 8981 2 "ES BIO" "Bilbao" "32:00:00"
4487 "422677" "PB" 101.93730752860417 842.6817422364611 8825 1 "GB PME" "Portsmouth" "23:45:00" 9047 2 "ES BIO" "Bilbao" "32:00:00"
4541 "422678" "PB" 101.93730752860417 842.6817422364611 8879 1 "GB PME" "Portsmouth" "23:45:00" 9101 2 "ES BIO" "Bilbao" "32:00:00"
fast_travel_between_far_stops WARNING 7

fast_travel_between_far_stops

A transit vehicle moves too fast between two far stops.

Two stops are considered "far" if they are more than 10 km apart. This normally indicates a more serious problem than too fast travel between consecutive stops.

The speed threshold depends on route type and are the same as fast_travel_between_consecutive_stops.

You can see more about this notice here.

tripCsvRowNumber (?) The row number of the problematic trip. tripId (?) `trip_id` of the problematic trip. routeId (?) `route_id` of the problematic trip. speedKph (?) Travel speed (km/h). distanceKm (?) Distance between stops (km). csvRowNumber1 (?) The row number of the first stop time. stopSequence1 (?) `stop_sequence` of the first stop. stopId1 (?) `stop_id` of the first stop. stopName1 (?) `stop_name` of the first stop. departureTime1 (?) `departure_time` of the first stop. csvRowNumber2 (?) The row number of the second stop time. stopSequence2 (?) `stop_sequence` of the second stop. stopId2 (?) `stop_id` of the second stop. stopName2 (?) `stop_name` of the second stop. arrivalTime2 (?) `arrival_time` of the second stop.
4757 "422682" "PB" 101.93730752860417 842.6817422364611 9337 1 "GB PME" "Portsmouth" "23:45:00" 9557 2 "ES BIO" "Bilbao" "32:00:00"
4664 "422680" "PB" 101.93730752860417 842.6817422364611 9244 1 "GB PME" "Portsmouth" "23:45:00" 9464 2 "ES BIO" "Bilbao" "32:00:00"
4717 "422681" "PB" 101.93730752860417 842.6817422364611 9297 1 "GB PME" "Portsmouth" "23:45:00" 9517 2 "ES BIO" "Bilbao" "32:00:00"
4671 "422679" "PB" 101.93730752860417 842.6817422364611 9251 1 "GB PME" "Portsmouth" "23:45:00" 9471 2 "ES BIO" "Bilbao" "32:00:00"
4421 "422676" "PB" 101.93730752860417 842.6817422364611 8759 1 "GB PME" "Portsmouth" "23:45:00" 8981 2 "ES BIO" "Bilbao" "32:00:00"
4487 "422677" "PB" 101.93730752860417 842.6817422364611 8825 1 "GB PME" "Portsmouth" "23:45:00" 9047 2 "ES BIO" "Bilbao" "32:00:00"
4541 "422678" "PB" 101.93730752860417 842.6817422364611 8879 1 "GB PME" "Portsmouth" "23:45:00" 9101 2 "ES BIO" "Bilbao" "32:00:00"
leading_or_trailing_whitespaces WARNING 1

leading_or_trailing_whitespaces

The value in CSV file has leading or trailing whitespaces.

This notice is emitted for values protected with double quotes since whitespaces for non-protected values are trimmed automatically by CSV parser.

The validator strips whitespaces from protected values. We do not see any use case when such a whitespace may be needed. On the other hand, some real-world feeds use trailing whitespaces for some values and omit them for the others. This is causing the largest problem when a primary key and a foreign key differ just by a whitespace: it is clear that they are intended to be the same, that is why we always strip whitespaces.

You can see more about this notice here.

filename (?) The name of the faulty file. csvRowNumber (?) The row of the faulty record. fieldName (?) Faulty record's field name. fieldValue (?) Faulty value.
"stops.txt" 7 "stop_desc" "Situé dans le Sud-Ouest de l'Angleterre, le port de Plymouth dessert bien le Sud de l'Angleterre et le Pays de Galles. On y accède facilement grâce au réseau routier anglais. Londres est à moins de 4 heures de voiture. "
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 52

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 52 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" "GB POO-FR CER" 2
"routes.txt" "route_long_name" "POOLE-CHERBOURG" 2
"routes.txt" "route_short_name" "FR OUI-GB PME" 3
"routes.txt" "route_long_name" "OUISTREHAM-PORTSMOUTH" 3
"routes.txt" "route_short_name" "GB PME-FR OUI" 4
"routes.txt" "route_long_name" "PORTSMOUTH-OUISTREHAM" 4
"routes.txt" "route_short_name" "FR CER-GB POO" 5
"routes.txt" "route_long_name" "CHERBOURG-POOLE" 5
"routes.txt" "route_short_name" "IE ROE-FR CER" 6
"routes.txt" "route_long_name" "ROSSLARE-CHERBOURG" 6
"routes.txt" "route_short_name" "GB PME-FR SML" 7
"routes.txt" "route_long_name" "PORTSMOUTH-ST MALO" 7
"routes.txt" "route_short_name" "ES BIO-IE ROE" 8
"routes.txt" "route_long_name" "BILBAO-ROSSLARE" 8
"routes.txt" "route_short_name" "FR CER-IE ROE" 9
"routes.txt" "route_long_name" "CHERBOURG-ROSSLARE" 9
"routes.txt" "route_short_name" "FR SML-GB PME" 10
"routes.txt" "route_long_name" "ST MALO-PORTSMOUTH" 10
"routes.txt" "route_short_name" "GB PME-ES SDR" 11
"routes.txt" "route_long_name" "PORTSMOUTH-SANTANDER" 11
"routes.txt" "route_short_name" "IE ROE-ES BIO" 12
"routes.txt" "route_long_name" "ROSSLARE-BILBAO" 12
"routes.txt" "route_short_name" "ES SDR-GB PME" 13
"routes.txt" "route_long_name" "SANTANDER-PORTSMOUTH" 13
"routes.txt" "route_short_name" "FR ROS-GB PLY" 14
"routes.txt" "route_long_name" "ROSCOFF-PLYMOUTH" 14
"routes.txt" "route_short_name" "GB PLY-FR ROS" 15
"routes.txt" "route_long_name" "PLYMOUTH-ROSCOFF" 15
"routes.txt" "route_short_name" "GB PME-ES BIO" 16
"routes.txt" "route_long_name" "PORTSMOUTH-BILBAO" 16
"routes.txt" "route_short_name" "GB PLY-FR SML" 17
"routes.txt" "route_long_name" "PLYMOUTH-ST MALO" 17
"routes.txt" "route_short_name" "FR SML-GB PLY" 18
"routes.txt" "route_long_name" "ST MALO-PLYMOUTH" 18
"routes.txt" "route_short_name" "GB PME-FR CER" 19
"routes.txt" "route_long_name" "PORTSMOUTH-CHERBOURG" 19
"routes.txt" "route_short_name" "FR CER-GB PME" 20
"routes.txt" "route_long_name" "CHERBOURG-PORTSMOUTH" 20
"routes.txt" "route_short_name" "ES BIO-GB PME" 21
"routes.txt" "route_long_name" "BILBAO-PORTSMOUTH" 21
"routes.txt" "route_short_name" "FR LEH-GB PME" 22
"routes.txt" "route_long_name" "LE HAVRE-PORTSMOUTH" 22
"routes.txt" "route_short_name" "ES SDR-GB PLY" 23
"routes.txt" "route_long_name" "SANTANDER-PLYMOUTH" 23
"routes.txt" "route_short_name" "FR ROS-IE ORK" 24
"routes.txt" "route_long_name" "ROSCOFF-CORK" 24
"routes.txt" "route_short_name" "GB PME-FR LEH" 25
"routes.txt" "route_long_name" "PORTSMOUTH-LE HAVRE" 25
"routes.txt" "route_short_name" "GB PLY-ES SDR" 26
"routes.txt" "route_long_name" "PLYMOUTH-SANTANDER" 26
route_short_name_too_long WARNING 26

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`.
"LH" 2 "GB POO-FR CER"
"NP" 3 "FR OUI-GB PME"
"PN" 4 "GB PME-FR OUI"
"HL" 5 "FR CER-GB POO"
"OH" 6 "IE ROE-FR CER"
"PM" 7 "GB PME-FR SML"
"BO" 8 "ES BIO-IE ROE"
"HO" 9 "FR CER-IE ROE"
"MP" 10 "FR SML-GB PME"
"PS" 11 "GB PME-ES SDR"
"OB" 12 "IE ROE-ES BIO"
"SP" 13 "ES SDR-GB PME"
"RY" 14 "FR ROS-GB PLY"
"YR" 15 "GB PLY-FR ROS"
"PB" 16 "GB PME-ES BIO"
"YM" 17 "GB PLY-FR SML"
"MY" 18 "FR SML-GB PLY"
"PH" 19 "GB PME-FR CER"
"HP" 20 "FR CER-GB PME"
"BP" 21 "ES BIO-GB PME"
"AP" 22 "FR LEH-GB PME"
"SY" 23 "ES SDR-GB PLY"
"RC" 24 "FR ROS-IE ORK"
"PA" 25 "GB PME-FR LEH"
"YS" 26 "GB PLY-ES SDR"
"CR" 27 "IE ORK-FR ROS"
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.
"20260323" "20260330" "20261101"
unknown_column INFO 1

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" "cars_allowed" 6