# EU Modified Waterbody Use Records — EEA WISE (`nexgensignal/eu-modified-waterbody-use-records`) Actor

Keyless pay-per-record EEA WISE WFD heavily-modified water body water uses — water body, water use, designation and ecological/chemical status, as filed. Water-body grain, no person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-modified-waterbody-use-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 modified-waterbody use 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 Modified Waterbody Use Records — EEA WISE

**Keyless. Pay per record. The water uses behind Europe's heavily modified water bodies.**

This actor turns the **European Environment Agency (EEA) WISE Water Framework Directive (WFD) database** into clean, per-record data — the water USES that member states cite to designate a surface water as HEAVILY MODIFIED. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per use, structured for water-management and economic analysis, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

A water body is designated heavily modified because a specific water USE — navigation, hydropower, flood protection, drinking-water storage, and the like — depends on the physical changes that keep it from good status. This actor reads that water-use table and delivers one record per entry: the country, river basin district and sub-unit, the surface water body (code, name, category), the natural/artificial/heavily-modified designation, the WATER USE, and the body's ecological and chemical status — all carried as filed. It is the use-justification layer behind Europe's heavily-modified designations, the sibling of the alteration cell.

### Who buys this and for what job

- **Navigation, hydropower and water-supply analysts** mapping which uses drive modified-water designations.
- **Economic and policy teams** weighing the uses cited against restoration options.
- **Water-policy researchers** studying how use-based justification varies by country.
- **Data engineers** who want the WISE WFD heavily-modified use 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 classifications as filed — not a compliance verdict.

### Water-body grain — no person data

The unit of every record is a water use for a surface water body — a water body and a coded use, never a person. WISE WFD reporting is at water-body level: there is **no contact, operator, or responsible-person field** in the source table, and none is selected or emitted. The free-text "other pressure / other impact" narrative fields are **EXCLUDED at field selection**. A person-key guard runs on every record as a backstop.

### A note on scale, honestly

The source table holds **49,581 rows**; this actor delivers the rows that carry an actual water use — an exact `COUNT(*)` of **48,327** at build time, which matches the planning index for this category exactly. It carries both the 2016 and 2022 WFD reporting cycles (the `reporting_year` field distinguishes them). The live count above is authoritative.

### Sample output

![Sample output — EU Modified Waterbody Use Records — EEA WISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-modified-waterbody-use-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": "ATOK100020003:Energy - hydropower:2016",
  "reporting_year": 2016,
  "country_code": "AT",
  "country_name": "Austria",
  "eu_rbd_code": "AT2000",
  "rbd_name": "RHINE",
  "eu_sub_unit_code": "AT2100",
  "sub_unit_name": "RHINE",
  "eu_surface_water_body_code": "ATOK100020003",
  "surface_water_body_name": "NO INTERNATIONAL NAME",
  "surface_water_body_category": "RW",
  "natural_awb_hmwb": "Heavily modified water body",
  "water_use": "Energy - hydropower",
  "sw_ecological_status_value": "3",
  "sw_chemical_status_value": "3",
  "surface_water_body_transboundary": "No",
  "has_descriptive_data": 1,
  "file_url": "http://cdr.eionet.europa.eu/at/eu/wfd2016/districts/at2000/envwvtbw/SWB_AT_20170509.xml",
  "source": "EEA WISE Water Framework Directive (WFD) — heavily modified water body water uses",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) WISE database under EU environmental reporting. 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 (discodata.eea.europa.eu).",
  "disclaimer": "Water USES supporting the designation of European surface waters as HEAVILY MODIFIED, at water-body / use grain from the EEA WISE WFD database (rows filtered to those carrying a recorded use). Each record carries the country, river basin district and sub-unit, the surface water body (code, name, category), the natural/AWB/HMWB designation, the WATER USE, and the body's ecological and chemical status labels VERBATIM. The free-text 'other pressure/impact' narrative fields are EXCLUDED at field selection. Water-body grain — no contact, operator, or responsible-person field is selected or emitted, and a person-key guard runs on every record.",
  "observed_at": "2026-09-25T17:33:26Z"
}
```

### Pricing

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

### Output

One JSON object per water use. Representative example (values as reported):

```json
{
  "record_id": "DERW0001:Navigation, ports or recreation:2022",
  "reporting_year": 2022,
  "country_code": "DE",
  "eu_rbd_code": "DE1000",
  "rbd_name": "RHINE",
  "eu_surface_water_body_code": "DERW0001",
  "surface_water_body_category": "River",
  "natural_awb_hmwb": "Heavily modified water body",
  "water_use": "Navigation, ports or recreation",
  "sw_ecological_status_value": "3",
  "sw_chemical_status_value": "2",
  "source": "EEA WISE Water Framework Directive (WFD) — heavily modified water body water uses",
  "observed_at": "2026-08-27T00: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 water use. 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`. Designation and use: `natural_awb_hmwb` and `water_use`. Status: `sw_ecological_status_value`, `sw_chemical_status_value`, and `surface_water_body_transboundary`. 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 WFD heavily-modified use table (always keeping only rows with a real water use, plus your optional `countryCode` and `year`), ordered by the high-cardinality water-body code, and flattens each row to one record — carrying every coded label **verbatim**, never anything person-shaped and never the free-text narrative — 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 **48,327 rows** across reporting countries, river basin districts, water uses, and the 2016 and 2022 cycles. Because each record carries the `country_code`, the water-body code, the `water_use`, and the `reporting_year`, segmenting by country, basin, use or cycle is straightforward. Pull one country, one water use, or the whole table to seed a water-status warehouse.

### Working with the data

The uses are an economic-justification layer, and the fields make them actionable. Because every record pairs a water body with a `water_use` and its ecological status, an analyst can rank the uses most often cited for modified designations, and — joined to the paired **eu-modified-waterbody-alteration-records** on the water-body code — line each water use up against the physical alteration that serves it.

### Cost guidance

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

### Honest limitations

- **As reported.** Uses and status are as filed by member states; this actor reformats, it does not audit or recompute.
- **Filtered to recorded uses.** Water bodies with no recorded use are excluded by design; the full table is larger.
- **Two cycles merged.** The `reporting_year` field distinguishes the 2016 and 2022 cycles.
- **Acknowledge the EEA**, and note there is **no person data** of any kind.

### Differentiation

It is the USE half of the heavily-modified-designation evidence — a distinct source table from its paired sibling **eu-modified-waterbody-alteration-records** (the physical alterations), proven independently by count, and different from the surface-water status, pressure and impact cells. Its specific job is the **WFD heavily-modified water uses**.

### The NexGen Signal family

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

- [EU Surface Water Priority Substance Records — EEA](https://apify.com/nexgensignal/eu-surface-water-priority-substance-records)
- [EU Pressure Substance Failure Records — EEA](https://apify.com/nexgensignal/eu-pressure-substance-failure-records)
- [EU River Basin Measure Inventory Records — EEA](https://apify.com/nexgensignal/eu-river-basin-measure-inventory-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 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 grain; no contact, operator, or responsible-person field is selected or emitted, no natural-person data of any kind. Reported classifications as filed for the WFD reporting cycle, not a compliance verdict.*

# Actor input Schema

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

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

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

Optional WFD reporting cycle year (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-modified-waterbody-use-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-modified-waterbody-use-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-modified-waterbody-use-records --silent --output-dataset

```

## MCP server setup

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