Watch the overview
About 2 minutes. A narrated explainer; the transcript is below. The written guide includes additional detail.
Read the video text
- 0:00Harbour Roads Training has received a road-condition export. We will choose a matching template by file definition, rather than by whichever option happens to be first.
- 0:10Check templates lists file formats and their available versions. Read the description and state, then open the candidate template for its details.
- 0:18Compare required fields, value types and file extension with the source export. A similar filename does not prove the same structure or units.
- 0:28A traffic count and a road-condition assessment answer different questions. Selecting the wrong template can produce misleading findings or leave relevant checks unavailable.
- 0:38Record which template version applies to the upload. A result is meaningful in the context of the version and rule coverage actually used.
- 0:46Stable, review, beta and deprecated describe the template's lifecycle. They do not describe the quality of the survey file you are about to upload.
- 0:56If the template requires a section identifier that the export lacks, investigate the source format. Do not fill every row with an invented value to make the file fit.
- 1:06The catalogue's field or usage counts describe the template and visible submissions. They are not proof that all possible engineering checks are implemented.
- 1:16Custom-template administration is permission-restricted. Most users choose an existing approved template; changes to a definition should be controlled and reviewed.
- 1:25Pause here. Compare the training export with its candidate template. State the matching version, two required fields and one check that depends on those fields.
Choose checks deliberately
Harbour Roads Training has received a road-condition export. We will choose a matching template by file definition, rather than by whichever option happens to be first. Check templates lists file formats and their available versions. Read the description and state, then open the candidate template for its details. Compare required fields, value types and file extension with the source export. A similar filename does not prove the same structure or units.
Example: wrong survey family
A traffic count and a road-condition assessment answer different questions. Selecting the wrong template can produce misleading findings or leave relevant checks unavailable. Record which template version applies to the upload. A result is meaningful in the context of the version and rule coverage actually used. Stable, review, beta and deprecated describe the template's lifecycle. They do not describe the quality of the survey file you are about to upload.
Example: missing required column
If the template requires a section identifier that the export lacks, investigate the source format. Do not fill every row with an invented value to make the file fit. The catalogue's field or usage counts describe the template and visible submissions. They are not proof that all possible engineering checks are implemented. Custom-template administration is permission-restricted. Most users choose an existing approved template; changes to a definition should be controlled and reviewed.
Match the definition to the export
Compare the survey family, edition, field order, expected units and delimiter before choosing a template. A traffic-count export and a condition survey can both be text files while needing different definitions. Renaming an extension does not convert the underlying record structure.
After analysis, review which checks actually ran. A template catalogue describes available definitions, while the recorded result describes the specific file. Missing required context or unavailable references must not be interpreted as successful checking.
Practise and check your interpretation
Pause here. Compare the training export with its candidate template. State the matching version, two required fields and one check that depends on those fields.
The exercise uses TMH-18.blc v5-2016: Block Pavement Visual Condition Summary. The public authority code WCP is used solely as a valid format example; the survey and organisation are fictional and no authority endorsement is implied. Required fields include AUTH_ID, ROAD_ID, START_KM and MEASURE_DATE. START_KM and END_KM support the segment-consistency check. The exercise’s simplified diagrams are explanatory excerpts; the downloadable .blc files contain the complete field layout. Select a template by its definition, not by a convenient name.
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.