Watch the overview
About 2 minutes. A narrated explainer; the transcript is below. The written guide includes additional detail.
Read the video text
- 0:00Our fictional survey contains a position away from the expected road. We will use road and map context to investigate it without confusing a visual match with certification.
- 0:10Start with the survey's road and coordinate records. Use the map as context for the finding you are reviewing, rather than as a separate verdict.
- 0:18The sample survey records a point beside the reference line. First inspect the reported coordinates rather than assuming the displayed road match is the original measurement.
- 0:27Reported coordinates and matched road geometry serve different purposes. Matching to OpenStreetMap is separate from checking the survey against a project's approved reference files.
- 0:37If latitude and longitude are exchanged, a point can appear far from the expected area. Check the field definitions, sign and source coordinate system before editing.
- 0:47A point drawn near a road is not evidence that its original coordinates are correct. Use the survey record and reference information to decide the remedy.
- 0:57Read the road section’s start, end and associated findings together. On large files, road matching may load for the current view rather than the whole network at once.
- 1:06If the file has no usable coordinates, the map cannot draw them. Read the message and use the table findings; an empty map is not a successful geometry check.
- 1:16Travel direction follows the order of positions along the road geometry. It is not simply left or right on the screen, and missing geometry can prevent the check.
- 1:25The map helps investigation. File validation, project alignment, OpenStreetMap matching and professional review remain separate sources of evidence.
- 1:35Pause here. Explain whether the sample issue concerns reported coordinates, road matching or project alignment. State which source you would check before making a correction.
Put the finding on the road
Our fictional survey contains a position away from the expected road. We will use road and map context to investigate it without confusing a visual match with certification. Start with the survey's road and coordinate records. Use the map as context for the finding you are reviewing, rather than as a separate verdict. The sample survey records a point beside the reference line. First inspect the reported coordinates rather than assuming the displayed road match is the original measurement.
Read the map layers
Reported coordinates and matched road geometry serve different purposes. Matching to OpenStreetMap is separate from checking the survey against a project's approved reference files. If latitude and longitude are exchanged, a point can appear far from the expected area. Check the field definitions, sign and source coordinate system before editing. A point drawn near a road is not evidence that its original coordinates are correct. Use the survey record and reference information to decide the remedy.
Follow the segment
Read the road section’s start, end and associated findings together. On large files, road matching may load for the current view rather than the whole network at once. If the file has no usable coordinates, the map cannot draw them. Read the message and use the table findings; an empty map is not a successful geometry check. Travel direction follows the order of positions along the road geometry. It is not simply left or right on the screen, and missing geometry can prevent the check.
Keep context separate
The map helps investigation. File validation, project alignment, OpenStreetMap matching and professional review remain separate sources of evidence.
Compare location and sequence separately
A point can lie close to a line while belonging to a different road identifier. Resolve its identity and coordinate context before interpreting distance from the line. Likewise, a sequence drawn on a map does not prove travel direction unless the ordering and required source fields support that interpretation.
Use a map to investigate a reported position, not to move the data into a visually convenient place. Record the reference version, reported tolerance and source correction where one is justified. Missing geometry leaves relevant checks unavailable.
Practise and check your interpretation
Pause here. Explain whether the sample issue concerns reported coordinates, road matching or project alignment. State which source you would check before making a correction.
The coordinate worksheet deliberately swaps latitude and longitude. The expected fictional position is latitude −30.412, longitude 22.936. Inspect the source definitions, signs and coordinate system before correcting it. Reported coordinates, OpenStreetMap matching and project-reference alignment are different evidence. Travel direction follows the ordered geometry, not screen-left or screen-right. Missing usable coordinates can leave a check unavailable.
Use the signed-in onboarding library to record viewing progress and return to unfinished lessons. Watching the public article is useful for reference, but does not update your account’s lesson completion record.
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.