WEBVTT

1
00:00:00.400 --> 00:00:02.950
Traffic link data can look convincing while

2
00:00:02.960 --> 00:00:05.750
using the wrong template version. The older

3
00:00:05.840 --> 00:00:09.590
annual-average fields and the newer average-daily-traffic fields

4
00:00:09.760 --> 00:00:12.590
must not be treated as identical layouts.

5
00:00:12.800 --> 00:00:15.830
In the version-five description, minibus traffic is

6
00:00:16.040 --> 00:00:18.310
included in the light total. Adding a

7
00:00:18.320 --> 00:00:21.350
subclass again can misstate a total. This

8
00:00:21.360 --> 00:00:24.150
diagram explains the relationship; it is not

9
00:00:24.160 --> 00:00:27.030
claiming an automated sum check. The schema

10
00:00:27.040 --> 00:00:30.470
validator checks declared types and constraints. A

11
00:00:30.480 --> 00:00:33.270
fractional value in an integer traffic-count field

12
00:00:33.440 --> 00:00:35.750
is a concrete type problem, even when

13
00:00:35.760 --> 00:00:39.030
the road identifier is valid. Applicable cross-row

14
00:00:39.040 --> 00:00:41.590
checks examine the location key and kilometre

15
00:00:41.600 --> 00:00:44.710
range, including duplicates and reversed or equal

16
00:00:44.720 --> 00:00:47.830
intervals. Project references can add road and

17
00:00:47.840 --> 00:00:50.790
lane context where available. The audited rule

18
00:00:50.800 --> 00:00:53.990
pack does not establish a comprehensive traffic-total

19
00:00:54.000 --> 00:00:57.590
reconciliation. Do not advertise a class-sum check

20
00:00:57.680 --> 00:01:00.710
merely because the catalogue describes those classes.

21
00:01:00.880 --> 00:01:03.590
Select the matching version, preserve the original

22
00:01:03.600 --> 00:01:07.150
count evidence, and investigate each actual finding.

23
00:01:07.280 --> 00:01:10.950
Correct the export without double-counting subclasses, then

24
00:01:11.040 --> 00:01:13.590
rerun the checks supported for that file.