Skip to content

Commit 9432fde

Browse files
committed
update table
1 parent 4c45065 commit 9432fde

1 file changed

Lines changed: 8 additions & 18 deletions

File tree

example_data/00_README.md

Lines changed: 8 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -30,25 +30,15 @@ The following table describes the columns present in the `orderbook_2022-01-02.c
3030

3131

3232
| Column Name | Data Type | Description | Notes |
33-
3433
| :--- | :--- | :--- | :--- |
35-
36-
| *(unnamed)* | `Integer` | A unique identifier. | Corresponds to the `ID` field in the EPEX specification |
37-
38-
| `initial` | `Integer` | A unique identifier for the order. | Corresponds to the `initialID` field in the EPEX specification. |
39-
40-
| `side` | `String` | The side of the order book. | Can be `BUY` or `SELL`. |
41-
42-
| `start` | `UTC Timestamp` | The start of the delivery period for the order. | Formatted as `YYYY-MM-DDTHH:MM:SSZ`. |
43-
44-
| `transaction` | `UTC Timestamp` | The exact timestamp when the order was submitted (transacted). | Formatted as `YYYY-MM-DDTHH:MM:SS.sssZ`. |
45-
46-
| `validity` | `UTC Timestamp` | A timestamp indicating the expiration of the order. | In the sample data, some fields are empty, which signifies no expiry. Formatted as `YYYY-MM-DDTHH:MM:SS.sssZ`. |
47-
48-
| `price` | `Float` | The price of the order in EUR/MWh. | Negative prices are possible in electricity markets. |
49-
50-
| `quantity` | `Float` | The volume of the order in MWh, in increments of the minimum order volume of 0.1 MWh. | Represents the amount of electricity being bought or sold; the value is always positive. |
51-
34+
| *(unnamed)* | `Integer` | A unique identifier. | Corresponds to the `ID` field in the EPEX specification. |
35+
| `initial` | `Integer` | A unique identifier for the order. | Corresponds to the `initialID` field in the EPEX specification. |
36+
| `side` | `String` | The side of the order book. | Can be `BUY` or `SELL`. |
37+
| `start` | `UTC Timestamp` | The start of the delivery period for the order. | Formatted as `YYYY-MM-DDTHH:MM:SSZ`. |
38+
| `transaction` | `UTC Timestamp` | The exact timestamp when the order was submitted (transacted). | Formatted as `YYYY-MM-DDTHH:MM:SS.sssZ`. |
39+
| `validity` | `UTC Timestamp` | A timestamp indicating the expiration of the order. | In the sample data, some fields are empty, which signifies no expiry. Formatted as `YYYY-MM-DDTHH:MM:SS.sssZ`. |
40+
| `price` | `Float` | The price of the order in EUR/MWh. | Negative prices are possible. |
41+
| `quantity` | `Float` | The volume of the order in MWh, in increments of the minimum order volume of 0.1 MWh. | Represents the amount of electricity being bought or sold; the value is always positive. |
5242

5343

5444
### Example Row

0 commit comments

Comments
 (0)