# EU River Basin Measure Inventory Records — EEA WISE (`nexgensignal/eu-river-basin-measure-inventory-records`) Actor

Keyless pay-per-record EEA WISE WFD river-basin Programme of Measures — Key Type Measure, measure code, basic/supplementary type and MSFD relevance, as filed. River-basin grain, no person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-river-basin-measure-inventory-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 river-basin measure 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 River Basin Measure Inventory Records — EEA WISE

**Keyless. Pay per record. Every coded intervention in Europe's river-basin Programmes of Measures.**

This actor turns the **European Environment Agency (EEA) WISE Water Framework Directive (WFD) database** into clean, per-record data — the coded measures that member states put in place to restore their river basins, as reported in the Programme of Measures. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per measure, structured for environmental and water-policy 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, every river basin district reports a Programme of Measures — the interventions it will take to reach good water status, each classified against a standard list of Key Type Measures. This actor reads that measure inventory and delivers one record per measure: the country and river basin district, the KEY TYPE MEASURE (the coded intervention category), the national or RBD-specific MEASURE CODE, the measure TYPE (basic or supplementary), and the marine-strategy (MSFD) relevance flag — all carried as filed. It is the measure-inventory layer of Europe's water-restoration effort.

### Who buys this and for what job

- **Water-policy analysts** benchmarking which Key Type Measures dominate a country's or basin's programme.
- **Environmental consultancies** mapping planned interventions against pressures and status.
- **Marine-strategy teams** using the MSFD relevance flag to find freshwater measures that also serve marine goals.
- **Data engineers** who want the WISE WFD measure inventory 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 programme entries as filed — not a compliance verdict.

### River-basin grain — no person data

The unit of every record is a measure for a river basin district — a coded intervention and its attributes, never a person. WISE WFD reporting is at river-basin level: there is **no contact, operator, or responsible-person field** in the source table, and none is selected or emitted. The free-text measure NAME and the conditional free-text "other key type measure" field are **EXCLUDED at field selection** — the query keeps only the coded category, the measure code, the type, and the MSFD 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, never a person.

### A note on scale, honestly

The source table holds **59,689 rows**; this actor delivers the rows that carry an actual measure code — an exact `COUNT(*)` of **59,669** at build time, which matches the planning index for this category. 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 River Basin Measure Inventory Records — EEA WISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-river-basin-measure-inventory-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": "EL01:M01Σ0203:2016",
  "reporting_year": 2016,
  "country_code": "EL",
  "country_name": "Greece",
  "eu_rbd_code": "EL01",
  "rbd_name": "WESTERN PELOPONNESE",
  "rbd_area_km2": 8277.935,
  "key_type_measure": "KTM6 - Improving hydromorphological conditions of water bodies other than longitudinal continuity",
  "measure_code": "M01Σ0203",
  "measure_type": "Supplementary",
  "msfd_relevance": "No",
  "has_descriptive_data": 1,
  "file_url": "http://cdr.eionet.europa.eu/gr/eu/wfd2016/districts/el01/envxjvzfw/RBMPPoM_EL_20200130.xml",
  "source": "EEA WISE Water Framework Directive (WFD) — river basin Programme of Measures (Key Type Measures)",
  "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": "Coded river-basin interventions from the EU Water Framework Directive Programme of Measures, at measure grain from the EEA WISE WFD database. Each record carries the country and river basin district, the KEY TYPE MEASURE (the coded intervention category), the national/RBD MEASURE CODE, the measure TYPE (basic or supplementary), and the marine-strategy (MSFD) relevance flag VERBATIM. The free-text measure NAME and the conditional free-text 'other key type measure' field are EXCLUDED at field selection. River-basin grain — there is no contact, operator, or responsible-person field selected or emitted, and a person-key guard runs on every record.",
  "observed_at": "2026-09-25T17:33:45Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `river_basin_measure_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 measure. Representative example (values as reported):

```json
{
  "record_id": "ES150:ES150_2_Ceuta0085:2022",
  "reporting_year": 2022,
  "country_code": "ES",
  "country_name": "Spain",
  "eu_rbd_code": "ES150",
  "rbd_name": "CEUTA",
  "rbd_area_km2": 60.187,
  "key_type_measure": "KTM7 - Improvements in flow regime and/or establishment of ecological flows",
  "measure_code": "ES150_2_Ceuta0085",
  "measure_type": "Supplementary - additional protection",
  "msfd_relevance": "No",
  "source": "EEA WISE Water Framework Directive (WFD) — river basin Programme of Measures (Key Type Measures)",
  "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 coded measure. Identity: `record_id`, `country_code`, `country_name`, `eu_rbd_code`, `rbd_name`, `rbd_area_km2`, and `reporting_year`. Measure: `key_type_measure` (the coded intervention category), `measure_code`, `measure_type` (basic or supplementary), and `msfd_relevance`. 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 Key-Type-Measure inventory (always keeping only rows with a real measure code, plus your optional `countryCode` and `year`), ordered by the high-cardinality measure code, and flattens each row to one record — carrying every coded label **verbatim**, never anything person-shaped and never the free-text measure name — 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 inventory holds **59,669 rows** across reporting countries, river basin districts, Key Type Measures, and the 2016 and 2022 cycles. Because each record carries the `country_code`, the `eu_rbd_code`, the `key_type_measure`, and the `reporting_year`, segmenting by country, basin, measure type, or cycle is straightforward. Pull one country, one Key Type Measure, or the whole inventory to seed a water-policy warehouse.

### Working with the data

The inventory is a planning layer, and the fields make it actionable. Because every record pairs a `key_type_measure` with a `measure_type` and the `msfd_relevance` flag, an analyst can count which intervention categories dominate a country's programme in one group-by, separate basic from supplementary measures, and isolate the freshwater measures a country counts toward its marine strategy — and track how programmes changed between the 2016 and 2022 cycles.

### Cost guidance

One `river_basin_measure_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.** Measure categories and types are as filed by member states for the WFD reporting cycle; this actor reformats, it does not audit or recompute.
- **Codes, not narrative.** The free-text measure name is excluded by design; this cell delivers the coded skeleton (category, code, type, MSFD flag), not the descriptive title.
- **Two cycles merged.** The `reporting_year` field distinguishes the 2016 and 2022 cycles — filter on it if you want a single cycle.
- **Acknowledge the EEA**, and note there is **no person data** of any kind.

### Differentiation

It is the MEASURE (intervention) layer, distinct from the pressure, impact, status, and exemption cells, which describe the state of the water rather than the actions taken. Its specific job is the **WFD river-basin Programme of Measures inventory**.

### The NexGen Signal family

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

- [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)
- [EU Bathing Water Quality Records — EEA](https://apify.com/nexgensignal/eu-bathing-water-quality-records)
- [EU Industrial Emissions Records — EEA](https://apify.com/nexgensignal/eu-industrial-emissions-records)
- [EU Surface Water Priority Substance Records — EEA](https://apify.com/nexgensignal/eu-surface-water-priority-substance-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. River-basin grain; the free-text measure name is excluded; no contact, operator, or responsible-person field is selected or emitted, no natural-person data of any kind. Reported programme entries 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 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-river-basin-measure-inventory-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-river-basin-measure-inventory-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-river-basin-measure-inventory-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-river-basin-measure-inventory-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/H3iQvViUXd3V4ONL6/builds/xN6QwGfFvSAVh8eu0/openapi.json