WEBVTT

1
00:00:00.400 --> 00:00:03.590
The road identifier says DEMO zero one,

2
00:00:03.600 --> 00:00:05.350
but the survey point sits beside a

3
00:00:05.360 --> 00:00:08.230
different line. A column check alone cannot

4
00:00:08.240 --> 00:00:11.830
resolve that conflict. Geometry provides an independent

5
00:00:11.840 --> 00:00:15.590
comparison. Use a readable road geometry reference

6
00:00:15.600 --> 00:00:18.470
with the right identifiers and coordinate system.

7
00:00:18.640 --> 00:00:20.630
A point and a shapefile cannot be

8
00:00:20.680 --> 00:00:23.270
compared meaningfully until their coordinates can be

9
00:00:23.280 --> 00:00:27.270
interpreted consistently. The alignment engine locates a

10
00:00:27.360 --> 00:00:29.350
survey coordinate on its own road line

11
00:00:29.360 --> 00:00:32.550
and evaluates its offset. The illustration shows

12
00:00:32.560 --> 00:00:34.510
one point on the line and another

13
00:00:34.560 --> 00:00:37.630
displaced from it. When appropriate, it considers

14
00:00:37.760 --> 00:00:39.790
another section of the same parent road

15
00:00:39.920 --> 00:00:42.320
before another road. A nearby line is

16
00:00:42.320 --> 00:00:45.360
evidence to investigate, not permission to rewrite

17
00:00:45.360 --> 00:00:48.630
the submitted identifier. Bands depend on the

18
00:00:48.800 --> 00:00:51.430
data type and coordinate precision. Read the

19
00:00:51.840 --> 00:00:54.870
reported tolerance and its basis. These operational

20
00:00:55.280 --> 00:00:57.430
thresholds are not a universal guarantee of

21
00:00:57.680 --> 00:01:00.880
measurement accuracy. A missing road geometry leaves

22
00:01:00.880 --> 00:01:04.790
the relevant comparison unavailable. Inspect the source

23
00:01:04.880 --> 00:01:07.750
coordinates, reference version and finding, correct the

24
00:01:07.840 --> 00:01:10.390
cause, and rerun. Do not drag points

25
00:01:10.400 --> 00:01:12.310
into place just to clear a warning.