Watch the overview
84 seconds. A narrated explainer; the transcript is below. The written guide includes additional detail.
Read the video text
- 0:00Unpaved-road visual data needs its own template
- 0:03and context. It is not a flexible-pavement
- 0:06file with a different name. Road type,
- 0:09moisture and gravel observations carry different meanings.
- 0:13The template checks declared code sets, including
- 0:16road type and moisture. An unsupported moisture
- 0:19code is a field finding; it is
- 0:21not a measurement of the actual water
- 0:23content. The current segment rule uses a
- 0:26five kilometre rural baseline and a fifty-percent
- 0:29band. An eight kilometre assessment exceeds the
- 0:32seven point five kilometre upper band. Urban
- 0:35context needs separate review. Condition indices are
- 0:39checked against zero to one hundred where
- 0:41present, while declared distress ratings have their
- 0:43own constraints. Keep a coding error separate
- 0:46from a professional judgement about road condition.
- 0:49Do not populate an unmeasured instrument field
- 0:52with invented data. In combined-instrument checking, the
- 0:56repeated-vector rule excludes partially measured vectors rather
- 1:00than treating repeated roughness alone as copied
- 1:02full measurements. Select the right schema, inspect
- 1:06the original assessment and review each finding
- 1:09in context. Preserve unavailable measurements honestly. Automated
- 1:14validation supports an engineering decision; it does
- 1:17not create missing survey evidence.
Unpaved data has its own context
Unpaved-road visual data needs its own template and context. It is not a flexible-pavement file with a different name. Road type, moisture and gravel observations carry different meanings.
The template checks declared code sets, including road type and moisture. An unsupported moisture code is a field finding; it is not a measurement of the actual water content.
Interpret assessment length
The current segment rule uses a five kilometre rural baseline and a fifty-percent band. An eight kilometre assessment exceeds the seven point five kilometre upper band. Urban context needs separate review.
Condition indices are checked against zero to one hundred where present, while declared distress ratings have their own constraints. Keep a coding error separate from a professional judgement about road condition.
Distinguish an observation from missing evidence
An unpaved-road record should retain the location and assessment context that explain its values. A blank, a declared unavailable code and a measured zero are not interchangeable. Before normalising an export, read the selected field definition and compare the original assessment record.
Keep unit, coding and segment questions separate in the review notes. Filling gaps with convenient in-range values can make a file look tidier while reducing its evidential value. Review the applicable findings, retain genuine limitations and rerun only after a justified source correction.
Do not fabricate unmeasured data
Do not populate an unmeasured instrument field with invented data. In combined-instrument checking, the repeated-vector rule excludes partially measured vectors rather than treating repeated roughness alone as copied full measurements.
Select the right schema, inspect the original assessment and review each finding in context. Preserve unavailable measurements honestly. Automated validation supports an engineering decision; it does not create missing survey evidence.
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.