WEBVTT

1
00:00:00.400 --> 00:00:02.470
In a mixed traffic file, the meaning

2
00:00:02.480 --> 00:00:04.470
of a record depends on its surrounding

3
00:00:04.480 --> 00:00:07.670
definitions. Reading each line as an unrelated

4
00:00:07.680 --> 00:00:10.550
spreadsheet row loses relationships that the system

5
00:00:10.560 --> 00:00:13.270
can check. A header block begins with

6
00:00:13.280 --> 00:00:15.910
H zero and closes with H nine.

7
00:00:16.320 --> 00:00:19.350
The mixed-file checks detect orphaned, nested and

8
00:00:19.440 --> 00:00:22.710
unclosed boundaries, and look for compulsory definitions

9
00:00:22.720 --> 00:00:26.630
in completed blocks. Lane consistency compares the

10
00:00:26.640 --> 00:00:28.630
totals in L zero with the L

11
00:00:28.720 --> 00:00:31.990
one definitions. Two declared lanes but one

12
00:00:32.000 --> 00:00:34.870
lane definition is a relationship problem, even

13
00:00:34.880 --> 00:00:38.470
if both records contain valid numbers. Variable

14
00:00:38.480 --> 00:00:40.870
vehicle records use their declared counts and

15
00:00:40.960 --> 00:00:44.110
schema rules to determine expected field lengths.

16
00:00:44.320 --> 00:00:46.150
Dropping a repeated value can make the

17
00:00:46.160 --> 00:00:49.070
physical record disagree with its own count.

18
00:00:49.360 --> 00:00:52.070
These contextual checks depend on the mixed-file

19
00:00:52.080 --> 00:00:55.510
route. A standalone record template cannot establish

20
00:00:55.520 --> 00:00:57.830
all the relationships available in a complete

21
00:00:57.840 --> 00:01:01.110
file with active headers. Preserve the original

22
00:01:01.120 --> 00:01:03.590
record order and review the reported source

23
00:01:03.600 --> 00:01:06.550
line. Correct the header, lane definition or

24
00:01:06.560 --> 00:01:09.830
record length at source, then rerun. Keep

25
00:01:09.840 --> 00:01:12.640
structural validity distinct from the accuracy of

26
00:01:12.640 --> 00:01:13.910
the measured traffic.