Industry steel Blastfurnace - transformation demand has double count in Cokes In EB generated values.

[kaskranenburgQ]

In industry_steel.yml the values for industry steel are generated.
Blastfurnace - transformation demand consists of Coal demand and Cokes demand.
For Coal demand (key: input_energy_blastfurnace_transformation_coal_input_demand).
The code that is used to extract data from the EB is:
EB("Transformation input - blast furnaces - energy use", "Coal incl lignite and peat")
In the entso.yml, this is then translated as the sum of the values of the intersection the row "Transformation input - blast furnaces - energy use" and the following columns that fall under "Coal incl lignite and peat":
- Anthracite
- Coking coal
- Other bituminous coal
- Sub-bituminous coal
- Patent fuel
- Coke oven coke
- Gas coke
- Coal tar
- Brown coal briquettes
- Peat and peat products
- Lignite

For Cokes demand (key: input_energy_blastfurnace_transformation_cokes_input_demand).
The code that is used to extract data from the EB is:
EB("Transformation input - blast furnaces - energy use", "Coke oven coke")
Meaning that the value on the intersection of the row "Transformation input - blast furnaces - energy use" & the column "Coke oven Coke" is returned.

Since Coke oven coke also falls under "Coal incl lignite and peat" A double count of Coke oven coke is appearing in the Blastfurnace - transformation input. For instance, the NL-dataset that is online on the Dataset manager at the moment counts 48 PJ of cokes double.

Since this data if als used to determine the losses of the transformation output, this section is affected as well.

A solution to this problem would be to change the extraction code/definition of input_energy_blastfurnace_transformation_coal_input_demand in industry_steel.yml to:

EB("Transformation input - blast furnaces - energy use", "Coal incl lignite and peat") - EB("Transformation input - blast furnaces - energy use", "Coke oven coke")

Notifying @mabijkerk

[mabijkerk]

Well-spotted! We might also update the product mappings in entso.yml to for example add coal exlc. cokes. When we fix this we also need to re-export the EU datasets to ETSource.

[github-actions]

This issue has had no activity for 60 days and will be closed in 7 days. Removing the "Stale" label or posting a comment will prevent it from being closed automatically. You can also add the "Pinned" label to ensure it isn't marked as stale in the future.