Submit
Upload a UTF-8 CSV. Maximum 50 MB per file. Required headers map to the TMH-18 ingest schema; the full list is in the docs.
Meridian/V validates CSV uploads against the COTO TMH-18 (Road Asset Data Electronic Exchange Formats) specification. On engineer co-sign, each submission gets a SHA-256 signed certificate any third party can verify.
Pre-pilot. Open to applications from South African road authorities, consultants, and contractors.
Upload a UTF-8 CSV. Maximum 50 MB per file. Required headers map to the TMH-18 ingest schema; the full list is in the docs.
Five rule checks run on upload: required-header presence, UTF-8 encoding, monotonic chainage, deflection-sensor ratio sanity, and temperature-correction presence. Warnings can be overridden with a justification — every override is recorded in the immutable audit log.
A user with the principal_engineer role co-signs. The platform computes a SHA-256 hash over the stored file bytes and issues a certificate. Anyone can verify the certificate at tmh18.com/verify.
Meridian/V targets the South African Technical Methods for Highways (TMH) series published by the Committee of Transport Officials (COTO) and Department of Transport. Currently we ingest CSVs aligned with the TMH-18 data exchange format. Other TMH documents are on the roadmap as schemas are added to the engine.
| Standard | Published | Platform support | Scope |
|---|---|---|---|
| TMH-18 | v4 · Oct 2014 | In progress | Road Asset Data Electronic Exchange Formats — primary ingest |
| TMH-9 | May 2016 | Roadmap | Manual for Visual Assessment of Road Pavements |
| TMH-22 | Draft V8b · Mar 2013 | Roadmap | Road Asset Management Manual |
Source documents: transport.gov.za/tmh-documents.
Meridian/V is a web platform that validates road asset datasets aligned with the South African TMH-18 (Road Asset Data Electronic Exchange Formats) specification published by the Committee of Transport Officials (COTO). On co-sign by an engineer, the platform issues a SHA-256 cryptographically signed certificate over the stored file bytes.
TMH-18 is published by the Department of Transport on behalf of COTO. The currently published version available from transport.gov.za is Version 4 (October 2014). Meridian/V aligns its ingest to that document. The current rule set is a subset (header presence, UTF-8 encoding, monotonic chainage, deflection ratio, temperature correction) and will expand as additional sections are implemented.
No. Meridian/V is pre-pilot. We are accepting applications from South African road authorities, consultants and contractors via the sign-up form. Each application is reviewed before access is granted.
South African road authorities (SANRAL; provincial departments such as the Western Cape Department of Mobility, Gauteng Department of Roads and Transport, Eastern Cape Department of Transport, and Mpumalanga Department of Public Works, Roads and Transport), as well as consulting engineers and contractors who submit pavement and road asset data on their behalf.
Visit tmh18.com/verify and enter the certificate ID. The verifier returns the dataset metadata, signers, issued time, and SHA-256 hash so any third party can independently re-hash their copy of the file and confirm it matches. No login required.
Pre-pilot infrastructure is hosted on AWS us-east-1 (cost-driven). Migration to AWS af-south-1 (Cape Town) is on the roadmap before any commercial launch so customer data resides within South Africa, consistent with POPIA expectations.
Free during pre-pilot for accepted organisations. Commercial pricing has not been published.
API tokens can be issued from the app. A documented REST API for programmatic submissions and webhooks for cosign events is on the post-MVP roadmap.