Data coverage

What this shows. One row for each dataset an API answer or MCP tool result comes from, and one for each edition of it we hold: 38 datasets in 38 rows. Each row names the jurisdiction the data is law or reference for, the edition and the dates the authority gives it, where the values came from, and when the authority was last checked. The calculators (CBM, loading metres, chargeable weight, pallet fitting, unit conversion and the rest) compute from your inputs and hold no dataset, so they have no row of their own; the tables they read do. ADR 2027 is held beside ADR 2025 and its status is the one the depositary record gives: accepted.

Verification is the state every answer already carries in its _source: verified (checked against the authority as the dataset’s verification decision records), pending-verification (not yet independently verified as a whole), computed (worked out by a published method) or live (fetched from the authority on every request). Beside it is how the check was made, and, where a dataset records a state for each record, the count of records in each state, in the words the data uses. We do not round a mixed dataset up to a better word.

Source status says whether the edition we serve was the authority’s current one when we last checked its page, or whether the data is fetched live. The licensing status is the one on Data Licensing, which says what we know of each publisher’s terms. The dates are those of this page’s build: the daily authority check records its result without redeploying the site, so the last check shown can be a little older than the latest one. The Upstream column is not of the build: it is the state every answer carries, read from the site’s daily upstream check (which could not be read when this page was rendered, so every row says unknown); its five states are explained on Data status.

Not to be confused with field coverage. Elsewhere in our documentation, “coverage” can mean whether every field a source holds is served; this page is about which datasets, jurisdictions and editions are served at all.

The same data as JSON

The matrix is at /api/coverage, with every row’s authority, source link, retrieval method, record count, file checksum and the reasons for anything not recorded. The licensing rows are at /api/data-licensing. Both are generated from the same registry as this page. Jurisdictions: ADR contracting parties (the contracting parties to ADR (the Agreement concerning the International Carriage of Dangerous Goods by Road)); UK (the United Kingdom); EU (the European Union); US (the United States); COTIF member states (the member states of COTIF (the Convention concerning International Carriage by Rail), to which RID is an appendix); Worldwide (worldwide: a global reference, not the law of one jurisdiction).

This page is reference information about our data, not legal advice. How each dataset is sourced and verified is on the Methodology page.