# EU Water Abstraction Records — EEA WISE (`nexgensignal/eu-water-abstraction-records`) Actor

Per-record EU water-abstraction volumes by country, spatial unit, use code, and period from EEA WISE State of Environment (Waterbase). Keyless, pay per record, values verbatim, no person data.

- **URL**: https://apify.com/nexgensignal/eu-water-abstraction-records.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** Business, 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 water abstraction 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 Water Abstraction Records — EEA WISE

**Keyless. Pay per record. How much water Europe withdraws — abstraction volumes by country, spatial unit, use, and period, verbatim.**

This actor turns the **European Environment Agency (EEA) WISE State of Environment (Waterbase) water-abstraction dataset** into clean, per-record data — how much water Europe abstracts, by country, spatial unit, and use. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per abstraction observation, structured for water-resource and abstraction-pressure analysis, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

The EEA compiles national water-abstraction (withdrawal) reporting into the WISE State of Environment (Waterbase) water-abstraction dataset — how much water is taken from the environment, split by the source and the sector that uses it. This actor reads that table and delivers one record per spatial unit / observed-property / period: the country and spatial unit, the observed-property USE CODE (for example, abstraction from groundwater for public water supply, or from surface water for agriculture) carried verbatim, the time period and reference year, the observed VOLUME in the source units verbatim, and the observation-STATUS flag. It is the withdrawals side of Europe's water balance — the demand pressure on the resource.

### Who buys this and for what job

- **Water-resource analysts quantifying withdrawals by country, basin, and sector**
- **Abstraction-pressure and scarcity teams sizing demand against available resource**
- **Researchers comparing abstraction volumes and uses across Europe and over time**
- **Data engineers** who want the WISE water-abstraction 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.

### Spatial-unit grain — no person data

The unit of every record is a water-abstraction observation for a spatial unit — a withdrawal volume, never a person. The spatial unit 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 Water Abstraction Records — EEA WISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-water-abstraction-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": "AL:ABS_GW_DOM:2022",
  "country_code": "AL",
  "spatial_unit_identifier": "AL",
  "spatial_unit_identifier_scheme": "countryCode",
  "observed_property": "ABS_GW_DOM",
  "time_period": "2022",
  "year": "2022",
  "observed_volume": 0.023652,
  "observation_status": "A",
  "source": "EEA WISE State of Environment (Waterbase) — water abstraction",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) WISE State of Environment (Waterbase) — water abstraction volumes. 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": "Water abstraction (withdrawal) volumes by country / spatial unit / use / period from the EEA WISE State of Environment (Waterbase) water-abstraction dataset. Each record carries the spatial unit, the observed-property USE CODE (e.g. abstraction by source and sector such as groundwater for domestic use) VERBATIM, the time period, the observed VOLUME in the SOURCE UNITS verbatim, and the observation-STATUS flag. Country / spatial-unit 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:22:09Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `water_abstraction_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 | 500 | Ceiling on records delivered and billed. |

### Output

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

```json
{
  "record_id": "AT_SU_0001:gross freshwater abstraction by groundwater for public water supply:2016",
  "country_code": "AT",
  "spatial_unit_identifier": "AT_SU_0001",
  "spatial_unit_identifier_scheme": "eionetSchema",
  "observed_property": "gross freshwater abstraction by groundwater for public water supply",
  "time_period": "2016",
  "year": "2016",
  "observed_volume": 123.4,
  "observation_status": "A",
  "source": "EEA WISE State of Environment (Waterbase) \u2014 water abstraction",
  "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 abstraction observation. Identity: `record_id`, `country_code`, `spatial_unit_identifier`, and `spatial_unit_identifier_scheme`. Use and period: `observed_property` (the USE CODE, verbatim), `time_period`, and `year`. Measurement: `observed_volume` (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 water-abstraction 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 **68,058 rows**. Because each record carries the `country_code`, the spatial unit, the observed-property use code, and the year, segmenting is straightforward. Pull one slice, or the whole table to seed a warehouse.

### Working with the data

The abstractions are a demand ledger, and the fields make them additive. Because every record pairs an `observed_property` use code with an `observed_volume` at a `spatial_unit_identifier`, an analyst can build a country's or a basin's withdrawal profile by sector without unit-guessing — the volume travels in the source units, and the `observation_status` flag marks provisional or estimated figures. The `year` frames each volume in time, so multi-year abstraction trends assemble directly.

### Identifiers and joins

Every record carries the `spatial_unit_identifier` and `country_code`, keying each withdrawal to the fleet's water-return and reservoir-storage cells for the same spatial unit, and lining the withdrawals up against the WFD pressure and status cells so abstraction pressure can be read alongside the body's condition.

### Withdrawals versus returns

A water-abstraction figure is water TAKEN from the environment; a water-return figure is water PUT BACK (or lost) — the two halves of the human water balance. This cell reads the abstraction table; the companion return-flow cell reads the returns table. Keeping them as separate actors means a buyer pays only for the side they need, and pulling both and joining on the spatial unit lets net consumption be estimated — withdrawals minus returns — on a like-for-like basis.

### Cost guidance

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

This is a **net-new** category for the NexGenData fleet. It is distinct from **eu-water-return-flow-records** — that cell carries returned water, leakage and losses (water put back or lost), while this cell carries the WITHDRAWALS (water taken); withdrawals vs returns. Its specific job is the **WISE water-abstraction volumes by spatial unit, use, and period**.

### 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. Spatial-unit / use / period grain; the spatial unit 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": 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-water-abstraction-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-water-abstraction-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-water-abstraction-records --silent --output-dataset

```

## MCP server setup

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