# EU Pressure Substance Failure Records — EEA WISE (`nexgensignal/eu-pressure-substance-failure-records`) Actor

Keyless pay-per-record EEA WISE WFD crosswalk of significant pressures to failing substances — river basin, pressure, substance, water/groundwater, as filed. Water-body grain, no person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-pressure-substance-failure-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 pressure substance 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?

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 Pressure Substance Failure Records — EEA WISE

**Keyless. Pay per record. The crosswalk of significant pressures to the substances failing Europe's water objectives.**

This actor turns the **European Environment Agency (EEA) WISE (Water Information System for Europe)** into clean, per-record data — the crosswalk between significant pressure types and the substances recorded as failing water objectives across Europe's river basins. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per pressure-substance record, structured for environmental and water-management 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 programme-of-measures reporting, member states record which significant pressures are linked to which substances failing to meet water objectives. This actor reads that crosswalk table and delivers one record per pressure-substance pairing: the country and river basin district, whether the pairing concerns surface water or groundwater, the significant pressure, the substance failing (and any 'other' free-text substance), and a flag for whether Article 4(5) is used beyond 2027 — carried as filed. It is the pressure-to-failure crosswalk beneath Europe's water objectives.

### Who buys this and for what job

- **Catchment and river-basin managers linking failing substances to the pressures that drive them**
- **Environmental policy researchers analysing pressure–substance relationships across basins**
- **ESG and water-risk products mapping which pressures threaten which water objectives**
- **Data engineers** who want the WISE pressure-substance 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 significant-pressure to failing-substance pairing — a water body or river basin 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 pressure, failing substance, and Article 4(5) flag. A person-key guard runs on every record as a backstop. The `file_url`, where present, points to the official EEA/Eionet reporting file (an organisation reporting system), never a person.

### A note on scale, honestly

The source table (`RBMPPoM_PoM_SignificantPressureSubstanceFailing`) holds **10,148 rows** as verified by an exact `COUNT(*)` at build time — the real, populated crosswalk table, carrying the 2016 and 2022 reporting cycles. This is the authoritative live count.

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `pressure_substance_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 pressure-substance record. Real example (values as reported):

```json
{
  "record_id": "AT1000:Diffuse - Agriculture:Nitrate:2022",
  "reporting_year": 2022,
  "country_code": "AT",
  "country_name": "Austria",
  "eu_rbd_code": "AT1000",
  "rbd_name": "DANUBE",
  "surface_water_or_groundwater": "groundwater",
  "significant_pressure": "Diffuse - Agriculture",
  "substance_failing": "Nitrate",
  "use_article_45_beyond_2027": "No",
  "source": "EEA WISE Water Framework Directive (WFD) \u2014 significant pressure to failing substance crosswalk",
  "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 pressure-substance pairing. Identity: `record_id`, `country_code`, `country_name`, `eu_rbd_code`, `rbd_name`, `eu_sub_unit_code`, `sub_unit_name`, and `reporting_year`. Crosswalk: `surface_water_or_groundwater`, `significant_pressure`, `substance_failing`, `other_substance_failing`, and `use_article_45_beyond_2027`. Plus `has_descriptive_data` and `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 pressure-substance table (filtered to your optional `countryCode` and `year`), and flattens each row to one record — carrying every value and flag **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 **10,148 rows**. Because each record carries the `country_code`, the water-body identity, and the `significant_pressure` and `substance_failing`, segmenting by country, basin, or year is straightforward. Pull one country, or the whole table to seed a water-analysis warehouse.

### Identifiers and joins

Every record carries the `eu_rbd_code`, keying each pressure-substance pairing back to the fleet's other WISE cells for that river basin — the failing pollutants, the exemptions, and the river-basin-specific standards — so a buyer can line up which pressures drive which failures against the standards and exemptions reported for the same basin, on a shared identifier rather than a fuzzy name match.

### Working with the data

The crosswalk is a causal map, and the fields make it queryable. Because every record pairs a `significant_pressure` with a `substance_failing`, an analyst can count which pressures are most often linked to a given failing substance across a country or basin in a single group-by, and the `surface_water_or_groundwater` split keeps the two water categories separable. The `reporting_year` lets the 2016 and 2022 cycles be compared to see how the pressure–failure picture shifted.

### Cost guidance

One `pressure_substance_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 by member states; this actor reformats, it does not audit or recompute.
- **A label, not a verdict.** These are reported classifications, standards, exceedances, or linkages, not an independent compliance or hazard 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 the fleet's exemption and status cells — this cell is the PRESSURE-to-failing-SUBSTANCE crosswalk (which pressures drive which substance failures), not a status classification or an exemption. It differs entirely from the Nitrates, Bathing Water, and Urban Waste Water directive cells. Its specific job is the **WFD significant-pressure to failing-substance crosswalk**.

### The NexGen Signal family

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

- [EU Surface Water Failing Pollutant Records — EEA WISE](https://apify.com/nexgensignal/eu-surface-water-failing-pollutant-records)
- [EU Groundwater Threshold Value Records — EEA WISE](https://apify.com/nexgensignal/eu-groundwater-threshold-value-records)
- [EU Surface Water Chemical Exemption Records — EEA WISE](https://apify.com/nexgensignal/eu-surface-water-chemical-exemption-records)
- [EU Pesticide Water Monitoring Records — EEA](https://apify.com/nexgensignal/eu-pesticide-water-monitoring-records)
- [EU Waterbody Quality Records — EEA](https://apify.com/nexgensignal/eu-waterbody-quality-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 / river-basin grain; no contact, operator, or responsible-person field is selected or emitted, 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.

## `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-pressure-substance-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": 500 }

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

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-pressure-substance-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/yhr5lHRhn5U1Tqf4h/builds/YN2AzsC8WvMVQySg9/openapi.json