ADT: version, location and traffic classes

Choose the right traffic template

Traffic link data can look convincing while using the wrong template version. The older annual-average fields and the newer average-daily-traffic fields must not be treated as identical layouts.

In the version-five description, minibus traffic is included in the light total. Adding a subclass again can misstate a total. This diagram explains the relationship; it is not claiming an automated sum check.

Reject a broken field type

The schema validator checks declared types and constraints. A fractional value in an integer traffic-count field is a concrete type problem, even when the road identifier is valid.

Applicable cross-row checks examine the location key and kilometre range, including duplicates and reversed or equal intervals. Project references can add road and lane context where available.

Read traffic classes in the chosen definition

A fictional count total is meaningful only with its period, location and class definitions. Confirm the selected ADT edition and the original road context before comparing the fields. A valid-looking numeric value can still be attached to the wrong class or road record.

Investigate findings using the declared schema and source export. Keep missing observations separate from recorded zero traffic. A structural or class-consistency result does not validate the equipment, monitoring programme or representativeness of the count period.

For a disputed total, retain the original interval records and the declared vehicle-class mapping. Compare equivalent periods and directions before drawing a conclusion from differences between two exports.

Do not promise an unbuilt check

The audited rule pack does not establish a comprehensive traffic-total reconciliation. Do not advertise a class-sum check merely because the catalogue describes those classes.

Select the matching version, preserve the original count evidence, and investigate each actual finding. Correct the export without double-counting subclasses, then rerun the checks supported for that file.

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.