# EU Combustion Plant Records — EEA IED LCP (`nexgensignal/eu-combustion-plant-operating-hour-records`) Actor

Keyless pay-per-record EEA IED Large Combustion Plant register — site, type, thermal input, waste capacity, INSPIRE ids. No persons. EEA acknowledge. $0.05 per record on the Free plan, $0.0335 on Gold.

- **URL**: https://apify.com/nexgensignal/eu-combustion-plant-operating-hour-records.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** Automation, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 1,000 combustion plant records

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

## EU Combustion Plant Records — EEA IED LCP

**Keyless. Pay per record. Every European Large Combustion Plant — site, type, thermal input, and waste co-incineration capacity.**

This actor turns the **European Environment Agency (EEA) Industrial Emissions Directive (IED) Large Combustion Plants (LCP) register** into clean, per-plant records — the large combustion plants regulated under the IED across Europe. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per plant: the site name, the installation-part name and plant type, the total rated thermal input, the reporting year, specific operating conditions, and waste co-incineration capacities. Plant grain, structured for engineering use, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

The IED regulates Large Combustion Plants — the big boilers, turbines and engines that dominate Europe's industrial energy use — and the EEA publishes the register. This actor reads that register and flattens each plant into a single analysis-ready record: the site name (a facility/organisation), the installation-part name and the plant type, the total rated thermal input, the reporting year, the specific operating conditions declared, and the waste co-incineration attributes (hazardous-waste heat release, total nominal capacity for any waste, and the untreated-municipal-waste flag), plus the INSPIRE identifiers that key the plant to its site, facility, and installation. Values are carried **verbatim**. It is the plant-level view of Europe's large combustion capacity. You are billed only for records actually delivered.

### Who buys this and for what job

- **Energy, power-market, and decarbonisation teams** mapping large combustion capacity by site, type, and thermal input.
- **Waste-to-energy and circular-economy products** identifying plants with waste co-incineration capacity.
- **Environmental and infrastructure teams** joining plants to their INSPIRE-referenced sites and facilities.
- **Data engineers** who want the IED LCP register as clean rows from a keyless source.

### EEA licence — reuse with acknowledgement

One licence rider travels on every record. EEA data may be **reused, including commercially, provided the source is acknowledged**: "Source: European Environment Agency (EEA)." Where third-party content is marked, it keeps its own terms. These are register values as published — not a compliance verdict.

### Plant grain — no person data

The unit of every record is a large combustion plant — a facility, never a person. The site name is a facility/organisation name. There is no operator, contact, or responsible-person field in the source, and none is emitted; a person-key guard runs on every record as a backstop.

### Sample output

![Sample output — EU Combustion Plant Records — EEA IED LCP](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-combustion-plant-operating-hour-records.png)

*Real rows from a live run of this actor (first 5 rows, selected columns).*

One full record from the same run, exactly as delivered:

```json
{
  "record_id": "AT.CAED/9008390225387.PART",
  "site_name": "Nettingsdorfer Papierfabrik",
  "country_code": "AT",
  "installation_part_name": "Nettingsdorfer Papierfabrik AG Co KG, Sodakessel 3",
  "plant_type": "LCP",
  "total_rated_thermal_input": 98,
  "reporting_year": 2016,
  "specific_conditions": null,
  "heat_release_hazardous_waste": "False",
  "total_nominal_capacity_any_waste": null,
  "untreated_municipal_waste": "False",
  "lcp_inspire_id": "AT.CAED/9008390225387.PART",
  "installation_inspire_id": "AT.CAED/9008391292319.INSTALLATION",
  "facility_inspire_id": "AT.CAED/9008390707227.FACILITY",
  "site_inspire_id": "AT.CAED/9008390105719.SITE",
  "source": "EEA Industrial Emissions Directive (IED) — Large Combustion Plants",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) Industrial Emissions Directive (IED) — Large Combustion Plants (LCP) register. Reuse is permitted, including for commercial purposes, provided the source is acknowledged: 'Source: European Environment Agency (EEA)'. Third-party content, where marked, keeps its own terms.",
  "attribution": "Source: European Environment Agency (EEA), IED Large Combustion Plants register.",
  "disclaimer": "Large Combustion Plant (LCP) records at plant grain from the EEA IED registry: the site name (a facility/organisation), the installation-part name and plant type, the total rated thermal input, the reporting year, specific operating conditions, and waste co-incineration capacities. Plant/organisation grain — no natural-person data; there is no operator, contact, or responsible-person field in the source, and none is emitted. Values carried VERBATIM as reported.",
  "observed_at": "2026-09-25T17:32:10Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `combustion_plant_record` | $0.05 | $0.045 | $0.04 | $0.0335 |

Delivered before charged. Blocked runs and empty results cost nothing.

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `countryCode` | string | — | Optional 2-letter country code (e.g. DE, FR). |
| `plantTypeContains` | string | — | Optional. Keep only plants whose plant type contains this text. |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per plant. Real example (values as published):

```json
{
  "record_id": "AT.LCP.1",
  "site_name": "Nettingsdorfer Papierfabrik",
  "country_code": "AT",
  "installation_part_name": "LCP1",
  "plant_type": "LCP",
  "total_rated_thermal_input": 98.0,
  "reporting_year": 2019,
  "specific_conditions": "none",
  "heat_release_hazardous_waste": "No",
  "total_nominal_capacity_any_waste": 0.0,
  "untreated_municipal_waste": "No",
  "lcp_inspire_id": "AT.LCP.1",
  "facility_inspire_id": "AT.FAC.1",
  "source": "EEA Industrial Emissions Directive (IED) — Large Combustion Plants",
  "licence": "European Environment Agency (EEA) ... provided the source is acknowledged ...",
  "disclaimer": "Large Combustion Plant (LCP) records ... no operator, contact, or responsible-person field ...",
  "observed_at": "2026-08-22T00:00:00Z"
}
```

An unbilled `RUN_RECEIPT` records the robots check, the filters, rows seen and delivered, and whether charged equals delivered.

### Field reference

Each record is one plant. Identity: `record_id`, `site_name`, `installation_part_name`, and the INSPIRE identifiers (`lcp_inspire_id`, `installation_inspire_id`, `facility_inspire_id`, `site_inspire_id`). Plant: `plant_type`, `total_rated_thermal_input`, and `reporting_year`. Conditions and waste: `specific_conditions`, `heat_release_hazardous_waste`, `total_nominal_capacity_any_waste`, and `untreated_municipal_waste`. Scope: `country_code`. Provenance: `source`, `source_url`, `licence`, `attribution`, `disclaimer`, and `observed_at`.

### How a run works

A run first re-reads the source host's robots posture from your runtime — the EEA DiscoData host — and stops at the door if that ever changes. It pages the LCP register, applies your optional `countryCode` and `plantTypeContains` filters, and flattens each plant to one record — carrying the values **verbatim**, never anything person-shaped — delivered **before** it is charged, so a blocked or empty run costs you nothing. The actor stops at your `maxRecords` ceiling and records `charge_equals_delivered` in the receipt.

### Coverage and scope

The LCP register holds on the order of **32,000+ plants**. Because each record carries the `country_code`, `plant_type`, and `total_rated_thermal_input`, segmenting by country, type, or size is straightforward. Pull one country, or the whole register to seed a combustion-capacity table.

### Working with the register

The register is a capacity map, and the fields make it queryable. Because every plant carries the `total_rated_thermal_input`, an analyst can rank and band plants by size, and the `plant_type` separates classic LCPs from waste co-incinerators and other categories. The waste attributes — `heat_release_hazardous_waste`, `total_nominal_capacity_any_waste`, and `untreated_municipal_waste` — isolate plants with waste-to-energy capacity in a single filter, a signal for the circular-economy market. The INSPIRE identifiers key each plant to its site, facility, and installation, so the register joins cleanly to the fleet's other IED cells and to spatial layers.

### Identifiers and joins

Every plant carries a full set of INSPIRE identifiers — for the LCP itself, its installation, its facility, and its site — which is what makes this register a spine other datasets hang off. A buyer can attach emissions, permit conditions, BAT conclusions, or fuel-input data to a plant on a stable identifier rather than a fuzzy name match, and the `site_name` gives a human-readable anchor for QA. The `plant_type` and `total_rated_thermal_input` together let an analyst band the register by size and technology, while the waste-capacity fields flag the subset of plants that can co-incinerate waste — a distinct market segment. Because every field is carried verbatim, the register stays a faithful, joinable picture of Europe's large combustion capacity.

### Cost guidance

One `combustion_plant_record` per delivered plant: cost = plants delivered × your plan's per-record price. Scope with `countryCode` or `plantTypeContains`. The register is ~32,000 plants; 1,000 plants is **$50** (Free) / **$33.50** (Gold).

### Honest limitations

- **As published.** Values are as registered; this actor reformats, it does not audit.
- **Plant grain.** These are plant-level records; the installation-*part* combustion report is a separate fleet cell.
- **Acknowledge the EEA.** The acknowledgement travels on every record.
- **No person data** of any kind.

### Differentiation

It is distinct from the fleet's **eu-combustion-installation-part-records** (installation-*part* combustion reports — a finer grain), from **eu-industrial-emissions-records** (facility *emissions*), and from **eu-combustion-plant-fuel-input-records** (the fuel/energy input feeding these plants). Its specific job is the **IED Large Combustion Plant register at plant grain** — site, type, thermal input, and waste capacity.

### The NexGen Signal family

Part of the NexGen Signal family of pay-per-record data products:

- [EU Combustion Installation Part Records — EEA IED](https://apify.com/nexgensignal/eu-combustion-installation-part-records)
- [EU Combustion Plant Fuel Input Records — EEA IED](https://apify.com/nexgensignal/eu-combustion-plant-fuel-input-records)
- [EU Industrial Facility Report Records — EEA IED](https://apify.com/nexgensignal/eu-industrial-facility-report-records)
- [EU Industrial Emissions Records — EEA IED Facilities](https://apify.com/nexgensignal/eu-industrial-emissions-records)
- [EU Industrial BAT Conclusion Records — EEA IED](https://apify.com/nexgensignal/eu-industrial-bat-conclusion-records)

*Source: European Environment Agency (EEA), IED Large Combustion Plants register (discodata.eea.europa.eu). EEA data may be reused, including commercially, provided the source is acknowledged: "Source: European Environment Agency (EEA)"; marked third-party content keeps its own terms. Plant grain; the site name is a facility/organisation; no operator, contact, or responsible-person field, no natural-person data of any kind. Values as published, not a compliance verdict.*

# Actor input Schema

## `countryCode` (type: `string`):

Optional 2-letter country code (e.g. DE, FR).

## `plantTypeContains` (type: `string`):

Optional. Keep only plants whose plant type contains this text.

## `maxRecords` (type: `integer`):

Maximum records delivered and billed.

## Actor input object example

```json
{
  "maxRecords": 10
}
```

# Actor output Schema

## `results` (type: `string`):

Delivered records.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "maxRecords": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/eu-combustion-plant-operating-hour-records").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "maxRecords": 10 }

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/eu-combustion-plant-operating-hour-records").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "maxRecords": 10
}' |
apify call nexgensignal/eu-combustion-plant-operating-hour-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-combustion-plant-operating-hour-records"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/c9BDC9MW7iLOhDE22/builds/QvpTTvsOOh1cOfxVe/openapi.json