WEBVTT

1
00:00:00.400 --> 00:00:02.710
A block-pavement record carries more than a

2
00:00:02.720 --> 00:00:05.670
collection of ratings. It ties block type,

3
00:00:05.680 --> 00:00:08.630
laying pattern and observations to a particular

4
00:00:08.640 --> 00:00:11.430
road interval and measurement date. The current

5
00:00:11.440 --> 00:00:14.390
template declares specific codes for block type,

6
00:00:14.400 --> 00:00:17.830
laying pattern and chamfers. For example, H

7
00:00:17.920 --> 00:00:20.950
B is a permitted laying-pattern code. Free

8
00:00:20.960 --> 00:00:23.030
text in that coded field is not

9
00:00:23.080 --> 00:00:26.390
equivalent. The segment-length check uses a zero

10
00:00:26.480 --> 00:00:29.190
point two kilometre baseline with a fifty-percent

11
00:00:29.280 --> 00:00:32.230
band. A zero point four kilometre example

12
00:00:32.240 --> 00:00:35.190
is outside the band and needs review.

13
00:00:35.200 --> 00:00:37.720
A disallowed code is a schema error;

14
00:00:37.720 --> 00:00:40.680
the assessment-length issue is a warning. Read

15
00:00:40.680 --> 00:00:43.320
the finding category and affected row instead

16
00:00:43.320 --> 00:00:45.510
of treating every highlighted value as the

17
00:00:45.520 --> 00:00:49.430
same problem. Where supplied, condition indices must

18
00:00:49.440 --> 00:00:52.150
remain within zero to one hundred. This

19
00:00:52.160 --> 00:00:54.630
check does not recalculate an index or

20
00:00:54.640 --> 00:00:57.190
prove that the block-pavement rating matches field

21
00:00:57.200 --> 00:01:00.390
conditions. Use the original assessment to resolve

22
00:01:00.400 --> 00:01:03.030
the code or interval. Preserve the approved

23
00:01:03.040 --> 00:01:05.670
version and evidence, then rerun the applicable

24
00:01:05.760 --> 00:01:09.110
checks. A clean file supports review; it

25
00:01:09.120 --> 00:01:11.030
does not replace the assessor.