# EU Water Emission Load Records — EEA WISE (`nexgensignal/eu-water-emission-load-records`) Actor

Keyless pay-per-record EEA WISE Waterbase emissions to water — river basin, pollutant, source category, emissions value and unit in source units, method and status flags, verbatim. No person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-water-emission-load-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 water emission load 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 Water Emission Load Records — EEA WISE

**Keyless. Pay per record. Pollutant emissions to Europe's waters — by river basin, source category, and period, verbatim.**

This actor turns the **European Environment Agency (EEA) WISE State of Environment (Waterbase) emissions dataset** into clean, per-record data — the pollutant emissions to water reported for Europe's river basins. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per emission-load record, structured for water-pollution and catchment-load analysis, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

The EEA compiles national reporting of pollutant emissions to water into the WISE State of Environment (Waterbase) emissions dataset. This actor reads that emissions table and delivers one record per river basin / pollutant / source category / period: the country and spatial unit (river basin district), the reference period, the pollutant (determinand code and label), the emissions SOURCE CATEGORY, an EPRTR-facilities flag, and the emissions VALUE and UNIT in the source units verbatim, plus the emissions METHOD and observation-STATUS flags. It is the water-emissions layer of Europe's catchment pollution picture.

### Who buys this and for what job

- **Water-pollution analysts quantifying emissions to water by basin, pollutant, and source**
- **Catchment-load modelling teams feeding official emissions into pollution models**
- **Researchers comparing point vs diffuse emission sources to water across basins**
- **Data engineers** who want the WISE water emissions 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 as filed — not a compliance verdict.

### River-basin grain — no person data

The unit of every record is a pollutant emission load for a basin, source, and period — a load figure, never a person. 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. Free-text remark fields are excluded at field selection.

### Sample output

![Sample output — EU Water Emission Load Records — EEA WISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-water-emission-load-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": "AT1000:CAS_7439-92-1:I:2016",
  "country_code": "AT",
  "spatial_unit_identifier": "AT1000",
  "spatial_unit_identifier_scheme": "euRBDCode",
  "reference_period": "2016",
  "determinand_code": "CAS_7439-92-1",
  "determinand_label": "Lead and its compounds",
  "emissions_source_category": "I",
  "eprtr_facilities": "yes",
  "emissions_value": 759.5,
  "emissions_uom": "kg/a",
  "emissions_method": "calculated",
  "observation_status": "X",
  "source": "EEA WISE State of Environment (Waterbase) — emissions to water",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) WISE State of Environment (Waterbase) — pollutant emissions to water. 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).",
  "disclaimer": "Pollutant emissions to water by river basin / source category / period from the EEA WISE State of Environment (Waterbase) emissions dataset. Each record carries the spatial unit (river basin district), the reference period, the pollutant (determinand code and label), the emissions SOURCE CATEGORY, an EPRTR-facilities flag, and the emissions VALUE and UNIT in the SOURCE UNITS VERBATIM, plus the emissions METHOD and observation-STATUS flags carried verbatim. River-basin 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:34:25Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `water_emission_load_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 period to filter. |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per emission-load record. Real example (values as reported):

```json
{
  "record_id": "AT1000:CAS_7439-92-1:I:2016",
  "country_code": "AT",
  "spatial_unit_identifier": "AT1000",
  "spatial_unit_identifier_scheme": "euRBDCode",
  "reference_period": "2016",
  "determinand_code": "CAS_7439-92-1",
  "determinand_label": "Lead and its compounds",
  "emissions_source_category": "I",
  "eprtr_facilities": "yes",
  "emissions_value": 759.5,
  "emissions_uom": "kg/a",
  "emissions_method": "calculated",
  "observation_status": "X",
  "source": "EEA WISE State of Environment (Waterbase) \u2014 emissions to water",
  "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 emission load. Identity: `record_id`, `country_code`, `spatial_unit_identifier`, `spatial_unit_identifier_scheme`, and `reference_period`. Pollutant and source: `determinand_code`, `determinand_label`, `emissions_source_category`, and `eprtr_facilities`. Measurement: `emissions_value`, `emissions_uom`, `emissions_method`, and `observation_status`. 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 water emissions table (filtered to your optional `countryCode` and optional `year`), and flattens each row to one record — carrying every 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 **171,771 rows**. Because each record carries the `determinand_label`, `emissions_source_category`, and `reference_period`, segmenting is straightforward. Pull one slice, or the whole table to seed a warehouse.

### Working with the data

The emission loads are a pollution ledger, and the fields make them additive. Because every record pairs a `determinand_label` with an `emissions_value` and `emissions_uom` and the `emissions_source_category`, an analyst can compare pollutant loads by source across basins without unit-guessing, and the `emissions_method` and `observation_status` flags travel so estimated or provisional figures can be handled explicitly. The `reference_period` frames each load in time.

### Identifiers and joins

Every record carries the `spatial_unit_identifier` (river basin district), keying each emission load to the fleet's other WISE cells for that basin — the input-total inventory, the failing pollutants, and the river-basin-specific standards — on a shared identifier rather than a fuzzy name match.

### Point, diffuse, and the EPRTR link

The `emissions_source_category` distinguishes the origin of a load — point sources, diffuse sources, and their sub-types — which is the first cut any catchment analysis needs, and the `eprtr_facilities` flag marks loads associated with the large industrial facilities reported under the E-PRTR. Together they let an analyst separate the industrial point-source contribution from diffuse agricultural and urban runoff for a given pollutant in a basin. The `emissions_method` (measured, calculated, estimated) and `observation_status` travel on every record so provisional or modelled loads are never silently mixed with measured ones.

### Cost guidance

One `water_emission_load_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).

### Building a basin load series

Because every record carries the `spatial_unit_identifier`, `determinand_code`, `emissions_source_category`, and `reference_period`, a single filtered pull reconstructs a basin's emission trajectory for a pollutant and source over time, and the shared river-basin identifier means those loads line up directly with the input-inventory totals and failing pollutants reported for the same basin — turning three separate WISE cells into one connected picture of what enters a basin and what fails there.

### Honest limitations

- **As reported.** Values, flags, and thresholds are as filed; this actor reformats, it does not audit or recompute.
- **A label, not a verdict.** These are reported statistics/regimes/volumes/loads, not an independent compliance assessment.
- **Acknowledge the EEA.** The acknowledgement travels on every record.
- **No person data** of any kind.

### Differentiation

It is distinct from **eu-basin-pollutant-input-total-records** — that cell carries the WFD programme-of-measures INPUT INVENTORY totals (point-and-diffuse inputs with methodology), while this cell carries the State-of-Environment EMISSIONS to water by source category from Waterbase; a different dataset and grain. Its specific job is the **WISE emissions to water**.

### The NexGen Signal family

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

- [EU Basin Pollutant Input Total Records — EEA WISE](https://apify.com/nexgensignal/eu-basin-pollutant-input-total-records)
- [EU Waterbody Pesticide Exceedance Records — EEA WISE](https://apify.com/nexgensignal/eu-waterbody-pesticide-exceedance-records)
- [EU Surface Water Failing Pollutant Records — EEA WISE](https://apify.com/nexgensignal/eu-surface-water-failing-pollutant-records)
- [EU Nitrate Monitoring Records — EEA](https://apify.com/nexgensignal/eu-nitrate-monitoring-records)
- [EU Waterbody Quality Records — EEA](https://apify.com/nexgensignal/eu-waterbody-quality-records)

*Source: European Environment Agency (EEA), WISE State of Environment (Waterbase) (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. River-basin / pollutant / source / period grain; free-text remarks excluded, no contact/operator/responsible-person field selected or emitted. No natural-person data of any kind. Values 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 period 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-water-emission-load-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-water-emission-load-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-water-emission-load-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-water-emission-load-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/VRvlvlN6R7eL5qe8b/builds/7Girkg2kviN8TRBW1/openapi.json