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

Keyless pay-per-record EEA WISE WFD groundwater significant pressures — groundwater body, quantitative/chemical status, pressure type and group, as filed. Twin of the surface-water pressure cell. No person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-groundwater-pressure-source-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 gw 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?

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 Groundwater Pressure Source Records — EEA WISE

**Keyless. Pay per record. The significant pressures attributed to each of Europe's groundwater 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 groundwater bodies. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per pressure attribution, structured for groundwater-management 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 groundwater body. This actor reads that pressure table and delivers one record per groundwater body / pressure-type / cycle: the country, river basin, and groundwater body; its quantitative and chemical status labels; and the significant PRESSURE TYPE and its group attributed to that body — all carried as filed. It is the groundwater pressure-attribution layer, the twin of the surface-water pressure cell.

### Who buys this and for what job

- **Groundwater and catchment analysts mapping which pressures act on which groundwater bodies**
- **Water-management teams targeting the pressures behind groundwater status failures**
- **Researchers studying groundwater pressure attribution across basins**
- **Data engineers** who want the WISE WFD groundwater 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 groundwater body — a driver line, never a person. There is no contact, operator, or responsible-person field in the source, and none is selected or emitted; 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.

### Sample output

![Sample output — EU Groundwater Pressure Source Records — EEA WISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-groundwater-pressure-source-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": "::2010",
  "reporting_year": 2010,
  "country_code": "BE",
  "country_name": "Belgium",
  "eu_rbd_code": "BENOORDZEE_FED",
  "rbd_name": "BELGIAN COAST",
  "eu_groundwater_body_code": null,
  "groundwater_body_name": null,
  "quantitative_status_value": null,
  "chemical_status_value": null,
  "significant_pressure_type": null,
  "significant_pressure_type_group": null,
  "file_url": null,
  "source": "EEA WISE Water Framework Directive (WFD) — groundwater significant pressures",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) WISE Water Framework Directive (WFD) database — groundwater significant pressures. 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.",
  "disclaimer": "Significant pressures attributed to groundwater bodies at groundwater-body / pressure-type / reporting-cycle grain from the EEA WISE Water Framework Directive database. Each record names a groundwater body, its quantitative and chemical status labels, and the significant PRESSURE TYPE and its group attributed to that body — carried as filed. This is the GROUNDWATER pressure regime, the twin of the surface-water pressure cell. Water-body grain — there is no contact, operator, or responsible-person field in the source, and none is selected or emitted (free-text 'other' pressure/impact fields excluded at field selection); a person-key guard runs on every record as a backstop.",
  "observed_at": "2026-09-25T17:20:42Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `gw_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 | — | Optional 2-letter country code (e.g. DE, FR). |
| `year` | integer | — | Optional reporting cycle year to filter. |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per pressure attribution. Real example (values as reported):

```json
{
  "record_id": "ATGK100001:2.1 - Diffuse - Agricultural:2016",
  "reporting_year": 2016,
  "country_code": "AT",
  "country_name": "Austria",
  "eu_rbd_code": "AT1000",
  "rbd_name": "DANUBE",
  "eu_groundwater_body_code": "ATGK100001",
  "groundwater_body_name": "Example GW Body",
  "quantitative_status_value": "2",
  "chemical_status_value": "2",
  "significant_pressure_type": "2.1 - Diffuse - Agricultural",
  "significant_pressure_type_group": "Diffuse",
  "source": "EEA WISE Water Framework Directive (WFD) \u2014 groundwater 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_groundwater_body_code`, `groundwater_body_name`, and `reporting_year`. Status: `quantitative_status_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 groundwater significant-pressure table (filtered to your optional `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 **64,385 rows**. Because each record carries the `country_code`, the groundwater-body identity, and the pressure type, segmenting is straightforward. Pull one slice, or the whole table to seed a 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's groundwater and correlate them with status, and the `significant_pressure_type_group` rolls the detailed types up to families. The `reporting_year` tracks change between cycles.

### Identifiers and joins

Every record carries the `eu_groundwater_body_code`, keying each pressure attribution to the fleet's groundwater pollutant-failure, exemption, and failure-reason cells for the same body, on a shared identifier rather than a fuzzy name match.

### The groundwater–surface-water twin

This cell is the groundwater half of a deliberate pair: it uses the same pressure-type taxonomy as the surface-water pressure cell but reads the groundwater table, exactly as the chemical- and quantitative-failure-reason cells split the two regimes. Keeping them as separate actors means a buyer pays only for the compartment they need, and the shared taxonomy lets pressures be compared across groundwater and surface water on a like-for-like basis when both are pulled.

### Rolling pressures up to families

The `significant_pressure_type` follows the WFD's structured pressure taxonomy, and the `significant_pressure_type_group` is its family roll-up, so an analyst can move between a detailed pressure code and its broad class — diffuse, point, abstraction, hydromorphology — in a single field without maintaining a crosswalk. Because two reporting cycles share the schema, the same body can be compared across 2016 and 2022 to see whether a pressure was newly attributed, carried over, or dropped.

### Cost guidance

One `gw_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, values, and flags are as filed; this actor reformats, it does not audit or recompute.
- **A label, not a verdict.** These are reported classifications and outcomes, not an independent compliance or health 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-waterbody-pressure-source-records** — that cell attributes pressures to SURFACE water bodies, while this cell attributes them to GROUNDWATER bodies; the same twin discipline as the chemical/quantitative failure-reason pair. Its specific job is the **WFD groundwater significant-pressure attributions**.

### The NexGen Signal family

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

- [EU Waterbody Pressure Source Records — EEA WISE](https://apify.com/nexgensignal/eu-waterbody-pressure-source-records)
- [EU Groundwater Pollutant Failure Records — EEA WISE](https://apify.com/nexgensignal/eu-groundwater-pollutant-failure-records)
- [EU Surface Water Priority Substance Records — EEA WISE](https://apify.com/nexgensignal/eu-surface-water-priority-substance-records)
- [EU Waterbody Quality Records — EEA](https://apify.com/nexgensignal/eu-waterbody-quality-records)
- [EU Water Emission Load Records — EEA WISE](https://apify.com/nexgensignal/eu-water-emission-load-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. Groundwater-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`):

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

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

Optional reporting cycle 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-groundwater-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 = { "maxRecords": 500 }

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/eu-groundwater-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 '{
  "maxRecords": 500
}' |
apify call nexgensignal/eu-groundwater-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-groundwater-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/pcQ1mhYrV83gCzaca/builds/DpUSOku7irinmhjvd/openapi.json