Loading page…
Please wait while we prepare this page.
7-day free trial7-day free trialPlease wait while we prepare this page.
Practical resources
Blank templates and completed synthetic examples for road-data preparation, review and handover. Adapt them to the receiving authority’s requirements.
Identify every file in a delivery: survey period, file family, source edition, network context, byte length, SHA-256 and review evidence.
Download blank delivery manifest (JSON)
This is a training record, not an approval. “Not supplied” means unknown or not applicable to the demonstration; it does not mean zero.
| project | SYNTHETIC training demonstration |
|---|---|
| delivery id | DEMO-DELIVERY-001 |
| filename | tmh9-flx-corrected.flx |
| file family | TMH-18 .flx |
| source edition | Committee Draft 5.0, February 2016 |
| bytes | 190 |
| sha256 | 3047ba25f84e213ed6c43e7424dea1702d934c1729bb915280dae0d8d6bd8203 |
| source record count | 1 |
| count definition | One headerless synthetic data record; CRLF terminator excluded |
| template code | TMH-18.flx |
| software template version | v5-2016 |
| validation run id | Not supplied |
| certificate id | Not supplied |
| known exceptions | No complete field assessment, network reference or real authority acceptance is supplied |
Account for records exported, received, loaded, rejected and intentionally excluded. Keep the categories mutually exclusive.
Download blank import reconciliation (JSON)
This is a training record, not an approval. “Not supplied” means unknown or not applicable to the demonstration; it does not mean zero.
| delivery id | DEMO-DELIVERY-001 |
|---|---|
| source records | 1 |
| loaded records | 1 |
| rejected records | 0 |
| intentionally excluded records | 0 |
| unaccounted records | 0 |
| categories are mutually exclusive | true |
| equation | 1 = 1 + 0 + 0 + 0 |
| record key definition | Synthetic road ID, lane, start km, end km and measurement date |
| reviewer | Not supplied |
| acceptance decision | Demonstration only; no receiving-authority decision |
Keep the source manual edition, authority instruction, network version and software check-template version separate.
Download blank edition and delivery profile (JSON)
This is a training record, not an approval. “Not supplied” means unknown or not applicable to the demonstration; it does not mean zero.
| manual title | TMH-18 Road Asset Data Electronic Exchange Formats |
|---|---|
| manual edition | Committee Draft 5.0 |
| manual issue date | February 2016 |
| authority instruction reference | Not supplied |
| required file families | .flx |
| template name | TMH-18.flx |
| software template version | v5-2016 |
| covered requirements | Selected positional field layout; Declared range of SURFACE_FAILURE_DEG |
| checks outside platform | This example does not verify assessor judgement; No network alignment result is claimed |
| profile decision by | Not supplied |
Explain the finding, affected records, evidence, proposed treatment and limitations so another engineer can review the decision.
Download blank engineering exception note (Markdown)
This is a training record, not an approval. “Not supplied” means unknown or not applicable to the demonstration; it does not mean zero.
| finding | RANGE:SURFACE_FAILURE_DEG |
|---|---|
| scope | One synthetic record, field 20 |
| observation | Export 6 disagrees with invented source note 2 and lies outside 0–5 |
| evidence | tmh9-flx-invalid.flx, tmh9-flx-corrected.flx and the worked example |
| treatment | Correct the export to the known source value 2; do not record an exception merely to suppress the error |
| reviewer | Not supplied |
| approval | Not supplied |
| follow up | Revalidate the corrected saved file; assess all other project requirements separately |
Compare a faulty file with its corrected counterpart and the expected narrow validation result. These examples do not contain real survey evidence.
Download the completed synthetic working records (JSON) · Read example assumptions and test scope
The reconciliation above is a fictional one-record import, not a report from a live project. The manifest’s byte count and SHA-256 are calculated from the actual corrected synthetic FLX download.
Look up the certificate and compare its recorded SHA-256 with a local digest of the exact file you received. A matching hash establishes file identity; it does not establish measurement accuracy or override a withdrawn certificate.
Follow the file-verification guide or open the public verifier.
DATSEMBRA (Pty) Ltd permits you to copy and adapt these original templates for your project work. Retain the version and scope note when sharing an unmodified template. The templates do not replace the source manuals or your project’s acceptance procedure.