Big Physical
RTE documentation
The RTE documentation is available here.
What this API collects
Validated physical measurements for a delivery point, in two states:
- initial values, read from the validated points endpoint;
- updated values, published later by RTE when a measurement is revalidated. They are read from the updated data endpoint and overwrite what was collected before.
Insights configuration
Source
Create one source per EIC, as described in Source configuration.
| Property | Value |
|---|---|
| Source type | Rte |
| Meter number | The EIC code |
Variables
| Property | Value |
|---|---|
| Name | Free text |
| Variable type | Basic |
| Mapping config | See Mapping config |
| Granularity | 10 minutes or 5 minutes, depending on the resolution of the data |
| Quantity type | Instant |
| Unit | Kilowatt (kW) or kilovar (kvar) |
Mapping config
BIG-PHYSICAL_{state}_{product}_{status}_{resolution}_{unitName}
{state}
| Value | Meaning |
|---|---|
INITIAL |
The first values published for the day, read from the validated points endpoint. |
UPDATED |
Values revalidated afterwards by RTE, read from the updated data endpoint. When a correction is published several times, the latest one wins. |
{product}
| Value | Meaning |
|---|---|
ACTIVE_POWER_IN |
Average active power injected |
ACTIVE_POWER_OUT |
Average active power withdrawn |
{status}
| Value | Meaning |
|---|---|
Z01 |
Validated |
A02 |
Not available |
A single response can mix both statuses, and the values are split by status into different keys. Create the
A02 variables as well if you want to see where the measurement is missing rather than only where it is sound.
{resolution}
| Value | Applies to |
|---|---|
PT10M |
Data points timestamped before 2024-06-01T00:00:00Z |
PT5M |
Data points timestamped on or after 2024-06-01T00:00:00Z |
Important
The resolution follows the timestamp of the data, not the day it is collected. A recovery that reaches back across 2024-06-01 produces both resolutions in the same run, so both variables have to exist for the history to be complete.
{unitName}
| Value | Meaning |
|---|---|
KW |
Kilowatt |
KVAR |
Kilovar |
Examples
BIG-PHYSICAL_INITIAL_ACTIVE_POWER_IN_Z01_PT10M_KW
BIG-PHYSICAL_UPDATED_ACTIVE_POWER_OUT_A02_PT5M_KVAR
Collection schedule
The collection runs six times a day, in UTC. Two of these runs fall in the first slot of the day and collect the initial values before looking for corrections; the four others collect corrections only.
| Time (UTC) | BIG-PHYSICAL_INITIAL_* |
BIG-PHYSICAL_UPDATED_* |
|---|---|---|
| 00:30 | Yes | Yes |
| 07:30 | Yes | Yes |
| 08:15 | — | Yes |
| 14:30 | — | Yes |
| 16:00 | — | Yes |
| 17:00 | — | Yes |
Recovery behaviour
Initial values are collected by gap filling over the last 31 days: a day is queried only when one of the
BIG-PHYSICAL_INITIAL_* variables has no data for it. Days already covered are left untouched, so existing
values are never rewritten by an initial collection.
Note
Corrections are a separate path. They are driven by what RTE announces on the updated data endpoint, and they do overwrite the values already collected — that is their purpose.