# EU Waterbody Pressure Source Records — EEA WISE (`nexgensignal/eu-waterbody-pressure-source-records`) Actor

Keyless pay-per-record EEA WISE WFD surface-water significant pressures — water body, ecological/chemical status, pressure type and group, as filed. Required country partition. No person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-waterbody-pressure-source-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 waterbody pressure 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 Waterbody Pressure Source Records — EEA WISE

**Keyless. Pay per record. The significant pressures attributed to each of Europe's surface water bodies — type and group, verbatim.**

This actor turns the **European Environment Agency (EEA) WISE Water Framework Directive (WFD) database** into clean, per-record data — the significant pressures attributed to Europe's surface water bodies. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per pressure attribution, 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, member states attribute the significant pressures acting on each surface water body. This actor reads that pressure table and delivers one record per water body / pressure-type / cycle: the country, river basin, and water body; its ecological and chemical status labels; and the significant PRESSURE TYPE and its group attributed to that water body — all carried as filed. It is the pressure-attribution layer of Europe's surface-water assessment.

### Who buys this and for what job

- **Catchment and river-restoration teams mapping which pressures act on which water bodies**
- **Water-management analysts quantifying pressure prevalence across basins**
- **Researchers studying pressure attribution and its link to status**
- **Data engineers** who want the WISE WFD surface-water significant-pressure 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 attribution for a surface water 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 pressure type and group; 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.

### A required partition — this is a large dataset

The table holds **859,719 rows**, so this actor **requires a partition**: every run must set a `countryCode`. The country bounds the run; there is no unbounded all-Europe pull. An optional `year` (reporting cycle) filter narrows further, and `maxRecords` is the hard ceiling.

### Pricing

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

```json
{
  "record_id": "ATOK1000010000:2.1 - Diffuse - Agricultural:2016",
  "reporting_year": 2016,
  "country_code": "AT",
  "country_name": "Austria",
  "eu_rbd_code": "AT1000",
  "rbd_name": "DANUBE",
  "eu_surface_water_body_code": "ATOK1000010000",
  "surface_water_body_name": "Example Reach",
  "ecological_status_or_potential_value": "3",
  "chemical_status_value": "2",
  "significant_pressure_type": "2.1 - Diffuse - Agricultural",
  "significant_pressure_type_group": "Diffuse",
  "source": "EEA WISE Water Framework Directive (WFD) \u2014 surface-water significant pressures",
  "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 attribution. Identity: `record_id`, `country_code`, `country_name`, `eu_rbd_code`, `rbd_name`, `eu_sub_unit_code`, `sub_unit_name`, `eu_surface_water_body_code`, `surface_water_body_name`, `surface_water_body_category`, and `reporting_year`. Status: `ecological_status_or_potential_value` and `chemical_status_value`. Pressure: `significant_pressure_type` and `significant_pressure_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 surface-water significant-pressure table (filtered to your required `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 **859,719 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.

### Working with the data

The attributions are a driver map, and the fields make them countable. Because every record pairs a `significant_pressure_type` with the body's status labels, an analyst can rank which pressures are most prevalent in a basin and correlate them with status, and the `significant_pressure_type_group` rolls the detailed types up to families (diffuse, point, hydromorphology). The `reporting_year` tracks change between cycles.

### Identifiers and joins

Every record carries the `eu_surface_water_body_code`, keying each pressure attribution to the fleet's failing-pollutant, exemption, and priority-substance cells for the same body, on a shared identifier.

### Cost guidance

One `waterbody_pressure_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

This is a **net-new** category for the NexGenData fleet. It is distinct from **eu-pressure-substance-failure-records** — that cell is the river-basin PRESSURE-to-failing-SUBSTANCE crosswalk, while this cell attributes significant PRESSURES to individual WATER BODIES; water-body pressure attribution vs pressure-substance crosswalk. Its specific job is the **WFD surface-water significant-pressure attributions**.

### 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. Water-body / pressure-type / 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`):

REQUIRED 2-letter country code (e.g. DE, FR) — this table is large and cannot be pulled unbounded.

## `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
{
  "countryCode": "DE",
  "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 = {
    "countryCode": "DE",
    "maxRecords": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/eu-waterbody-pressure-source-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 = {
    "countryCode": "DE",
    "maxRecords": 500,
}

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

```

## MCP server setup

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