Home
France Feeds
pdc
Source Data Validation Report

pdc — Source Data Validation Report

This report was generated by the Canonical GTFS Schedule validator, version 7.1.0 at 2026-04-23T17:34:05Z,
for the dataset file:///shared/pdc_ecde6112.zip. No country code was provided.

Use this report alongside our documentation.

Summary

Agencies included

CAR_HDF_62_COM
- website: https://transports.hautsdefrance.fr/
- phone number:
- email: Not provided

Feed Info

Publisher Name:
N/A: Publisher URL:
N/A: Feed Email:
N/A: Feed Language:
N/A: Service Window:
2026-05-03 to 2027-04-25 (?) 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
routes.txt
stop_times.txt
stops.txt
trips.txt
trips_extensions.txt

Counts

Agencies: 1
Blocks: 0
Routes: 37
Shapes: 0
Stops: 3594
Trips: 1160

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

Headsigns Location Types

Specification Compliance report

20216 notices reported (63 errors, 20152 warnings, 1 infos)

Notice Code Severity Total

decreasing_or_equal_stop_time_distance ERROR 63

decreasing_or_equal_stop_time_distance

Decreasing or equal shape_dist_traveled in stop_times.txt.

When sorted by stop_times.stop_sequence, two consecutive entries in stop_times.txt should have increasing distance, based on the field shape_dist_traveled. If the values are equal, this is considered as an error.

You can see more about this notice here.

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

tripId (?) The id of the faulty trip.	stopId (?) The id of the faulty stop.	csvRowNumber (?) The row number from `stop_times.txt`.	shapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the faulty record.	stopSequence (?) The faulty record's `stop_times.stop_sequence`.	prevCsvRowNumber (?) The row number from `stop_times.txt` of the previous stop time.	prevShapeDistTraveled (?) Actual distance traveled along the shape from the first shape point to the previous stop time.	prevStopSequence (?) The previous record's `stop_times.stop_sequence`.
"Lr422017\|20250901\|1"	"62:25696"	11275	22.3	21	11274	22.3	20
"Lr422017\|20250901\|1"	"62:25699"	11276	22.3	22	11275	22.3	21
"Lr422017\|20250901\|1"	"62:25701"	11277	22.3	23	11276	22.3	22
"Lr413004\|20230901\|1"	"62:33025"	6393	14.08	24	6392	14.08	23
"Lr413004\|20230901\|1"	"62:33024"	6394	14.08	25	6393	14.08	24
"Lr413004\|20230901\|1"	"62:27267"	6395	14.08	26	6394	14.08	25
"Lr406006\|20250505\|1"	"62:29355"	3026	45.71	20	3025	45.71	19
"Lr406006\|20250505\|1"	"62:33487"	3027	45.71	21	3026	45.71	20
"Lr426023\|20260105\|1"	"62:29280"	14194	1.02	3	14193	1.02	2
"Lr426023\|20260105\|1"	"62:30023"	14195	1.02	4	14194	1.02	3
"Lr422029\|20250901\|1"	"62:34213"	11531	19.35	20	11530	19.35	19
"Lr422029\|20250901\|1"	"62:25696"	11532	19.35	21	11531	19.35	20
"Lr422029\|20250901\|1"	"62:25699"	11533	19.35	22	11532	19.35	21
"Lr422029\|20250901\|1"	"62:25701"	11534	19.35	23	11533	19.35	22
"Lr422029\|20250901\|2"	"62:34213"	11554	19.35	20	11553	19.35	19
"Lr422029\|20250901\|2"	"62:25696"	11555	19.35	21	11554	19.35	20
"Lr422029\|20250901\|2"	"62:25699"	11556	19.35	22	11555	19.35	21
"Lr422029\|20250901\|2"	"62:25701"	11557	19.35	23	11556	19.35	22
"Lr422031\|20250901\|1"	"62:25696"	11581	22.82	22	11580	22.82	21
"Lr422031\|20250901\|1"	"62:25699"	11582	22.82	23	11581	22.82	22
"Lr422031\|20250901\|1"	"62:25701"	11583	22.82	24	11582	22.82	23
"Lr422031\|20250901\|2"	"62:25696"	11605	22.82	22	11604	22.82	21
"Lr422031\|20250901\|2"	"62:25699"	11606	22.82	23	11605	22.82	22
"Lr422031\|20250901\|2"	"62:25701"	11607	22.82	24	11606	22.82	23
"Lr422018\|20250901\|1"	"62:34213"	11280	1.17	3	11279	1.17	2
"Lr424008\|20231218\|1"	"62:26200"	13014	22.1	5	13013	22.1	4
"Lr424008\|20231218\|1"	"62:30084"	13015	22.1	6	13014	22.1	5
"Lr424008\|20231218\|1"	"62:26201"	13016	22.1	7	13015	22.1	6
"Lr424008\|20231218\|1"	"62:27658"	13017	22.1	8	13016	22.1	7
"Lr424008\|20231218\|1"	"62:29079"	13018	22.1	9	13017	22.1	8
"Lr424008\|20231218\|1"	"62:26206"	13019	22.1	10	13018	22.1	9
"Lr424008\|20231218\|1"	"62:29076"	13020	22.1	11	13019	22.1	10
"Lr424008\|20231218\|1"	"62:29074"	13021	22.1	12	13020	22.1	11
"Lr424008\|20231218\|1"	"62:28304"	13022	22.1	13	13021	22.1	12
"Lr424008\|20231218\|1"	"62:29082"	13023	22.1	14	13022	22.1	13
"Lr424008\|20231218\|1"	"62:29083"	13024	22.1	15	13023	22.1	14
"Lr424008\|20231218\|1"	"62:29085"	13025	22.1	16	13024	22.1	15
"Lr424008\|20231218\|1"	"62:29086"	13026	22.1	17	13025	22.1	16
"Lr424008\|20231218\|2"	"62:26200"	13031	22.1	5	13030	22.1	4
"Lr424008\|20231218\|2"	"62:30084"	13032	22.1	6	13031	22.1	5
"Lr424008\|20231218\|2"	"62:26201"	13033	22.1	7	13032	22.1	6
"Lr424008\|20231218\|2"	"62:27658"	13034	22.1	8	13033	22.1	7
"Lr424008\|20231218\|2"	"62:29079"	13035	22.1	9	13034	22.1	8
"Lr424008\|20231218\|2"	"62:26206"	13036	22.1	10	13035	22.1	9
"Lr424008\|20231218\|2"	"62:29076"	13037	22.1	11	13036	22.1	10
"Lr424008\|20231218\|2"	"62:29074"	13038	22.1	12	13037	22.1	11
"Lr424008\|20231218\|2"	"62:28304"	13039	22.1	13	13038	22.1	12
"Lr424008\|20231218\|2"	"62:29082"	13040	22.1	14	13039	22.1	13
"Lr424008\|20231218\|2"	"62:29083"	13041	22.1	15	13040	22.1	14
"Lr424008\|20231218\|2"	"62:29085"	13042	22.1	16	13041	22.1	15

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 20146

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

mixed_case_recommended_field WARNING 4

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"	"CAR_HDF_62_COM"	2
"stops.txt"	"stop_name"	"BAPAUME - RRT 62"	193
"stops.txt"	"stop_name"	"SAINT-LAURENT-BLANGY - MAPAD"	909
"stops.txt"	"stop_name"	"CALAIS - UFR"	1202

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.
"20260423"	"20260427"	"20260704"

unknown_file INFO 1

unknown_file

A file is unknown.

You can see more about this notice here.

filename (?) The name of the unknown file.
"trips_extensions.txt"