# EU Groundwater Surface Water Linkage Records — EEA WISE (`nexgensignal/eu-groundwater-surface-water-linkage-records`) Actor

Keyless pay-per-record EEA WISE WFD groundwater-to-surface-water body linkages — groundwater body, linked surface-water code, transboundary, ecosystem, status context, as filed. No person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-groundwater-surface-water-linkage-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 gw-sw linkage 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 Surface Water Linkage Records — EEA WISE

**Keyless. Pay per record. Which surface water body each European groundwater body is linked to, with status and transboundary context.**

This actor turns the **European Environment Agency (EEA) WISE (Water Information System for Europe)** into clean, per-record data — the resolution of each groundwater body to its associated surface-water body across Europe. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per linkage record, 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, member states report which surface-water bodies each groundwater body is associated with. This actor reads that linkage table and delivers one record per groundwater-body-to-surface-water-body link: the country and river basin district, the groundwater body (code, name, area), the linked surface-water body code, and the surrounding context — transboundary status, terrestrial-ecosystem link, geological formation, and the groundwater body's quantitative and chemical status labels. It is the groundwater-to-surface-water resolution layer of Europe's water assessment.

### Who buys this and for what job

- **Hydrogeologists and catchment modellers resolving groundwater bodies to their linked surface waters**
- **Integrated water-management teams tracing groundwater–surface-water dependencies across basins**
- **Researchers studying transboundary and ecosystem-linked groundwater bodies**
- **Data engineers** who want the WISE gw-sw-linkage 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 groundwater-body to surface-water-body link — a water body or river basin and its reported attributes, never a person. WISE 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 status/flags, and the linked surface-water body code and status/transboundary context. 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 (`GWB_GroundWaterBody_linkSurfaceWaterBodyCode`) holds **124,412 rows** as verified by an exact `COUNT(*)` at build time — the real, populated linkage table (carrying the 2016 and 2022 reporting cycles), larger than an earlier index figure suggested. This live count is authoritative; the floor is cleared many times over.

### Sample output

![Sample output — EU Groundwater Surface Water Linkage Records — EEA WISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-groundwater-surface-water-linkage-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::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",
  "groundwater_body_area": 31.121,
  "groundwater_body_transboundary": "No",
  "link_surface_water_body": "Yes",
  "link_terrestrial_ecosystem": "No",
  "geological_formation": "Porous aquifers - highly productive",
  "quantitative_status_value": "2",
  "chemical_status_value": "2",
  "link_surface_water_body_code": null,
  "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 to surface-water body linkage",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) WISE (Water Information System for Europe) — groundwater-body to surface-water-body linkage. 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 Information System for Europe).",
  "disclaimer": "Groundwater-body to associated surface-water-body linkages, at groundwater-body / linked-surface-water-body / reporting-cycle grain from the EEA WISE Water Framework Directive database. Each record resolves a groundwater body to a linked surface-water body code, with transboundary, terrestrial-ecosystem, geological-formation, and quantitative/chemical status context carried as filed. Water-body grain — there is no contact, operator, or responsible-person field in the source, and none is selected or emitted; a person-key guard runs on every record as a backstop.",
  "observed_at": "2026-09-25T17:32:54Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `gw_sw_linkage_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 linkage record. Real example (values as reported):

```json
{
  "record_id": "ATGK100001:ATOK1000010000: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",
  "groundwater_body_transboundary": "No",
  "link_surface_water_body": "Yes",
  "link_surface_water_body_code": "ATOK1000010000",
  "quantitative_status_value": "2",
  "chemical_status_value": "2",
  "source": "EEA WISE Water Framework Directive (WFD) \u2014 groundwater to surface-water body linkage",
  "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 groundwater-to-surface-water link. Identity: `record_id`, `country_code`, `country_name`, `eu_rbd_code`, `rbd_name`, `eu_groundwater_body_code`, `groundwater_body_name`, `groundwater_body_area`, and `reporting_year`. Linkage: `link_surface_water_body`, `link_surface_water_body_code`, and `link_terrestrial_ecosystem`. Context: `groundwater_body_transboundary`, `geological_formation`, `quantitative_status_value`, and `chemical_status_value`. 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 gw-sw-linkage table (filtered to your optional `countryCode` and `year`), and flattens each row to one record — carrying every value and flag **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 **124,412 rows**. Because each record carries the `country_code`, the water-body identity, and the `link_surface_water_body_code`, segmenting by country, basin, or year is straightforward. Pull one country, or the whole table to seed a water-analysis warehouse.

### Identifiers and joins

Every record carries both the `eu_groundwater_body_code` and the `link_surface_water_body_code`, the two identifiers that let this linkage table act as a bridge across the fleet's WISE cells — joining a groundwater body's exemptions, emerging pollutants, and threshold context to the failing pollutants and exemptions of its linked surface-water body, on shared identifiers rather than a fuzzy name match.

### Working with the data

The linkages are a connectivity map, and the fields make them navigable. Because every record resolves a `eu_groundwater_body_code` to a `link_surface_water_body_code`, an analyst can build the groundwater–surface-water dependency graph for a basin, and the `groundwater_body_transboundary` and `link_terrestrial_ecosystem` flags isolate the cross-border and ecosystem-dependent bodies. The quantitative and chemical status labels travel on the link so a downstream consumer can weight each connection by the groundwater body's condition.

### Cost guidance

One `gw_sw_linkage_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.** Values, flags, and status labels are as filed by member states; this actor reformats, it does not audit or recompute.
- **A label, not a verdict.** These are reported classifications, standards, exceedances, or linkages, not an independent compliance or hazard assessment.
- **Acknowledge the EEA.** The acknowledgement travels on every record.
- **No person data** of any kind.

### Differentiation

It is distinct from the fleet's status, threshold, and exemption cells — this cell resolves the groundwater-to-surface-water BODY LINKAGE (which surface water each groundwater body connects to), a connectivity map rather than a status or standard. It differs entirely from the Nitrates, Bathing Water, and Urban Waste Water directive cells. Its specific job is the **WFD groundwater-to-surface-water body linkage**.

### The NexGen Signal family

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

- [EU Surface Water Failing Pollutant Records — EEA WISE](https://apify.com/nexgensignal/eu-surface-water-failing-pollutant-records)
- [EU Groundwater Threshold Value Records — EEA WISE](https://apify.com/nexgensignal/eu-groundwater-threshold-value-records)
- [EU Surface Water Chemical Exemption Records — EEA WISE](https://apify.com/nexgensignal/eu-surface-water-chemical-exemption-records)
- [EU Pesticide Water Monitoring Records — EEA](https://apify.com/nexgensignal/eu-pesticide-water-monitoring-records)
- [EU Waterbody Quality Records — EEA](https://apify.com/nexgensignal/eu-waterbody-quality-records)

*Source: European Environment Agency (EEA), WISE (Water Information System for Europe) (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 / river-basin grain; no contact, operator, or responsible-person field is selected or emitted, 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": 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-surface-water-linkage-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-surface-water-linkage-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-surface-water-linkage-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-groundwater-surface-water-linkage-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/6n3kDjErQXF04NTES/builds/VxlZprA201ASBl53u/openapi.json