TMH-14 traffic-file preparation and review

Distinguish traffic records from station definitions

An RSV traffic file contains typed records whose interpretation depends on their context. An RSS file describes counting stations. These are different structures; neither should be flattened into an ordinary survey CSV merely to make it open neatly in a spreadsheet.

Preserve the original text and sequence. Check the filename, required version and selected template. TMH-14 uses comma-delimited records and its character conventions differ from the semicolon-delimited UTF-8 convention used for ordinary TMH-18 exchange records.

Follow the header before interpreting a traffic record

H0 starts a header block and H9 ends it. Header records describe how subsequent data are interpreted. Type 20, for example, describes speed-summary settings in the header and speed-summary data in the traffic block. An identifier without its context is insufficient to select a field layout.

When a finding points to a record, inspect the preceding header and declared counts. Record the line, identifier and surrounding context. Do not sort away header boundaries or pad truncated measurements with invented zeroes.

Keep measurement quality separate from format acceptance

Successful parsing is one part of review. Structural checks, data-quality findings, interval completeness and station references still need attention. Sensor failures, calibration evidence and the monitoring programme explain whether the measurements are suitable for the intended use.

After correcting the export source, check the saved replacement again and reconcile record counts. Keep unresolved limitations with the delivery. A format result does not certify the traffic equipment, monitoring design or all engineering requirements.

Sources and scope

• COTO TMH-14: South African Standard Traffic Data Collection FormatCommittee Draft, Format Version 3.20, issue 4 April 2018. §§2.2–2.5: file naming, structure, comma-delimited records and field types.
• COTO TMH-14: header data recordsCommittee Draft, Format Version 3.20, issue 4 April 2018. Chapter 8, printed pages 41–57; §8.10 for header Type 20.
• COTO TMH-14: summary traffic data recordsCommittee Draft, Format Version 3.20, issue 4 April 2018. Chapter 11, printed pages 75–86; §11.2 for traffic summary Type 20.
• COTO TMH-14: counting station definition dataCommittee Draft, Format Version 3.20, issue 4 April 2018. Chapter 12, printed pages 87–93.

The cited sources describe their own requirements. Practical checklists and examples do not replace the receiving authority’s adopted profile. Platform review and certification are described in the product documentation.