# EU Groundwater Significant Impact Records — EEA WISE (`nexgensignal/eu-groundwater-significant-impact-records`) Actor

Keyless pay-per-record EEA WISE WFD groundwater significant-impact types — groundwater body, impact type, quantitative and chemical status, as filed. Water-body grain, no person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-groundwater-significant-impact-records.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** 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 groundwater significant-impact 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 Significant Impact Records — EEA WISE

**Keyless. Pay per record. Every officially recorded significant impact type on a European groundwater body.**

This actor turns the **European Environment Agency (EEA) WISE Water Framework Directive (WFD) database** into clean, per-record data — the significant impact TYPES that member states have recorded on their groundwater bodies. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per recorded significant impact, structured for environmental and water-management 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, each groundwater body is assessed for the significant impacts acting on it — the ways human activity measurably harms the body's status. This actor reads that impact-type table, filtered to the rows that actually carry a recorded significant impact, and delivers one record per impact: the country and river basin district, the groundwater body (code, name, area), the significant IMPACT TYPE, and the body's quantitative and chemical status labels — all carried as filed. It is the groundwater significant-impact layer of Europe's water assessment, the impact companion to the pressure and exemption cells.

### Who buys this and for what job

- **Regulatory-intelligence teams** tracking which groundwater bodies carry which significant impacts and where.
- **Environmental NGOs and researchers** analysing the pattern of impacts across countries and basins.
- **Catchment and agri-environment products** linking impacts to their driving pressures.
- **Data engineers** who want the WISE WFD groundwater significant-impact 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 significant impact for a groundwater body — a water body and its reported attributes, never a person. WISE WFD reporting is at water-body / river-basin level: there is **no contact, operator, or responsible-person field** in the source table, and none is selected or emitted — the query reads only the water-body identity, the impact type, and the status labels. The free-text "other impact" and "other pressure" narrative fields are **EXCLUDED at field selection**. A person-key guard runs on every record as a backstop. The `file_url`, where present, points to the official EEA/Eionet reporting file (an organisation reporting system), never a person.

### A note on scale, honestly

The source table holds **52,954 rows**, but many are groundwater bodies with no recorded significant impact (a null impact type). This actor filters to the rows that actually carry a recorded significant impact type — an exact `COUNT(*)` of **38,671** at build time, which matches the planning index for this category exactly. It carries both the 2016 and 2022 Water Framework Directive reporting cycles (the `reporting_year` field distinguishes them). The live count above is authoritative.

### Sample output

![Sample output — EU Groundwater Significant Impact Records — EEA WISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-groundwater-significant-impact-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": "ATGK100001:Unpopulated: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": "NO INTERNATIONAL NAME",
  "area_km2": 31.121,
  "significant_impact_type": "Unpopulated",
  "gw_quantitative_status_value": "2",
  "gw_chemical_status_value": "2",
  "groundwater_body_transboundary": "No",
  "has_descriptive_data": 1,
  "file_url": "http://cdr.eionet.europa.eu/at/eu/wfd2016/districts/at1000/envwvttw/GWB_AT_20170405.xml",
  "source": "EEA WISE Water Framework Directive (WFD) — groundwater body significant impact types",
  "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": "Officially recorded SIGNIFICANT IMPACT TYPES for European groundwater bodies, at groundwater-body / impact-type grain from the EEA WISE WFD database (rows are filtered to those that actually carry a recorded significant impact type). Each record carries the country and river basin district, the groundwater body (code, name, area), the significant IMPACT TYPE, and the body's quantitative and chemical status labels VERBATIM. The free-text 'other impact' and 'other pressure' narrative fields are EXCLUDED at field selection. Water-body grain — there is no contact, operator, or responsible-person field in the source, none is selected or emitted, and a person-key guard runs on every record.",
  "observed_at": "2026-09-25T17:32:21Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `gw_significant_impact_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 to filter (e.g. 2016, 2022). |
| `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 significant impact. Representative example (values as reported):

```json
{
  "record_id": "DEGW001:Saline Intrusion:2022",
  "reporting_year": 2022,
  "country_code": "DE",
  "country_name": "Germany",
  "eu_rbd_code": "DE1000",
  "rbd_name": "RHINE",
  "eu_groundwater_body_code": "DEGW001",
  "groundwater_body_name": "Example GW Body",
  "area_km2": 128.4,
  "significant_impact_type": "Saline or other intrusion",
  "gw_quantitative_status_value": "2",
  "gw_chemical_status_value": "2",
  "source": "EEA WISE Water Framework Directive (WFD) — groundwater body significant impact types",
  "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 significant impact for a groundwater body. Identity: `record_id`, `country_code`, `country_name`, `eu_rbd_code`, `rbd_name`, `eu_groundwater_body_code`, `groundwater_body_name`, `area_km2`, and `reporting_year`. Impact and status: `significant_impact_type`, `gw_quantitative_status_value`, and `gw_chemical_status_value`. Plus `groundwater_body_transboundary`, `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 groundwater significant-impact table (always filtered to rows that carry a recorded impact type, plus your optional `countryCode` and `year`), ordered by the high-cardinality groundwater-body code, and flattens each row to one record — carrying every label and value **verbatim**, never anything person-shaped and never the free-text narrative fields — 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 filtered table holds **38,671 rows** across reporting countries, river basin districts, and the 2016 and 2022 WFD reporting cycles. Because each record carries the `country_code`, the water-body identity, the `significant_impact_type`, and the `reporting_year`, segmenting by country, basin, impact type, or cycle is straightforward. Pull one country, one impact type, or the whole filtered table to seed a water-status warehouse.

### Working with the data

The impacts are a diagnostic layer, and the fields make them actionable. Because every record pairs a groundwater body with a `significant_impact_type` and its quantitative and chemical status, an analyst can find, in one group-by, which impacts dominate among the bodies that are not in good status — and can track impact reporting between the 2016 and 2022 cycles. Joined to the significant-pressure and exemption cells on the groundwater-body code, it completes the pressure-impact-exemption picture.

### Cost guidance

One `gw_significant_impact_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.** Impact types and status labels are as filed by member states for the WFD reporting cycle; this actor reformats, it does not audit or recompute.
- **A classification, not a verdict.** These are reported significant-impact classifications, not an independent assessment.
- **Filtered to recorded impacts.** Bodies with no recorded significant impact type are excluded by design; the full table (with nulls) is larger.
- **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 IMPACT layer, distinct from the groundwater significant-PRESSURE data, from the chemical- and quantitative-EXEMPTION cells, and from the protected-area linkage cell. Its specific job is the **WFD groundwater significant-impact types**.

### The NexGen Signal family

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

- [EU Groundwater Chemical Exemption Records — EEA](https://apify.com/nexgensignal/eu-groundwater-chemical-exemption-records)
- [EU Groundwater Quantitative Exemption Records — EEA](https://apify.com/nexgensignal/eu-groundwater-quantitative-exemption-records)
- [EU Groundwater Protected Area Linkage Records — EEA](https://apify.com/nexgensignal/eu-groundwater-protected-area-linkage-records)
- [EU Groundwater Threshold Value Records — EEA](https://apify.com/nexgensignal/eu-groundwater-threshold-value-records)
- [EU Waterbody Quality Records — EEA](https://apify.com/nexgensignal/eu-waterbody-quality-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. 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 to filter (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-groundwater-significant-impact-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-groundwater-significant-impact-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-groundwater-significant-impact-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-groundwater-significant-impact-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/QwDfRmLaVTECAkwDq/builds/3HjEwXK2EJZvd8GeY/openapi.json