# EU Bathing Water Monitoring Compliance Records — EEA (`nexgensignal/eu-bathing-water-monitoring-compliance-records`) Actor

Keyless pay-per-record EEA WISE Bathing Water Directive monitoring compliance — site, season and the calendar/sample-count/pre-season/continuous-monitoring flags, as filed. Site grain, no person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-bathing-water-monitoring-compliance-records.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** 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 bathing-water monitoring compliance 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 Bathing Water Monitoring Compliance Records — EEA

**Keyless. Pay per record. Did each European bathing water meet the Directive's monitoring rules this season?**

This actor turns the **European Environment Agency (EEA) WISE Bathing Water Directive (BWD) database** into clean, per-record data — whether each official bathing-water site met the Directive's monitoring requirements in a season: the monitoring calendar, the minimum sample count, the pre-season sample, and continuous monitoring. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per site-season, structured for compliance and public-health analysis, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

The Bathing Water Directive does not only classify water quality — it also checks whether each site was monitored properly: enough samples, at the right intervals, with a pre-season sample, without unreported gaps. This actor reads that monitoring-compliance assessment and delivers one record per site-season: the bathing-water identifier, country and season, and the full set of compliance FLAGS — reported data, continuous monitoring, maximum interval between samples, minimum number of samples, pre-season sample, and abnormal-situation and inaccessibility flags — all carried as filed. It is the monitoring-compliance layer of Europe's bathing-water reporting.

### Who buys this and for what job

- **Public-health and tourism analysts** checking whether the sites they rely on were properly monitored.
- **Compliance and audit teams** finding site-seasons that missed the monitoring calendar or sample minimum.
- **Environmental researchers** studying monitoring-quality patterns across countries and seasons.
- **Data engineers** who want the BWD monitoring-compliance 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 compliance flags as filed — not a verdict of this actor's making.

### Site grain — no person data

The unit of every record is a monitoring-compliance assessment for a bathing-water site in a season — a site code and a set of flags, never a person. BWD reporting is at site level: there is **no contact or named-individual field** in the selected columns, and none is emitted. The bathing-water identifier is a site code, never a person. The free-text manual-classification reason is **EXCLUDED at field selection**. A person-key guard runs on every record as a backstop.

### A note on scale, honestly

The source table holds **87,659 rows** as verified by an exact `COUNT(*)` at build time. The planning index for this category was 87,538; the live count above is slightly higher and is the authoritative figure. It spans reporting countries, sites and seasons. This is the real, populated table for this category.

### Sample output

![Sample output — EU Bathing Water Monitoring Compliance Records — EEA](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-bathing-water-monitoring-compliance-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": "AL101:2021",
  "bathing_water_identifier": "AL101",
  "country_code": "AL",
  "season": 2021,
  "has_reported_data": true,
  "has_continuously_monitored": true,
  "has_been_inaccessible": false,
  "has_been_newly_identified": false,
  "has_met_maximum_interval_between_samples": true,
  "has_minimum_number_of_samples": true,
  "has_minimum_number_of_samples_last_period": true,
  "has_pre_season_sample": false,
  "has_abnormal_situation_season_start": false,
  "has_abnormal_situation_insufficient_interval": false,
  "has_inaccessibility_season_start": false,
  "has_inaccessibility_insufficient_interval": false,
  "has_quality_changes_season_start": false,
  "has_quality_changes_insufficient_interval": false,
  "has_quality_changes_last_period": false,
  "source_uid": "10814460",
  "source": "EEA WISE Bathing Water Directive (BWD) — bathing-water monitoring compliance assessment",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) WISE Bathing Water Directive (BWD) reporting. 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 Bathing Water Directive (BWD) database (discodata.eea.europa.eu).",
  "disclaimer": "Whether each official European bathing-water site met the Bathing Water Directive monitoring requirements in a season — the monitoring calendar, minimum sample count, pre-season sample and continuous-monitoring tests — at bathing-water / season grain from the EEA WISE BWD database. Each record carries the bathing-water identifier, country and season, and the full set of compliance FLAGS (reported data, continuous monitoring, maximum interval between samples, minimum number of samples, pre-season sample, abnormal-situation and inaccessibility flags) VERBATIM. The free-text manual-classification reason is EXCLUDED at field selection. Site grain — the identifier is a bathing-water site code, never a person; no contact or named-individual field is selected or emitted, and a person-key guard runs on every record.",
  "observed_at": "2026-09-25T17:31:30Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `bathing_water_monitoring_compliance_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 bathing season year to filter (e.g. 2021, 2022). |
| `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 site-season. Representative example (values as reported):

```json
{
  "record_id": "AL101:2021",
  "bathing_water_identifier": "AL101",
  "country_code": "AL",
  "season": 2021,
  "has_reported_data": true,
  "has_continuously_monitored": true,
  "has_met_maximum_interval_between_samples": true,
  "has_minimum_number_of_samples": true,
  "has_pre_season_sample": false,
  "source": "EEA WISE Bathing Water Directive (BWD) — bathing-water monitoring compliance assessment",
  "observed_at": "2026-08-27T00: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-season compliance assessment. Identity: `record_id`, `bathing_water_identifier`, `country_code`, `season`, and `source_uid`. Compliance flags: `has_reported_data`, `has_continuously_monitored`, `has_been_inaccessible`, `has_been_newly_identified`, `has_met_maximum_interval_between_samples`, `has_minimum_number_of_samples`, `has_minimum_number_of_samples_last_period`, `has_pre_season_sample`, and the abnormal-situation, inaccessibility and quality-change flags for season start, insufficient interval, and the last assessment period. 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 BWD monitoring-compliance table (filtered to your optional `countryCode` and season `year`), ordered by the high-cardinality bathing-water identifier, and flattens each row to one record — carrying every flag **verbatim**, never anything person-shaped and never the free-text reason — 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 **87,659 rows** across reporting countries, bathing-water sites, and seasons. Because each record carries the `country_code`, the `bathing_water_identifier`, and the `season`, segmenting by country, site or season is straightforward. Pull one country, one season, or the whole table to seed a bathing-water warehouse.

### Working with the data

The flags are a compliance layer, and they make audit trivial. Because every record is a set of booleans for one site-season, an analyst can filter to the site-seasons that failed the minimum-sample or maximum-interval test, count monitoring gaps by country, and — joined to the quality cell on the identifier — separate a poor classification caused by genuine pollution from one caused by inadequate monitoring.

### Cost guidance

One `bathing_water_monitoring_compliance_record` per delivered row: cost = rows delivered × your plan's per-record price. Scope with `countryCode` and `year`. 1,000 rows is **$50** (Free) / **$33.50** (Gold).

### Honest limitations

- **As reported.** Compliance flags are as filed by member states; this actor reformats, it does not audit or recompute.
- **Flags carried verbatim.** The source mixes boolean and 0/1 flags; both are carried as filed rather than normalised.
- **Monitoring, not quality.** This is the monitoring-compliance record; the water-quality classification lives in the sibling quality cell.
- **Acknowledge the EEA**, and note there is **no person data** of any kind.

### Differentiation

It is the MONITORING-COMPLIANCE grain, a distinct source table from the live **eu-bathing-water-quality-records** (the water-quality classification) — this cell answers whether a site was monitored properly, not how clean the water was. Its specific job is the **BWD monitoring-compliance assessment**.

### The NexGen Signal family

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

- [EU Bathing Water Quality Records — EEA](https://apify.com/nexgensignal/eu-bathing-water-quality-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)
- [EU Surface Water Priority Substance Records — EEA](https://apify.com/nexgensignal/eu-surface-water-priority-substance-records)
- [EU Wastewater Compliance Records — EEA UWWTD](https://apify.com/nexgensignal/eu-wastewater-compliance-records)

*Source: European Environment Agency (EEA), WISE Bathing Water Directive (BWD) database (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. Site grain; the bathing-water identifier is a site code, not a person; no contact or named-individual field is selected or emitted, no natural-person data of any kind. Reported compliance flags as filed, not a verdict.*

# Actor input Schema

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

Optional 2-letter country code (e.g. DE, FR).

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

Optional bathing season year to filter (e.g. 2021, 2022).

## `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-bathing-water-monitoring-compliance-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-bathing-water-monitoring-compliance-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-bathing-water-monitoring-compliance-records --silent --output-dataset

```

## MCP server setup

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