# EU Quality Element Exemption Records — EEA WISE (`nexgensignal/eu-quality-element-exemption-records`) Actor

Keyless pay-per-record EEA WISE WFD quality-element ecological exemptions — water body, quality element (code/status/monitoring), exemption type and group, as filed. Finer than exemption-type grain. No person data. Gold $0.0335/record.

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

## Pricing

from $33.50 / 1,000 quality element exemption 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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## EU Quality Element Exemption Records — EEA WISE

**Keyless. Pay per record. Ecological exemptions at quality-element grain — per element, per water body, with assessment context.**

This actor turns the **European Environment Agency (EEA) WISE Water Framework Directive (WFD) database** into clean, per-record data — the ecological-status exemptions of Europe's surface waters at the finer quality-element grain. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per quality-element exemption row, structured for water-status and river-restoration analysis, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

Under the Water Framework Directive, ecological exemptions can be reported per QUALITY ELEMENT (the biological, hydromorphological, and physico-chemical components that make up ecological status). This actor reads that per-element table and delivers one record per element-level exemption: the country, river basin, and water body; the water body's overall ecological status; the quality element (its code, status, monitoring results, and period); and the ecological exemption TYPE and TYPE GROUP for that element — all carried as filed. It is the finest grain of Europe's ecological-exemption reporting.

### Who buys this and for what job

- **Water-status analysts drilling into which quality elements drive ecological exemptions**
- **River-restoration teams targeting the specific elements under exemption in a water body**
- **Researchers studying exemption use at biological/hydromorphological/physico-chemical element level**
- **Data engineers** who want the WISE WFD quality-element exemption table 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 reported values as filed — not a compliance verdict.

### Water-body grain — no person data

The unit of every record is a quality-element-level ecological exemption for a water body — an assessment line, never a person. There is no contact, operator, or responsible-person field in the source, and none is selected or emitted; a person-key guard runs on every record as a backstop. The `file_url` points to the official Eionet/CDR reporting file.

### A note on scale, honestly

This actor delivers the rows of the quality-element ecological-exemption table where a quality-element exemption is actually present (`qeEcologicalExemptionType != 'None'`) — **582,116 rows** as verified by an exact `COUNT(*)` at build time, matching the index exactly. The full table is far larger and mostly 'None'; the filter keeps every record an actual exemption.

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `qe_exemption_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). |
| `year` | integer | — | Optional reporting cycle year to filter. |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per quality-element exemption row. Real example (values as reported):

```json
{
  "record_id": "FRSW001:QE1-1-1:Article 4(4) - Technical feasibility:2022",
  "reporting_year": 2022,
  "country_code": "FR",
  "country_name": "France",
  "eu_rbd_code": "FR1000",
  "rbd_name": "SEINE",
  "eu_surface_water_body_code": "FRSW001",
  "surface_water_body_name": "Example River",
  "surface_water_body_category": "RW",
  "ecological_status_or_potential_value": "3",
  "qe_code": "QE1-1-1",
  "qe_status_or_potential_value": "3",
  "qe_ecological_exemption_type": "Article 4(4) - Technical feasibility",
  "source": "EEA WISE Water Framework Directive (WFD) \u2014 quality-element ecological exemptions",
  "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 element-level exemption. Identity: `record_id`, `country_code`, `country_name`, `eu_rbd_code`, `rbd_name`, `eu_surface_water_body_code`, `surface_water_body_name`, `surface_water_body_category`, and `reporting_year`. Element: `ecological_status_or_potential_value`, `qe_code`, `qe_status_or_potential_value`, `qe_monitoring_results`, `qe_monitoring_period`, and `qe_status_or_potential_change`. Exemption: `qe_ecological_exemption_type` and `qe_ecological_exemption_type_group`. Plus `file_url`. Provenance travels on every record: `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 WISE WFD quality-element exemption table (rows where a quality-element exemption is present), and flattens each row to one record — carrying every value **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 table holds on the order of **582,116 rows**. Because each record carries the `qe_code`, `qe_ecological_exemption_type`, and water-body identity, segmenting is straightforward. Pull one slice, or the whole table to seed a warehouse.

### Working with the data

The element-level exemptions are a diagnostic layer, and the fields make them precise. Because every record pairs a `qe_code` with a `qe_ecological_exemption_type` and the element's own status and monitoring results, an analyst can see exactly which quality elements are under exemption in a water body and why, a finer view than water-body-level exemption reporting. The `reporting_year` tracks change between cycles.

### Cross-cycle and element structure

Because the quality-element code (`qe_code`) follows the WFD's structured element taxonomy — biological, hydromorphological, and physico-chemical groups — a buyer can roll element-level exemptions up to their groups or drill down to a single element, and because two reporting cycles share the schema, the same element in the same water body can be compared across 2016 and 2022 to see whether an exemption was newly claimed, carried over, or dropped.

### Identifiers and joins

Every record carries the `eu_surface_water_body_code`, keying each element-level exemption back to the fleet's water-body-level ecological and chemical exemption cells and the water-body status cell, so a buyer can move between the per-element detail and the water-body summary on a shared identifier.

### Cost guidance

One `qe_exemption_record` per delivered row: cost = rows delivered × your plan's per-record price. Scope with `countryCode` and `year` to keep runs bounded. 1,000 rows is **$50** (Free) / **$33.50** (Gold).

### Honest limitations

- **As reported.** Values, flags, and status labels are as filed; this actor reformats, it does not audit or recompute.
- **A label, not a verdict.** These are reported classifications/schedules/linkages, not an independent compliance assessment.
- **Acknowledge the EEA.** The acknowledgement travels on every record.
- **No person data** of any kind.

### Differentiation

This is a **net-new** category for the NexGenData fleet. It is distinct from **eu-surface-water-ecological-exemption-records** — that cell reports exemptions at exemption-TYPE grain (per water body), while this cell reports at QUALITY-ELEMENT grain (per element within a water body), a finer resolution with the element's own status and monitoring context. Its specific job is the **WFD quality-element ecological exemptions**.

### The NexGen Signal family

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

- [EU Water Monitoring Parameter Schedule Records — EEA WISE](https://apify.com/nexgensignal/eu-water-monitoring-parameter-schedule-records)
- [EU Surface Water Ecological Exemption Records — EEA WISE](https://apify.com/nexgensignal/eu-surface-water-ecological-exemption-records)
- [EU Waterbody Pesticide Exceedance Records — EEA WISE](https://apify.com/nexgensignal/eu-waterbody-pesticide-exceedance-records)
- [EU Waterbody Quality Records — EEA](https://apify.com/nexgensignal/eu-waterbody-quality-records)
- [EU Nitrate Monitoring Records — EEA](https://apify.com/nexgensignal/eu-nitrate-monitoring-records)

*Source: European Environment Agency (EEA), WISE (Water Information System for Europe) (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. Water-body / quality-element / exemption grain; no contact/operator/responsible-person field selected or emitted. No natural-person data of any kind. Values as filed, not a compliance verdict.*

# Actor input Schema

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

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

## `year` (type: `integer`):

Optional reporting cycle year to filter.

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

Maximum records delivered and billed.

## Actor input object example

```json
{
  "maxRecords": 500
}
```

# 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": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/eu-quality-element-exemption-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": 500 }

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/eu-quality-element-exemption-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": 500
}' |
apify call nexgensignal/eu-quality-element-exemption-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-quality-element-exemption-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/cDfMoEoiaNi0ZdRjr/builds/9ozBdboSftoTlRpQa/openapi.json