EU Stricter Permit Condition Records — EEA IED

Keyless. Pay per record. Which European industrial installations are held to permit conditions stricter than BAT — and on what legal basis.

This actor turns the European Environment Agency (EEA) Industrial Emissions Directive (IED) registry into clean, per-installation records — the installations operating under stricter-than-BAT permit conditions, and the legal basis for those conditions. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per stricter-condition entry: the installation id, the stricter-condition indicator, and the legal basis (BAT-AEL, Article 14(4), Article 18), plus the installation's facility name, country, and main IED activity. Facility / exception-basis 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 lets member states impose permit conditions stricter than the emission levels associated with Best Available Techniques — for example under Article 14(4) or Article 18, or via a stricter BAT-AEL. The registry records which installations carry such conditions and on what basis, and this actor extracts exactly that: it reads the stricter-permit-conditions table and joins each row to the installation's identity, delivering the installation id, the stricter-condition indicator, the BAT-AEL / Article 14(4) / Article 18 basis flags, and the installation's facility name (an organisation, suppressed where the source flags the name confidential), its country, main IED Annex I activity, and status. Conditions are carried as filed — this actor reports the basis, never a compliance verdict. You are billed only for records actually delivered.

Who buys this and for what job

• Environmental-permitting, compliance, and consultancy teams identifying installations under stricter-than-BAT regimes and the basis for them.
• Industrial-intelligence and ESG products flagging the most tightly regulated facilities by country and sector.
• Researchers and regulators' data teams studying how member states apply stricter-condition provisions.
• Data engineers who want the stricter-permit 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. Permit conditions are reported as filed — not a compliance judgment.

Installation grain — no person data

The unit of every record is an installation and its stricter-condition basis — an organisation, never a person. The installation name is a facility name, suppressed where the source marks it confidential. 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

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

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

{
  "record_id": "14896:14657",
  "installation_id": "14896",
  "stricter_permit_conditions_indicator": "False",
  "batael": null,
  "article_14_4": "False",
  "article_18": "False",
  "installation_name": "Alur álvinnsla",
  "country_code": "IS",
  "ied_annex_i_main_activity": "2.5(a)",
  "installation_status": "functional",
  "reporting_year": "2018",
  "control_file_id": "48",
  "source": "EEA Industrial Emissions Directive (IED) registry",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) Industrial Emissions Directive (IED) registry — installations under stricter-than-BAT permit conditions. 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), Industrial Emissions Directive (IED) registry.",
  "disclaimer": "Records of IED production installations under STRICTER-THAN-BAT permit conditions, at facility / exception-basis grain from the EEA IED registry. Each record carries the stricter-condition indicator and the legal basis (BAT-AEL, Article 14(4), Article 18) with the installation's FACILITY name (an organisation, suppressed where the source flags the name confidential), country, and main IED activity. Installation/organisation grain — no natural-person data. Permit conditions are carried as filed, never a compliance verdict.",
  "observed_at": "2026-09-25T17:34:21Z"
}

Pricing

Event	Free plan	Bronze	Silver	Gold / Platinum / Diamond
permit_condition_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 to filter (e.g. DE, FR, IT).
maxRecords	integer	500	Ceiling on records delivered and billed.

Output

One JSON object per stricter-condition entry. Real example (values as published):

{
  "record_id": "14896:31",
  "installation_id": "14896",
  "stricter_permit_conditions_indicator": "True",
  "batael": "stricter",
  "article_14_4": "Yes",
  "article_18": null,
  "installation_name": "Alur álvinnsla",
  "country_code": "IS",
  "ied_annex_i_main_activity": "2.5",
  "installation_status": "functional",
  "control_file_id": "55",
  "source": "EEA Industrial Emissions Directive (IED) registry",
  "licence": "European Environment Agency (EEA) ... provided the source is acknowledged ...",
  "disclaimer": "Records of IED production installations under STRICTER-THAN-BAT permit conditions ... as filed ...",
  "observed_at": "2026-08-22T00:00:00Z"
}

An unbilled RUN_RECEIPT records the robots check, the filter, rows matched and delivered, and whether charged equals delivered.

Field reference

Each record is one stricter-condition entry. Keys: record_id, installation_id. Basis: stricter_permit_conditions_indicator, batael, article_14_4, and article_18. Installation identity: installation_name (facility/org, confidentiality-suppressed), country_code, ied_annex_i_main_activity, installation_status, and reporting_year. Provenance: control_file_id, 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 stricter-permit-conditions table, enriches each row with the installation's identity (suppressing the facility name where confidential), applies your optional countryCode filter, and flattens each entry to one record — carrying the condition basis as filed, 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 stricter-permit-conditions table holds on the order of 472,000+ rows. Because each record carries the country_code, ied_annex_i_main_activity, and the basis flags, segmenting by country, sector, or legal basis is straightforward. Pull one country, or the whole table to seed a stricter-regime map.

Working with the register

The register answers "who is held to more than BAT, and why," and the basis flags make that a filter. Because every record carries the stricter_permit_conditions_indicator alongside the article_14_4, article_18, and batael fields, an analyst can isolate installations under a specific provision, and the ied_annex_i_main_activity groups them by sector. The installation_name and country_code anchor each row, and because the basis is carried as filed, the register joins cleanly to the fleet's BAT-conclusion and emissions cells for a fuller regulatory picture. Two pulls can be diffed to see where stricter conditions were newly applied.

Installation enrichment and confidentiality

Each linkage row in the source carries only an internal installation id; on its own that id is opaque. This actor enriches every record from the IED installation register, adding the installation's facility name, country, main IED Annex I activity, status, and reporting year, so a buyer sees which real facility each row refers to without running a second query. The enrichment is done in bounded, cached batches so a large pull stays efficient. One rule is enforced throughout: where the source flags an installation's name as confidential, the name is suppressed and only the non-name identity (country, activity, status) is carried — the linkage still resolves on the identifiers, but a withheld name is never revealed. This keeps the records both useful and faithful to the source's own confidentiality decisions.

Cost guidance

One permit_condition_record per delivered entry: cost = entries delivered × your plan's per-record price. Scope with countryCode to keep runs bounded. The table is ~472,000 rows; 1,000 rows is $50 (Free) / $33.50 (Gold).

Honest limitations

• As filed, not a verdict. These are the registry's own stricter-condition entries, carried as reported.
• Name may be withheld. Where the source marks the installation name confidential, it is suppressed; the identifiers still resolve.
• Acknowledge the EEA. The acknowledgement travels on every record.
• No person data of any kind.

Differentiation

It is distinct from the fleet's eu-industrial-emissions-records (IED facility emissions) — this cell carries the stricter-than-BAT permit-condition basis, a different table for a different job. It is the permit-condition member of a five-cell EEA industrial/water family (BAT conclusions, ETS linkage, offsite transfers, pesticide monitoring).

The NexGen Signal family

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

• EU Industrial BAT Conclusion Records — EEA IED
• EU Industrial ETS Linkage Records — EEA IED
• EU Offsite Pollutant Transfer Records — EEA E-PRTR
• EU Industrial Emissions Records — EEA IED Facilities
• EU Pesticide Water Monitoring Records — EEA WISE

Source: European Environment Agency (EEA), Industrial Emissions Directive (IED) registry (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. Facility / exception-basis grain; installation (facility/organisation) identity only, name suppressed where confidential; no natural-person data of any kind. Permit conditions as filed, not a compliance verdict.