# EU Water Monitoring Parameter Schedule Records — EEA WISE (`nexgensignal/eu-water-monitoring-parameter-schedule-records`) Actor

Keyless pay-per-record EEA WISE WFD monitoring schedules — site, parameter, monitoring roles, matrix, frequency, cycle, last-monitored year, verbatim. Schedule topology not values. Required country partition. No person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-water-monitoring-parameter-schedule-records.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** Business, Developer tools, Other
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $33.50 / 1,000 monitoring schedule 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?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## EU Water Monitoring Parameter Schedule Records — EEA WISE

**Keyless. Pay per record. Which parameters each official European monitoring site is scheduled to test — role, frequency, cycle, and last-monitored year.**

This actor turns the **European Environment Agency (EEA) WISE Water Framework Directive (WFD) monitoring programme** into clean, per-record data — the monitoring schedules of Europe's official water-monitoring sites: which parameters each site is set up to test, and how. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per schedule row, structured for monitoring-network 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 their monitoring programmes — which sites monitor which parameters, for which purpose, and how often. This actor reads that monitoring table and delivers one record per site-parameter schedule line: the country, river basin, water body, and monitoring site; the monitoring roles the site plays (ecological, chemical, quantitative, investigative, operational, surveillance); the parameter, matrix, and purpose; and the frequency, cycle, and last-monitored year — all carried verbatim. It is the monitoring SCHEDULE topology, not the measured values.

### Who buys this and for what job

- **Monitoring-network analysts mapping which parameters are scheduled where and how often across Europe**
- **Water-management and consultancy teams auditing monitoring coverage by parameter and site**
- **Researchers studying the design and frequency of national water-monitoring programmes**
- **Data engineers** who want the WISE WFD monitoring schedule 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.

### Monitoring-site grain — no person data

The unit of every record is a site-parameter schedule line — a monitoring site and a scheduled parameter, never a person. The monitoring site name is a location/facility label; 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. The `file_url` points to the official Eionet/CDR reporting file, never a person.

### A required partition — this is a large dataset

The table holds **5,847,200 rows**, so this actor **requires a partition**: every run must set a `countryCode`. The country bounds the run; there is no unbounded all-Europe pull. An optional `year` filter narrows further, and `maxRecords` is the hard ceiling.

### A note on scale, honestly

The source table (`Monitoring_MonitoringSite_ChemicalEcologicalQuantitativeMonitoring`) holds **5,847,200 rows** as verified by an exact `COUNT(*)` at build time — a genuine MONSTER carrying the 2016 and 2022 reporting cycles. This is why the run requires a `countryCode` partition; the live count is authoritative.

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `monitoring_schedule_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 | — | REQUIRED 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 schedule row. Real example (values as reported):

```json
{
  "record_id": "AT359182:Nitrate:2022",
  "reporting_year": 2022,
  "country_code": "AT",
  "country_name": "Austria",
  "eu_rbd_code": "AT1000",
  "rbd_name": "DANUBE",
  "water_body_code": "ATGK100001",
  "monitoring_site_name": "Example Site",
  "eu_monitoring_site_code": "AT359182",
  "quantitative_monitoring": "Yes",
  "surveillance_monitoring": "Yes",
  "parameter_code": "Nitrate",
  "chemical_matrix": "Water",
  "frequency": "12",
  "cycle": "Annual",
  "last_monitored": "2021",
  "source": "EEA WISE Water Framework Directive (WFD) \u2014 monitoring site parameter schedule",
  "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 site-parameter schedule line. Identity: `record_id`, `country_code`, `country_name`, `eu_rbd_code`, `rbd_name`, `water_body_code`, `water_body_name`, `water_body_category`, `monitoring_site_name`, `eu_monitoring_site_code`, and `reporting_year`. Roles: `ecological_monitoring`, `chemical_monitoring`, `quantitative_monitoring`, `investigative_monitoring`, `operational_monitoring`, and `surveillance_monitoring`. Schedule: `parameter_code`, `parameter_other`, `chemical_matrix`, `chemical_purpose`, `frequency`, `cycle`, and `last_monitored`. Plus `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 monitoring schedule table, 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 **5,847,200 rows**. Because each record carries the `country_code`, `eu_monitoring_site_code`, `parameter_code`, and `reporting_year`, segmenting is straightforward. Pull one slice, or the whole table to seed a warehouse.

### Working with the data

The schedules are a network map, and the fields make them auditable. Because every record pairs a `parameter_code` with a `frequency`, `cycle`, and the site's monitoring roles, an analyst can see which parameters are monitored most intensively, which sites carry surveillance vs operational monitoring, and where a parameter is scheduled at all. The `last_monitored` year flags stale schedules, and the `reporting_year` lets the 2016 and 2022 programmes be compared.

### Identifiers and joins

Every record carries the `eu_monitoring_site_code` and `water_body_code`, keying each schedule line to its water body across the fleet's other WISE cells — the water-body status, the failing pollutants, the exemptions — so a buyer can line up what a site is scheduled to measure against what its water body actually reports, on shared identifiers rather than a fuzzy name match.

### Cost guidance

One `monitoring_schedule_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; this actor reformats, it does not audit or recompute.
- **A label, not a verdict.** These are reported classifications/schedules/linkages, not an independent compliance assessment.
- **Acknowledge the EEA.** The acknowledgement travels on every record.
- **No person data** of any kind.

### Differentiation

This is a **net-new** category for the NexGenData fleet. It is distinct from **eu-nitrate-monitoring-records** and **eu-pesticide-water-monitoring-records**, which deliver measured VALUES; this cell delivers the monitoring SCHEDULE topology (what is planned to be tested, where, and how often), not the measurements. It differs entirely from the status and exemption cells. Its specific job is the **WFD monitoring-site parameter schedule**.

### The NexGen Signal family

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

- [EU Water Monitoring Parameter Schedule Records — EEA WISE](https://apify.com/nexgensignal/eu-water-monitoring-parameter-schedule-records)
- [EU Surface Water Ecological Exemption Records — EEA WISE](https://apify.com/nexgensignal/eu-surface-water-ecological-exemption-records)
- [EU Waterbody Pesticide Exceedance Records — EEA WISE](https://apify.com/nexgensignal/eu-waterbody-pesticide-exceedance-records)
- [EU Waterbody Quality Records — EEA](https://apify.com/nexgensignal/eu-waterbody-quality-records)
- [EU Nitrate Monitoring Records — EEA](https://apify.com/nexgensignal/eu-nitrate-monitoring-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. Monitoring-site / parameter / cycle grain; the site name is a location label, 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`):

REQUIRED 2-letter country code (e.g. DE, FR) — this table is large and cannot be pulled unbounded.

## `year` (type: `integer`):

Optional reporting cycle year to filter.

## `maxRecords` (type: `integer`):

Maximum records delivered and billed.

## Actor input object example

```json
{
  "countryCode": "DE",
  "maxRecords": 500
}
```

# 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 = {
    "countryCode": "DE",
    "maxRecords": 500
};

// Run the Actor and wait for it to finish
const run = await client.actor("nexgensignal/eu-water-monitoring-parameter-schedule-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 = {
    "countryCode": "DE",
    "maxRecords": 500,
}

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/eu-water-monitoring-parameter-schedule-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 '{
  "countryCode": "DE",
  "maxRecords": 500
}' |
apify call nexgensignal/eu-water-monitoring-parameter-schedule-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-water-monitoring-parameter-schedule-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/0K7C6CMEZktqUnWZI/builds/XJZbWLOWpdag3xLeq/openapi.json