We publish only a reading that we have actually retrieved. We never interpolate, average or estimate missing points. If the parser does not return a value within the permitted range for a given index, no data point is created: we prefer a gap in the series to a figure nobody has confirmed.
In brief: what, from where and how often
| Data | Source | Unit | Publication frequency |
|---|---|---|---|
| Sea freight, composite index | Drewry World Container Index (WCI) | USD per 40-foot container | weekly |
| Sea freight, departures from Shanghai | SCFI, Shanghai Shipping Exchange | index points | weekly |
| Rail, China to Europe | ERAI (Eurasian Rail Alliance Index), westbound | USD per FEU | weekly |
| Air freight, East-West | Drewry Airfreight Price Index | USD per kilogram | monthly |
| EU trade defence measures | TRON and EUR-Lex | case number, CN code, status | daily |
| USD/PLN exchange rate | NBP, table A | PLN per 1 USD | on working days |
Sea freight indices
Drewry World Container Index
From the publicly available index page we take the composite value, expressed in US dollars per 40-foot container, and the weekly percentage change. Drewry publishes an update once a week, so between releases the value does not change and that is exactly how we present it: with the reading date, not today's date.
The reading goes through a range check. Values outside a sensible band for this index are treated as a parsing error and rejected, rather than storing a suspicious figure.
SCFI (Shanghai Containerized Freight Index)
The index is published by the Shanghai Shipping Exchange. We take the composite value (comprehensive index) from the public table on the exchange's website, also once a week, together with the publication date. SCFI is a points-based index, so we report points, not dollars, and we do not mix it with WCI in a single series.
The current values of both indices, with the week-on-week change, are shown on the freight rates from China page (in Polish). How to read these indices is explained in the article what the WCI, SCFI and ERAI indices tell you, and why a forwarder's offer rarely equals the index in the article what a container from China really costs (both in Polish).
Rail, China to Europe
We use ERAI, the index published by the Eurasian Rail Alliance. We collect the westbound direction, that is carriage from China to Europe, in US dollars per FEU. From the index page we also take the date of the last change in value, and that is the reading date in our series.
Air freight
We track the Drewry Airfreight Price Index for East-West routes, published in US dollars per kilogram. This index is updated on a monthly cycle, so on our site it also changes once a month. If the publisher describes the value in a sentence referring to a specific month, we assign the reading to that month, not to the day we retrieved it.
European Union trade defence measures
We collect information on anti-dumping duties, anti-subsidy duties and safeguard measures from two places at once. The first is TRON, the European Commission's portal for trade defence proceedings: from there we take ongoing investigations, their numbers and status. The second is EUR-Lex, from which we take acts published in the Official Journal of the European Union: regulations imposing duties, notices of initiation and notices of impending expiry of measures.
We store only deterministic data, meaning data that can be read unambiguously from the document: the case number, the subject of the proceeding, CN codes, dates and a link to the act. Entries prepared by hand by the editorial team take precedence and the automated process never overwrites them. The finished summary, broken down by CN code, is published in the register of anti-dumping duties on goods from China (in Polish).
We do not publish a specific duty amount on the basis of the automated summary alone. A rate appears only once a human has checked it in the text of the regulation in EUR-Lex and in a tariff database (TARIC or ISZTAR4) and confirmed that it applies to exactly this CN code, this producer and this period. Until that verification is done we show the case status and a link to the document, without a figure.
Our summary does not replace binding tariff information or a decision of the customs authority. Before clearance, the rate should be confirmed in TARIC or ISZTAR4 for the specific code and origin of the goods.
On the Polish side we additionally follow notices from PUESC, the platform of the Polish National Revenue Administration: information on the handling of customs declarations and on changes to customs systems goes into Radar issues, because it changes the course of clearance rather than the rate itself.
Exchange rates
We take exchange rates from the public API of Narodowy Bank Polski (NBP, the Polish central bank), from table A (average rates). For every rate we work with the effective date given by NBP (the effective date field), not the date of our request. NBP does not publish a table on non-working days, so at weekends and on public holidays the last published rate applies and that is how we describe it.
Reading date and frequency
We distinguish three dates and try not to confuse them:
- Date of publication by the publisher: when the index was announced (for example the weekly WCI update).
- Reading date: when our collector retrieved the value. This is the date shown next to figures on the site.
- Radar issue date: the day that a particular issue of the digest covers.
The collectors run automatically, every day. A weekly index, however, does not change more often than its publisher releases it, even if we check it every day.
When a source does not respond
Each source is collected independently and in isolation: a failure in one does not stop the others. When a source's page does not respond, changes its layout or returns a value outside the permitted range, the following happens:
- no new data point is created, and a gap stays in the series instead of a made-up value;
- the site still shows the last confirmed reading together with its date, so that it is clear the data has not been refreshed;
- the error goes to the collector log, and the editorial team checks whether it is a temporary failure or a change in page structure that requires a parser fix;
- if the outage drags on, we say so plainly in the Radar issue.
Corrections
Index publishers sometimes revise a published value. If that happens, we correct the point in our series to the revised value and keep the date of the source reading. When a revision changes the conclusions of an article or Radar issue published earlier, we add a dated correction note to it instead of quietly swapping the figure. We apply the same rule to our own mistakes, and the reporting procedure is described in our editorial policy.
Rights to source data
The indices remain the property of their publishers. We quote publicly available values, always naming the publisher and linking to its website. We do not redistribute full, licensed series or route-level data that sits behind a paywall.