WEBVTT

1
00:00:00.000 --> 00:00:02.510
Our fictional survey contains a position away

2
00:00:02.512 --> 00:00:04.592
from the expected road. We will use

3
00:00:04.666 --> 00:00:06.889
road and map context to investigate it

4
00:00:07.107 --> 00:00:09.905
without confusing a visual match with certification.

5
00:00:10.037 --> 00:00:12.157
Start with the survey's road and coordinate

6
00:00:12.163 --> 00:00:14.663
records. Use the map as context for

7
00:00:14.669 --> 00:00:16.757
the finding you are reviewing, rather than

8
00:00:16.757 --> 00:00:19.259
as a separate verdict. The sample survey

9
00:00:19.260 --> 00:00:21.618
records a point beside the reference line.

10
00:00:21.763 --> 00:00:24.406
First inspect the reported coordinates rather than

11
00:00:24.587 --> 00:00:26.267
assuming the displayed road match is the

12
00:00:26.267 --> 00:00:29.403
original measurement. Reported coordinates and matched road

13
00:00:29.410 --> 00:00:33.280
geometry serve different purposes. Matching to OpenStreetMap

14
00:00:33.288 --> 00:00:35.374
is separate from checking the survey against

15
00:00:35.382 --> 00:00:38.267
a project's approved reference files. If latitude

16
00:00:38.271 --> 00:00:40.418
and longitude are exchanged, a point can

17
00:00:40.533 --> 00:00:42.865
appear far from the expected area. Check

18
00:00:42.869 --> 00:00:45.535
the field definitions, sign and source coordinate

19
00:00:45.539 --> 00:00:48.470
system before editing. A point drawn near

20
00:00:48.488 --> 00:00:50.582
a road is not evidence that its

21
00:00:50.776 --> 00:00:53.750
original coordinates are correct. Use the survey

22
00:00:53.768 --> 00:00:56.478
record and reference information to decide the

23
00:00:56.496 --> 00:00:59.101
remedy. Read the road section’s start, end

24
00:00:59.101 --> 00:01:02.236
and associated findings together. On large files,

25
00:01:02.236 --> 00:01:03.837
road matching may load for the current

26
00:01:03.837 --> 00:01:05.505
view rather than the whole network at

27
00:01:05.505 --> 00:01:07.671
once. If the file has no usable

28
00:01:07.756 --> 00:01:10.618
coordinates, the map cannot draw them. Read

29
00:01:10.625 --> 00:01:12.990
the message and use the table findings;

30
00:01:12.990 --> 00:01:15.038
an empty map is not a successful

31
00:01:15.045 --> 00:01:18.136
geometry check. Travel direction follows the order

32
00:01:18.136 --> 00:01:20.692
of positions along the road geometry. It

33
00:01:20.692 --> 00:01:22.449
is not simply left or right on

34
00:01:22.449 --> 00:01:25.004
the screen, and missing geometry can prevent

35
00:01:25.004 --> 00:01:28.559
the check. The map helps investigation. File

36
00:01:28.565 --> 00:01:32.602
validation, project alignment, OpenStreetMap matching and professional

37
00:01:32.609 --> 00:01:35.957
review remain separate sources of evidence. Pause

38
00:01:35.969 --> 00:01:39.008
here. Explain whether the sample issue concerns

39
00:01:39.008 --> 00:01:42.774
reported coordinates, road matching or project alignment.

40
00:01:43.114 --> 00:01:45.402
State which source you would check before

41
00:01:45.414 --> 00:01:46.798
making a correction.