WEBVTT

1
00:00:00.000 --> 00:00:02.476
Harbour Roads Training is reviewing a fictional

2
00:00:02.567 --> 00:00:06.006
road-survey programme. This lesson brings its files,

3
00:00:06.257 --> 00:00:09.296
references, alignment findings and report into one

4
00:00:09.306 --> 00:00:12.904
project context. Start with New project. Give

5
00:00:12.904 --> 00:00:15.001
the programme a clear name, choose the

6
00:00:15.010 --> 00:00:17.703
applicable authority and add the survey period

7
00:00:17.712 --> 00:00:20.644
when needed. Our example is Training network

8
00:00:20.653 --> 00:00:23.360
review. A project can group files before

9
00:00:23.368 --> 00:00:26.405
references are available. That helps organise work,

10
00:00:26.413 --> 00:00:28.981
but missing references limit which alignment checks

11
00:00:28.989 --> 00:00:31.898
can run. Geometry supplies the road line.

12
00:00:32.157 --> 00:00:35.510
Network definitions supply road identifiers and kilometre

13
00:00:35.522 --> 00:00:38.875
ranges. Classification and lane files provide their

14
00:00:38.887 --> 00:00:42.186
own supporting context. Upload the reference files

15
00:00:42.186 --> 00:00:45.107
and inspect their registration results. A usable

16
00:00:45.119 --> 00:00:47.337
reference can still have findings that need

17
00:00:47.556 --> 00:00:50.249
attention. Review the draft reference set before

18
00:00:50.532 --> 00:00:53.074
activation. The active version remains in use

19
00:00:53.083 --> 00:00:56.135
until deliberately replaced, so record which version

20
00:00:56.143 --> 00:00:58.391
supports the review. Add a survey using

21
00:00:58.394 --> 00:01:00.954
its matching template. File checks assess the

22
00:01:01.067 --> 00:01:04.103
export itself; project alignment assesses agreement with

23
00:01:04.107 --> 00:01:07.174
the available project references. A training survey

24
00:01:07.187 --> 00:01:09.914
uses road DEMO 02, but the reference

25
00:01:10.093 --> 00:01:13.484
contains DEMO 01. Investigate the identifier and

26
00:01:13.580 --> 00:01:16.737
source network before interpreting the measurements. The

27
00:01:16.757 --> 00:01:19.849
illustrative reference ends at kilometre ten, while

28
00:01:19.849 --> 00:01:22.026
a survey section ends at ten point

29
00:01:22.045 --> 00:01:24.984
five. Check the intended road and range

30
00:01:25.093 --> 00:01:28.347
rather than trimming the value blindly. Direction

31
00:01:28.367 --> 00:01:31.327
follows ordered survey positions along the reference

32
00:01:31.347 --> 00:01:34.217
road. If usable geometry or positions are

33
00:01:34.237 --> 00:01:37.377
missing, the check may not run. Skipped

34
00:01:37.668 --> 00:01:40.763
never means passed. Coverage shows where records

35
00:01:40.770 --> 00:01:43.521
exist, not whether they are correct. Project

36
00:01:43.528 --> 00:01:46.509
settings distinguish advisory alignment from findings that

37
00:01:46.516 --> 00:01:49.490
can gate sign-off. The project report identifies

38
00:01:49.497 --> 00:01:52.239
what was checked, not checked and excluded.

39
00:01:52.362 --> 00:01:54.910
Read those boundaries before using totals or

40
00:01:54.995 --> 00:01:57.718
presenting the programme as complete. Reference files

41
00:01:57.718 --> 00:02:00.848
and alignment rechecks are free. Survey validation

42
00:02:00.855 --> 00:02:03.295
follows its credit workflow, and reference files

43
00:02:03.295 --> 00:02:07.303
themselves are not certified. Pause here. Identify

44
00:02:07.322 --> 00:02:10.344
the active reference version, investigate the two

45
00:02:10.453 --> 00:02:13.206
sample alignment problems, and explain what the

46
00:02:13.359 --> 00:02:15.710
report can conclude when a direction check

47
00:02:15.729 --> 00:02:16.694
was skipped.