WEBVTT

1
00:00:00.400 --> 00:00:03.670
A concrete-pavement assessment connects a kilometre interval

2
00:00:03.680 --> 00:00:07.350
to surface type, observations and condition indices.

3
00:00:07.520 --> 00:00:09.750
If that interval is wrong, a correctly

4
00:00:09.760 --> 00:00:11.910
typed rating can still be attributed to

5
00:00:11.920 --> 00:00:15.030
the wrong section. The implemented concrete segment

6
00:00:15.040 --> 00:00:17.270
check uses a zero point two kilometre

7
00:00:17.280 --> 00:00:20.230
baseline and a fifty-percent band. In this

8
00:00:20.400 --> 00:00:23.270
example, zero point one five kilometres falls

9
00:00:23.280 --> 00:00:25.590
within the band. A zero point four

10
00:00:25.680 --> 00:00:28.150
kilometre segment is outside the zero point

11
00:00:28.160 --> 00:00:30.070
one to zero point three band and

12
00:00:30.080 --> 00:00:32.870
produces a warning. A reversed interval is

13
00:00:33.000 --> 00:00:35.110
handled separately; these are not the same

14
00:00:35.240 --> 00:00:38.390
issue. The concrete template also declares allowed

15
00:00:38.480 --> 00:00:41.600
surface-type codes. An unrecognised code is a

16
00:00:41.600 --> 00:00:44.630
schema finding. Keep the original schema version

17
00:00:44.640 --> 00:00:48.070
and field positions when correcting it. Condition-index

18
00:00:48.080 --> 00:00:50.550
fields outside zero to one hundred are

19
00:00:50.560 --> 00:00:53.190
errors where those fields are present. Field

20
00:00:53.200 --> 00:00:56.230
types, declared rating ranges and index bounds

21
00:00:56.240 --> 00:00:59.110
provide different pieces of evidence. Compare the

22
00:00:59.240 --> 00:01:01.430
finding with the actual assessed section and

23
00:01:01.520 --> 00:01:04.390
survey notes. The system does not infer

24
00:01:04.400 --> 00:01:07.350
concrete performance from a tidy file. Correct

25
00:01:07.360 --> 00:01:09.670
attribution or coding only when the evidence

26
00:01:09.840 --> 00:01:11.990
supports it, then rerun.