# EU Waterbody Pesticide Exceedance Records — EEA WISE (`nexgensignal/eu-waterbody-pesticide-exceedance-records`) Actor

Keyless pay-per-record EEA WISE Indicators pesticide-standard exceedances by water body — pesticide, matrix, reference year, MAC-EQS/AA-EQS exceedance flags, as filed. No person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-waterbody-pesticide-exceedance-records.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** Automation, Developer tools
- **Features:** Limited permissions
- **Stats:** 2 total users, 1 monthly users, 92.6% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 1,000 pesticide exceedance 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 Pesticide Exceedance Records — EEA WISE

**Keyless. Pay per record. Every recorded pesticide-standard exceedance in Europe's water bodies, chemical by chemical.**

This actor turns the **European Environment Agency (EEA) WISE (Water Information System for Europe)** into clean, per-record data — the official pesticide-standard exceedances recorded across Europe's water bodies. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per pesticide-exceedance 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

The EEA aggregates national pesticide monitoring into a by-water-body indicator dataset, flagging where a pesticide exceeded its quality standard. This actor reads that dataset and delivers one record per recorded EXCEEDANCE: the country, the water body (identifier, name, category), the river basin district, the pesticide (observed property), the analysed matrix, the reference year, the number of sites, the water-body status code, and the exceedance flags against the MAC-EQS and AA-EQS quality standards — all carried as filed. It is the pesticide-exceedance layer of Europe's water indicators.

### Who buys this and for what job

- **Water-quality and pesticide-policy analysts tracking where and when standards were exceeded**
- **Agri-environment and catchment teams targeting the water bodies with pesticide exceedances**
- **Researchers and NGOs building pesticide-exceedance time series by water body**
- **Data engineers** who want the WISE pesticide-exceedance 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 recorded pesticide-standard exceedance for a water body — 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 pesticide, matrix, year, and exceedance flags. 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

This actor delivers only the rows of the EEA WISE Indicators by-water-body pesticides dataset where an EXCEEDANCE was recorded (`exceedance = 1`) — **32,610 rows** as verified by an exact `COUNT(*)` at build time. The full dataset is much larger; this cell is deliberately scoped to the exceedance events, which is what makes it distinct from the concentration-observation monitoring cell.

### Sample output

![Sample output — EU Waterbody Pesticide Exceedance Records — EEA WISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-waterbody-pesticide-exceedance-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": "ATGK100002:CAS_1912-24-9:total:2013",
  "country_code": "AT",
  "country_name": "AUSTRIA",
  "water_body_identifier": "ATGK100002",
  "water_body_name": "NO INTERNATIONAL NAME",
  "rbd_identifier": "AT1000",
  "rbd_name": "DANUBE",
  "spatial_unit_name": "DANUBE",
  "water_body_category": "GW",
  "eea_indicator": "CAS_1912-24-9 - Atrazine",
  "observed_property_code": "CAS_1912-24-9",
  "procedure_analysed_matrix": "total",
  "reference_year": 2013,
  "result_number_of_sites": 67,
  "water_body_status_code": "stable",
  "exceedance_mac_eqs": null,
  "exceedance_aa_eqs": null,
  "exceedance_quality_standard": 1,
  "exceedance": 1,
  "lat": 47.44504,
  "lon": 11.90166,
  "source": "EEA WISE Indicators — pesticide standard exceedances by water body",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) WISE (Water Information System for Europe) — pesticide standard exceedances by water body. 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": "Official pesticide-standard EXCEEDANCES aggregated by water body, at water-body / pesticide / matrix / year grain from the EEA WISE Indicators pesticides dataset (rows where an exceedance was recorded). Each record names a water body, the pesticide (observed property), the analysed matrix, the reference year, and the exceedance flags against the MAC-EQS and AA-EQS quality standards — carried as filed, never an independent hazard verdict. 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. Coordinates are water-body locations, not persons.",
  "observed_at": "2026-09-25T17:34:55Z"
}
```

### Pricing

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

```json
{
  "record_id": "DEWB001:CAS_1912-24-9 - Atrazine:Water:2020",
  "country_code": "DE",
  "country_name": "Germany",
  "water_body_identifier": "DEWB001",
  "water_body_name": "Example Lake",
  "rbd_name": "RHINE",
  "water_body_category": "LW",
  "observed_property_code": "CAS_1912-24-9 - Atrazine",
  "procedure_analysed_matrix": "Water",
  "reference_year": 2020,
  "exceedance_aa_eqs": 1,
  "exceedance": 1,
  "lat": 50.1,
  "lon": 8.2,
  "source": "EEA WISE Indicators \u2014 pesticide standard exceedances by water body",
  "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 recorded exceedance. Identity: `record_id`, `country_code`, `country_name`, `water_body_identifier`, `water_body_name`, `rbd_identifier`, `rbd_name`, `spatial_unit_name`, `water_body_category`, and `reference_year`. Measurement: `eea_indicator`, `observed_property_code` (the pesticide), `procedure_analysed_matrix`, `result_number_of_sites`, and `water_body_status_code`. Exceedance flags: `exceedance_mac_eqs`, `exceedance_aa_eqs`, `exceedance_quality_standard`, and `exceedance`. Location: `lat` and `lon` (water-body coordinates). 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 pesticide-exceedance table (filtered to your optional `countryCode` and `year`, with a built-in filter to exceedance rows), 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 **32,610 rows** (the exceedance subset of the by-water-body pesticides dataset). Because each record carries the `country_code`, the water-body identity, and the `observed_property_code` and `reference_year`, segmenting by country, basin, or year is straightforward. Pull one country, or the whole table to seed a water-analysis warehouse.

### Working with the data

The exceedances are an early-warning layer, and the fields make them trackable. Because every record pairs an `observed_property_code` (pesticide) with a `reference_year` and the MAC-EQS/AA-EQS exceedance flags, an analyst can build a time series of which pesticides exceeded standards in which water bodies, and the `water_body_category` separates rivers, lakes, and coastal/transitional waters. The coordinates support mapping exceedance hotspots.

### Cost guidance

One `pesticide_exceedance_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 **eu-pesticide-water-monitoring-records** — that cell delivers the CONCENTRATION OBSERVATIONS (the full measurement dataset), while this cell delivers only the recorded EXCEEDANCE EVENTS aggregated by water body; observations vs exceedances, a different grain and a different question. It differs entirely from the Nitrates, Bathing Water, and Urban Waste Water directive cells. Its specific job is the **WISE pesticide-standard exceedances by water body**.

### 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 reference 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-waterbody-pesticide-exceedance-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-pesticide-exceedance-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-pesticide-exceedance-records --silent --output-dataset

```

## MCP server setup

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