# EU Reservoir Storage Records — EEA WISE (`nexgensignal/eu-reservoir-storage-records`) Actor

Per-record EU reservoir inventory and storage by water body and date from EEA WISE State of Environment (Waterbase). Keyless, pay per record, values verbatim, no person data.

- **URL**: https://apify.com/nexgensignal/eu-reservoir-storage-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 reservoir storage 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 Reservoir Storage Records — EEA WISE

**Keyless. Pay per record. Europe's reported reservoir inventory and storage — by water body and date, in the source units, verbatim.**

This actor turns the **European Environment Agency (EEA) WISE State of Environment (Waterbase) reservoir dataset** into clean, per-record data — Europe's reported reservoir inventory and storage, by water body and date. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per reservoir observation, structured for water-storage and drought-resilience analysis, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

The EEA compiles national reporting on reservoirs — the artificial and regulated water bodies that store water for supply, power, and flood control — into the WISE State of Environment (Waterbase) reservoir dataset. This actor reads that table and delivers one record per water body / observed-property / period: the country and water body, the observed-property CODE (for example, reservoir inventory) carried verbatim, the time period and reference year, the observed VALUE in the source units verbatim, and the observation-STATUS flag. It is the stored-water layer of Europe's water balance — the buffer between supply and demand.

### Who buys this and for what job

- **Water-storage and supply analysts tracking reservoir inventory and volumes by water body**
- **Drought-resilience and planning teams sizing the stored-water buffer across basins**
- **Researchers studying reservoir storage across Europe and over time**
- **Data engineers** who want the WISE reservoir-data 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 labels as filed — not a compliance verdict.

### Water-body grain — no person data

The unit of every record is a reservoir observation for a water body — a stored-water figure, never a person. The water body is a location code; there is no contact, operator, or responsible-person field in the source, and none is selected or emitted; the free-text remark and metadata narrative fields are excluded at field selection. A person-key guard runs on every record as a backstop.

### Sample output

![Sample output — EU Reservoir Storage Records — EEA WISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-reservoir-storage-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": "BERW17_MM39R:RINV:2000",
  "country_code": "BE",
  "water_body_identifier": "BERW17_MM39R",
  "water_body_identifier_scheme": "euSurfaceWaterBodyCode",
  "observed_property": "RINV",
  "time_period": "2000",
  "year": "2000",
  "observed_value": null,
  "observation_status": "M",
  "source": "EEA WISE State of Environment (Waterbase) — reservoir data",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) WISE State of Environment (Waterbase) — reservoir inventory and storage. 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 State of Environment (Waterbase).",
  "disclaimer": "Reported reservoir inventory and storage by water body and date from the EEA WISE State of Environment (Waterbase) reservoir dataset. Each record carries the water body, the observed-property CODE (e.g. reservoir inventory) VERBATIM, the time period, the observed VALUE in the SOURCE UNITS verbatim, and the observation-STATUS flag. Water-body grain — there is no contact, operator, or responsible-person field in the source, and none is selected or emitted (free-text remark fields excluded at field selection); a person-key guard runs on every record as a backstop.",
  "observed_at": "2026-09-25T17:33:45Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `reservoir_storage_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 reference year to filter. |
| `maxRecords` | integer | 10 | Ceiling on records delivered and billed. |

**Default changed on 30 Sep 2026:** if you leave `maxRecords` out, a run now returns up to **10** records (it was 500). Set `maxRecords` yourself to get more — the maximum is unchanged.

### Output

One JSON object per reservoir observation. Real example (values as reported):

```json
{
  "record_id": "ATWB0001:reservoir inventory:2016",
  "country_code": "AT",
  "water_body_identifier": "ATWB0001",
  "water_body_identifier_scheme": "eionetSchema",
  "observed_property": "reservoir inventory",
  "time_period": "2016",
  "year": "2016",
  "observed_value": 9.9,
  "observation_status": "A",
  "source": "EEA WISE State of Environment (Waterbase) \u2014 reservoir data",
  "source_url": "https://discodata.eea.europa.eu/",
  "observed_at": "2026-08-23T00: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 reservoir observation. Identity: `record_id`, `country_code`, `water_body_identifier`, and `water_body_identifier_scheme`. Property and period: `observed_property` (the CODE, verbatim), `time_period`, and `year`. Measurement: `observed_value` (in the source units) and `observation_status`. 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 reservoir-data table (filtered to your optional `countryCode` and optional `year`), and flattens each row to one record — carrying every value and label **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 **90,875 rows**. Because each record carries the `country_code`, the water body, the observed-property code, and the year, segmenting is straightforward. Pull one slice, or the whole table to seed a warehouse.

### Working with the data

The reservoir records are a storage ledger, and the fields make them comparable. Because every record pairs an `observed_property` code with an `observed_value` at a `water_body_identifier`, an analyst can profile a basin's reservoir inventory and storage without unit-guessing — the value travels in the source units, and the `observation_status` flag marks provisional or estimated figures. The `year` frames each value in time, so storage trends and inventory changes assemble directly.

### Identifiers and joins

Every record carries the `water_body_identifier` and `country_code`, keying each reservoir observation to the fleet's abstraction and return-flow cells for the same spatial context, and to the WFD water-body cells where the same body identifiers appear — so stored water can be read alongside withdrawals, returns, and status.

### Inventory versus flow

A reservoir figure is a STOCK — how much water is held, or the inventory of reservoirs — whereas abstraction and return figures are FLOWS: water moving in and out over a period. This cell reads the reservoir stock table; the abstraction and return cells read the flow tables. Pulling all three and joining on the spatial context lets a buyer relate the stored buffer to the withdrawals drawn from it and the returns feeding it — the stock-and-flow picture of a basin's managed water.

### Cost guidance

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

### Honest limitations

- **As reported.** Values, labels, and flags are as filed; this actor reformats, it does not audit or recompute.
- **A label, not a verdict.** These are reported values and classifications, not an independent compliance or conservation assessment.
- **Acknowledge the EEA.** The acknowledgement travels on every record.
- **No person data** of any kind.

### Differentiation

It is distinct from **eu-water-abstraction-records** and **eu-water-return-flow-records** — those cells carry FLOWS (water withdrawn and water returned over a period), while this cell carries the reservoir STOCK (inventory and storage held); stock vs flow. Its specific job is the **WISE reservoir inventory and storage by water body and date**.

### The NexGen Signal family

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

- [EU Reservoir Storage Records — EEA WISE](https://apify.com/nexgensignal/eu-reservoir-storage-records)
- [EU Water Return Flow Records — EEA WISE](https://apify.com/nexgensignal/eu-water-return-flow-records)
- [EU Water Emission Load Records — EEA WISE](https://apify.com/nexgensignal/eu-water-emission-load-records)
- [EU Riverine Pollutant Load Records — EEA WISE](https://apify.com/nexgensignal/eu-riverine-pollutant-load-records)
- [EU Surface Water Chemical Status Records — EEA WISE](https://apify.com/nexgensignal/eu-surface-water-chemical-status-records)

*Source: European Environment Agency (EEA), WISE State of Environment (Waterbase) (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 / property / period grain; the water body is a location code; free-text remark/metadata fields excluded, no contact/operator/responsible-person field selected or emitted. No natural-person data of any kind. Values and 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 reference year to filter.

## `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-reservoir-storage-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-reservoir-storage-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-reservoir-storage-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-reservoir-storage-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/8Xo2x1I8oZ5Nr0JHt/builds/dAgu0E1qIpMRXprpJ/openapi.json