# EU Groundwater Pollutant Failure Records — EEA WISE (`nexgensignal/eu-groundwater-pollutant-failure-records`) Actor

Keyless pay-per-record EEA WISE WFD groundwater pollutant assessments — groundwater body, pollutant, chemical status, causing-risk/failure and trend flags, verbatim. No person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-groundwater-pollutant-failure-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 gw pollutant failure 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 Groundwater Pollutant Failure Records — EEA WISE

**Keyless. Pay per record. Every pollutant assessed against Europe's groundwater bodies — status, risk, and failure flags, verbatim.**

This actor turns the **European Environment Agency (EEA) WISE Water Framework Directive (WFD) database** into clean, per-record data — the pollutant-level chemical assessments of Europe's groundwater bodies. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per pollutant assessment, structured for water-status and catchment 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, each groundwater body is assessed pollutant by pollutant for chemical status. This actor reads that pollutant-assessment table and delivers one record per groundwater body / pollutant / cycle: the country and river basin, the groundwater body, the chemical status value, assessment year and confidence, the pollutant, and the flags for whether it is causing risk or FAILURE, its upward trend and trend reversal, and its background level — all carried as filed. It is the pollutant-failure layer beneath Europe's groundwater chemical status.

### Who buys this and for what job

- **Groundwater analysts identifying which pollutants drive chemical-status failures by body**
- **Regulatory and catchment teams tracking the substances behind groundwater failures**
- **Researchers analysing groundwater pollutant risk and trends across basins**
- **Data engineers** who want the WISE WFD groundwater pollutant assessment 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 and status labels as filed — not a compliance verdict.

### Water-body grain — no person data

The unit of every record is a pollutant assessment for a groundwater body — a water body and its reported attributes, never a person. WISE reporting is at water-body / river-basin level: there is **no contact, operator, or responsible-person field** in the source table, and none is selected or emitted — the query reads only the water-body identity, the status/flags, and the pollutant, status, and risk/failure flags; the free-text 'other' pressure and impact narrative fields are excluded at field selection. A person-key guard runs on every record as a backstop. The `file_url` points to the official Eionet/CDR reporting file, never a person.

### Sample output

![Sample output — EU Groundwater Pollutant Failure Records — EEA WISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-groundwater-pollutant-failure-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": ":None:2010",
  "reporting_year": 2010,
  "country_code": "BE",
  "country_name": "Belgium",
  "eu_rbd_code": "BENOORDZEE_FED",
  "rbd_name": "BELGIAN COAST",
  "eu_groundwater_body_code": null,
  "groundwater_body_name": null,
  "chemical_status_value": null,
  "chemical_assessment_year": null,
  "chemical_assessment_confidence": null,
  "at_risk_chemical": null,
  "expected_to_be_at_risk_chemical": null,
  "quantitative_status_value": null,
  "pollutant_code": "None",
  "pollutant_other": null,
  "pollutant_causing_risk": "Unpopulated",
  "pollutant_causing_failure": "Unpopulated",
  "pollutant_upward_trend": "Unpopulated",
  "pollutant_trend_reversal": "Unpopulated",
  "pollutant_background_level_value": "unpopulated",
  "pollutant_background_level_unit": "unpopulated",
  "file_url": null,
  "source": "EEA WISE Water Framework Directive (WFD) — groundwater pollutant assessments",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) WISE Water Framework Directive (WFD) database — groundwater pollutant assessments. 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), WISE Water Framework Directive (WFD) database.",
  "disclaimer": "Groundwater pollutant assessments at groundwater-body / pollutant / reporting-cycle grain from the EEA WISE Water Framework Directive database. Each record names a groundwater body, the pollutant, the chemical STATUS LABEL carried VERBATIM (never a compliance verdict), the assessment year and confidence, and flags for whether the pollutant is causing risk or FAILURE and its trend. Water-body grain — there is no contact, operator, or responsible-person field in the source, and none is selected or emitted (free-text 'other' pressure/impact fields excluded at field selection); a person-key guard runs on every record as a backstop.",
  "observed_at": "2026-09-25T17:32:13Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `gw_pollutant_failure_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 (e.g. 2016, 2022). |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per pollutant assessment. Real example (values as reported):

```json
{
  "record_id": "ATGK100001:Nitrate:2016",
  "reporting_year": 2016,
  "country_code": "AT",
  "country_name": "Austria",
  "eu_rbd_code": "AT1000",
  "rbd_name": "DANUBE",
  "eu_groundwater_body_code": "ATGK100001",
  "groundwater_body_name": "Example GW Body",
  "chemical_status_value": "2",
  "pollutant_code": "Nitrate",
  "pollutant_causing_failure": "Yes",
  "source": "EEA WISE Water Framework Directive (WFD) \u2014 groundwater pollutant assessments",
  "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 pollutant assessment. Identity: `record_id`, `country_code`, `country_name`, `eu_rbd_code`, `rbd_name`, `eu_groundwater_body_code`, `groundwater_body_name`, and `reporting_year`. Status: `chemical_status_value`, `chemical_assessment_year`, `chemical_assessment_confidence`, `at_risk_chemical`, `expected_to_be_at_risk_chemical`, and `quantitative_status_value`. Pollutant: `pollutant_code`, `pollutant_other`, `pollutant_causing_risk`, `pollutant_causing_failure`, `pollutant_upward_trend`, `pollutant_trend_reversal`, `pollutant_background_level_value`, and `pollutant_background_level_unit`. 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 groundwater pollutant assessment table (filtered to your optional `countryCode` and optional `year`), and flattens each row to one record — carrying every status label and 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 **439,344 rows** across reporting countries, river basin districts, and the 2016 and 2022 WFD reporting cycles. Because each record carries the `country_code`, the water-body identity, and the `reporting_year`, segmenting by country, basin, or cycle is straightforward. Pull one country, or the whole table to seed a water-status warehouse.

### Risk versus failure

The directive distinguishes a pollutant that puts a body *at risk* of failing from one actually *causing failure*, and both are reported. Carrying `pollutant_causing_risk` and `pollutant_causing_failure` as separate flags lets an analyst separate the current failures from the emerging risks — the pollutants a basin should watch before they tip a body over — and the `at_risk_chemical` and `expected_to_be_at_risk_chemical` body-level flags frame each pollutant against the body's overall trajectory. The background-level value and unit add the reference against which an exceedance was judged.

### Working with the data

The assessments are a diagnostic layer, and the fields make them queryable. Because every record pairs a `pollutant_code` with `pollutant_causing_failure` and the body's `chemical_status_value`, an analyst can rank which pollutants drive the most groundwater failures in a basin, and the trend flags surface where a pollutant is rising or reversing. The `reporting_year` lets the 2016 and 2022 cycles be compared.

### Identifiers and joins

Every record carries the `eu_groundwater_body_code`, keying each pollutant assessment to the fleet's groundwater exemption, threshold-value, and surface-water-linkage cells for the same body, on a shared identifier rather than a fuzzy name match.

### Cost guidance

One `gw_pollutant_failure_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.** Status labels, reasons, and values are as filed by member states for the WFD reporting cycle; this actor reformats, it does not audit or recompute.
- **A label, not a verdict.** These are reported classifications, assessments, and reasons, not an independent compliance assessment.
- **Two cycles merged.** The table carries both the 2016 and 2022 reporting cycles; the `reporting_year` field distinguishes them.
- **Acknowledge the EEA.** The acknowledgement travels on every record.
- **No person data** of any kind.

### Differentiation

It is distinct from **eu-groundwater-chemical-exemption-records** — that cell records the EXEMPTIONS claimed for a pollutant, while this cell records the failure ASSESSMENT (which pollutant is causing risk or failure and its status). Its specific job is the **WFD groundwater pollutant assessments**.

### The NexGen Signal family

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

- [EU Groundwater Chemical Exemption Records — EEA WISE](https://apify.com/nexgensignal/eu-groundwater-chemical-exemption-records)
- [EU Surface Water Chemical Exemption Records — EEA WISE](https://apify.com/nexgensignal/eu-surface-water-chemical-exemption-records)
- [EU Pressure Substance Failure Records — EEA WISE](https://apify.com/nexgensignal/eu-pressure-substance-failure-records)
- [EU Surface Water Failing Pollutant Records — EEA WISE](https://apify.com/nexgensignal/eu-surface-water-failing-pollutant-records)
- [EU Waterbody Quality Records — EEA](https://apify.com/nexgensignal/eu-waterbody-quality-records)

*Source: European Environment Agency (EEA), WISE Water Framework Directive (WFD) database (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. Groundwater-body / pollutant / cycle grain; no contact/operator/responsible-person field selected or emitted, free-text 'other' narrative excluded. No natural-person data of any kind. Values and status labels 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 (e.g. 2016, 2022).

## `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-groundwater-pollutant-failure-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-groundwater-pollutant-failure-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-groundwater-pollutant-failure-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-groundwater-pollutant-failure-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/xhYr4UslAVvpPfm67/builds/3kVyEXw2ZsVU9evwm/openapi.json