Projects and reference alignment in TMH18 Validator

Connect the survey evidence

Harbour Roads Training is reviewing a fictional road-survey programme. This lesson brings its files, references, alignment findings and report into one project context. Start with New project. Give the programme a clear name, choose the applicable authority and add the survey period when needed. Our example is Training network review. A project can group files before references are available. That helps organise work, but missing references limit which alignment checks can run. Geometry supplies the road line. Network definitions supply road identifiers and kilometre ranges. Classification and lane files provide their own supporting context.

Review registration findings

Upload the reference files and inspect their registration results. A usable reference can still have findings that need attention. Review the draft reference set before activation. The active version remains in use until deliberately replaced, so record which version supports the review. Add a survey using its matching template. File checks assess the export itself; project alignment assesses agreement with the available project references. A training survey uses road DEMO 02, but the reference contains DEMO 01. Investigate the identifier and source network before interpreting the measurements.

Example: section beyond the road

The illustrative reference ends at kilometre ten, while a survey section ends at ten point five. Check the intended road and range rather than trimming the value blindly. Direction follows ordered survey positions along the reference road. If usable geometry or positions are missing, the check may not run. Skipped never means passed. Coverage shows where records exist, not whether they are correct. Project settings distinguish advisory alignment from findings that can gate sign-off. The project report identifies what was checked, not checked and excluded. Read those boundaries before using totals or presenting the programme as complete.

Understand cost and certification

Reference files and alignment rechecks are free. Survey validation follows its credit workflow, and reference files themselves are not certified.

Connect the reference to the finding

The first training row names DEMO 02 while the reference names DEMO 01. Resolve that identity conflict before interpreting measurements. A separate example ends at 10.5 km against a reference ending at 10.0 km: the 0.5 km excess is evidence to investigate, not permission to trim the source automatically.

Keep the active reference version with the result. Geometry, network, classification and lane references contribute different evidence. A usable registered reference can still have findings. When direction lacks usable geometry or positions, record the limitation instead of calling the check passed.

Practise and check your interpretation

Pause here. Identify the active reference version, investigate the two sample alignment problems, and explain what the report can conclude when a direction check was skipped.

The fictional project screens show an active reference set and a separate draft. A draft does not replace the active version until activation. DEMO-02 versus reference DEMO-01 requires an identifier/network investigation; an end at 10.500 km beyond a 10.000 km reference requires a range investigation. Do not trim or rename values blindly. Missing geometry can leave direction unchecked. Coverage shows where records exist, while the report must state included, excluded and not-checked scope.

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.