# EU Waterbody Quality Records — EEA WISE Waterbase (`nexgensignal/eu-waterbody-quality-records`) Actor

Keyless, pay-per-record EEA WISE Waterbase data. One row per water-body determinand observation — determinand, unit, year, sample stats, observation/metadata status carried verbatim (never upgraded). EEA acknowledge; no person data.

- **URL**: https://apify.com/nexgensignal/eu-waterbody-quality-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 waterbody 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 Waterbody Quality Records — EEA WISE Waterbase

**Keyless. Pay per record. Europe's aggregated water-body chemistry — with the source's observation status carried honestly.**

This actor turns the **European Environment Agency (EEA)** WISE State-of-Environment (Waterbase) dataset into clean, per-water-body-determinand records — the aggregated chemical and quality observations reported for Europe's water bodies. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per water-body / determinand / period observation: the water-body identifier, the country, the determinand (e.g. nitrate, phosphate), the unit, the year, the sample statistics, and — carried **verbatim** — the source observation status and metadata status code, including "experimental". Water-body / determinand grain, structured for engineering use, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

The EEA's Waterbase aggregates member-state monitoring into per-water-body determinand observations — the summary statistics for a substance in a water body over a reporting period. This actor reads that dataset and flattens each observation into a single analysis-ready record: the water-body identifier and scheme, the country, the water-body category, the determinand code and label, the analysed matrix and unit, the reference year and sampling period, the sample count, the minimum/mean/maximum/median and standard-deviation values, and — crucially — the `resultObservationStatus`, `metadata_observationStatus`, and `metadata_statusCode`. Those status fields are carried **verbatim and never upgraded**: a value flagged "experimental" stays labelled experimental. Values are exactly as published. You are billed only for records actually delivered.

### Who buys this and for what job

- **Environmental-analytics, water-utility, and ESG teams** studying water-body chemistry and quality across Europe.
- **Research and modelling products** that need aggregated determinand statistics with their provenance status intact.
- **Diligence and risk tools** assessing water-quality pressure across a region or catchment.
- **Data engineers** who want the Waterbase aggregation as clean rows — with the observation status preserved, not silently dropped — without writing SQL against the EEA service.

### 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. This rider is carried in this README and on every record. The data is aggregated monitoring data as reported — not a regulatory status determination.

### Honest status — carried verbatim, never upgraded

This is the defining property of this actor. The Waterbase carries observation-status and metadata-status fields — including the value **"experimental"** — that qualify how settled a figure is. This actor carries them **verbatim on every record** and **never** strips them or upgrades an experimental figure to a settled fact. `metadata_status_code` is a required field in the output schema, so a downstream consumer always sees whether a value is experimental, stable, or valid. The acceptance suite feeds an experimental row and asserts the status survives unchanged.

### Water-body grain — no person data

The unit of every record is a water body / determinand / period observation. The water-body, river-basin, and sub-unit names are place names, not people; the dataset carries no natural-person fields, and this actor emits none, with a person-key guard as a backstop.

### Sample output

![Sample output — EU Waterbody Quality Records — EEA WISE Waterbase](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-waterbody-quality-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": "1",
  "water_body_identifier": "ALGW_011",
  "water_body_identifier_scheme": "eionetGroundWaterBodyCode",
  "country_code": "AL",
  "water_body_category": "GW",
  "determinand_code": "CAS_14797-55-8",
  "determinand_label": "Nitrate",
  "analysed_matrix": "W",
  "result_uom": "mg{NO3}/L",
  "reference_year": 2004,
  "sampling_period": "2004-01-01--2004-12-31",
  "number_of_samples": 1,
  "min_value": 4.8,
  "mean_value": 5.2,
  "max_value": 5.6,
  "median_value": null,
  "std_deviation_value": null,
  "result_observation_status": null,
  "metadata_observation_status": "U",
  "metadata_status_code": "experimental",
  "remarks": null,
  "metadata_version_id": "http://discomap.eea.europa.eu/data/wisesoe/deriveddata/T_WISE4_AggregatedDataByWaterBody/0.html",
  "metadata_begin_lifespan_version": "2015-11-30 00:00:00.000",
  "source": "European Environment Agency (EEA) WISE SOE Waterbase",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) WISE State of Environment (Waterbase) water-body data. 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) dataset.",
  "disclaimer": "Aggregated water-body determinand observation records, as reported by member states and published by the EEA. Water-body/determinand/year grain — no natural-person data. The source observation status and metadata status code (e.g. 'experimental', 'stable', 'valid') are carried VERBATIM on every record and are NEVER stripped or upgraded to a settled fact; experimental data stays labelled experimental.",
  "observed_at": "2026-09-25T17:34:48Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `waterbody_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 member-state code (e.g. ES, IT, UK). |
| `determinandContains` | string | — | Optional. Keep only observations whose determinand label contains this text (e.g. Nitrate, Phosphate). |
| `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 water-body / determinand observation. Real example (values as published):

```json
{
  "record_id": "26356",
  "water_body_identifier": "ES080MSBT080-150",
  "country_code": "ES",
  "water_body_category": "GW",
  "determinand_code": "CAS_14797-55-8",
  "determinand_label": "Nitrate",
  "result_uom": "mg/L",
  "reference_year": 2019,
  "number_of_samples": 4,
  "mean_value": 12.5,
  "result_observation_status": "A",
  "metadata_status_code": "experimental",
  "source": "European Environment Agency (EEA) WISE SOE Waterbase",
  "licence": "European Environment Agency (EEA) ... provided the source is acknowledged ...",
  "disclaimer": "Aggregated water-body determinand observation records ... status ... carried VERBATIM ... never ... upgraded ...",
  "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 water-body / determinand observation. Identity: `record_id` (UID), `water_body_identifier`, `water_body_identifier_scheme`, and `country_code`. Determinand: `water_body_category`, `determinand_code`, `determinand_label`, `analysed_matrix`, and `result_uom`. Period: `reference_year` and `sampling_period`. Statistics: `number_of_samples`, `min_value`, `mean_value`, `max_value`, `median_value`, and `std_deviation_value`. Status (verbatim): `result_observation_status`, `metadata_observation_status`, `metadata_status_code`, and `remarks`. Provenance: `metadata_version_id`, `metadata_begin_lifespan_version`, `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 then queries the Waterbase aggregated table through the DiscoData SQL service, applying your optional `countryCode` and `determinandContains` filters, and pages through the results. Each observation is flattened to one record — carrying the values and the observation/metadata status **verbatim**, never upgrading an experimental figure — 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 aggregated table holds on the order of **21,000+ water-body determinand observations** across reporting countries. Because each record carries the `water_body_identifier`, `determinand_label`, and `reference_year`, filtering by country or determinand and joining across years is straightforward. Note the reporting set varies by country — some member states report to this aggregation and others do not — which the honest status fields make visible rather than hiding.

### Cost guidance

One `waterbody_record` per delivered observation: cost = rows delivered × your plan's per-record price. Scope with `countryCode` or `determinandContains` to keep runs bounded. 1,000 observations is **$50** (Free) / **$33.50** (Gold); the whole ~21,000-row table is a one-time seed.

### Honest limitations

- **Aggregated data with status.** Figures are aggregated as reported; the observation status (including "experimental") is carried so you know how settled each value is.
- **Reporting varies.** Not every country reports to this aggregation; the data reflects what was reported.
- **As published.** Values and status are exactly as the EEA distributes them; this actor reformats, it does not recompute.
- **Acknowledge the EEA.** The acknowledgement travels on every record.
- **No person data** of any kind.

### Differentiation

It is distinct from the fleet's bathing-water (recreational classification), waste-water (plant compliance), and nitrate (single-parameter monitoring) cells: this carries **multi-determinand aggregated water-body observations with their provenance status intact**. It is the water-body chemistry layer, honest about how experimental each figure is.

### The NexGen Signal family

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

- [EU Nitrate Monitoring Records — EEA WISE Nitrates](https://apify.com/nexgensignal/eu-nitrate-monitoring-records)
- [EU Bathing Water Quality Records — EEA BWD](https://apify.com/nexgensignal/eu-bathing-water-quality-records)
- [EU Wastewater Compliance Records — EEA UWWTD](https://apify.com/nexgensignal/eu-wastewater-compliance-records)
- [EU Industrial Emissions Records — EEA IED Facilities](https://apify.com/nexgensignal/eu-industrial-emissions-records)
- [EU Natura 2000 Site Records — EEA Protected Sites](https://apify.com/nexgensignal/eu-natura2000-site-records)

*Source: European Environment Agency (EEA), WISE State of Environment (Waterbase) dataset (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. Aggregated monitoring data; observation and metadata status carried verbatim and never upgraded. Water-body grain; no person data of any kind.*

# Actor input Schema

## `countryCode` (type: `string`):

Optional 2-letter member-state code (e.g. DE, FR, IT).

## `determinandContains` (type: `string`):

Optional. Keep only observations whose determinand label contains this text (e.g. Nitrate, Phosphate).

## `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-waterbody-quality-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-waterbody-quality-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-waterbody-quality-records --silent --output-dataset

```

## MCP server setup

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