Watch the overview
77 seconds. A narrated explainer; the transcript is below. The written guide includes additional detail.
Read the video text
- 0:00The road identifier says DEMO zero one,
- 0:03but the survey point sits beside a
- 0:05different line. A column check alone cannot
- 0:08resolve that conflict. Geometry provides an independent
- 0:11comparison. Use a readable road geometry reference
- 0:15with the right identifiers and coordinate system.
- 0:18A point and a shapefile cannot be
- 0:20compared meaningfully until their coordinates can be
- 0:23interpreted consistently. The alignment engine locates a
- 0:27survey coordinate on its own road line
- 0:29and evaluates its offset. The illustration shows
- 0:32one point on the line and another
- 0:34displaced from it. When appropriate, it considers
- 0:37another section of the same parent road
- 0:39before another road. A nearby line is
- 0:42evidence to investigate, not permission to rewrite
- 0:45the submitted identifier. Bands depend on the
- 0:48data type and coordinate precision. Read the
- 0:51reported tolerance and its basis. These operational
- 0:55thresholds are not a universal guarantee of
- 0:57measurement accuracy. A missing road geometry leaves
- 1:00the relevant comparison unavailable. Inspect the source
- 1:04coordinates, reference version and finding, correct the
- 1:07cause, and rerun. Do not drag points
- 1:10into place just to clear a warning.
Does the point fit its road?
The road identifier says DEMO zero one, but the survey point sits beside a different line. A column check alone cannot resolve that conflict. Geometry provides an independent comparison.
Use a readable road geometry reference with the right identifiers and coordinate system. A point and a shapefile cannot be compared meaningfully until their coordinates can be interpreted consistently.
Measure the spatial offset
The alignment engine locates a survey coordinate on its own road line and evaluates its offset. The illustration shows one point on the line and another displaced from it.
When appropriate, it considers another section of the same parent road before another road. A nearby line is evidence to investigate, not permission to rewrite the submitted identifier.
Keep identity, position and tolerance together
A point labelled DEMO-01 must first be considered against its own road geometry. The nearest line on a map may represent another road or another section. Confirm coordinate interpretation, road identity and reference completeness before using proximity as evidence. A mismatch can originate in the exported coordinate, its declared system or the reference itself.
Retain the reported distance and tolerance with the finding. A band reflects the implemented check and its source context; it is not a survey-accuracy certificate. Investigate the original evidence before replacing the point, identifier or reference, and then inspect the new run.
Explain the tolerance
Bands depend on the data type and coordinate precision. Read the reported tolerance and its basis. These operational thresholds are not a universal guarantee of measurement accuracy.
A missing road geometry leaves the relevant comparison unavailable. Inspect the source coordinates, reference version and finding, correct the cause, and rerun. Do not drag points into place just to clear a warning.
Sources and scope
This guide describes the platform workflow; it does not establish a requirement of a TMH manual. Platform review and certification are described in the product documentation.
Put it into practice
Review check templatesSign-in and the relevant account permissions are required.