# EU Bathing Water Quality Records — EEA BWD (`nexgensignal/eu-bathing-water-quality-records`) Actor

Keyless, pay-per-record EEA Bathing Water Directive data. One row per site per season — identifier, country, zone type, and quality classification carried verbatim (incl. not-classified). Partition required (country); EEA acknowledge; no person data.

- **URL**: https://apify.com/nexgensignal/eu-bathing-water-quality-records.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** Business, Developer tools, Travel
- **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 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 Quality Records — EEA BWD

**Keyless. Pay per record. Every European bathing site's official water-quality classification, season by season.**

This actor turns the **European Environment Agency (EEA)** Bathing Water Directive (BWD) dataset into clean, per-site-season records — the official record of how each designated bathing water in Europe was classified each year. Each run reads the EEA's keyless DiscoData SQL service for the country you choose and delivers one row per bathing site per season: the site identifier, the country, the zone type, the season, and the quality classification — carried exactly as published, including the "not classified" and "not sufficiently sampled" values. Site-period-quality grain, structured for engineering use, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

Under the Bathing Water Directive, member states classify every designated bathing water — coastal and inland — each season, and the EEA aggregates and publishes the result. This actor reads that register and flattens each site-season assessment into a single analysis-ready record: the bathing-water identifier, the country, the specialised zone type (coastal or inland lake/river), the season year, the monitoring-calendar and management indicators, and the two classification fields — the original classification and the harmonised quality label. Classification labels are carried **verbatim**, including the honest "0 - Not classified", "0 - Missing data", and "not sufficiently sampled" states — never upgraded to a settled quality. Values are exactly as published. You are billed only for records actually delivered.

### Who buys this and for what job

- **Travel, tourism, and property products** surfacing bathing-water quality by site and year for coastal and lakeside locations.
- **Environmental-research and public-health teams** studying bathing-water quality trends across Europe over time.
- **ESG and destination-analytics tools** scoring regions on water quality across seasons.
- **Data engineers** who want the BWD classification history as clean rows without writing SQL against the EEA service or paging a very large table.

### 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 a classification register as reported by member states — not a real-time swimming advisory. A site classified for a past season says nothing about water quality today.

### Site-period grain — no person data

The unit of every record is a bathing site in a given season. The register carries no natural-person fields, and this actor emits none; a person-key guard runs on every record as a pure backstop. The site identifier, zone type, season, and classification labels are the entire payload.

### A required partition — this is a 679,622-row dataset

The full classification history runs to **over 679,000 site-season rows**, so this actor **requires a partition**: every run must set a 2-letter `countryCode`. A run with no country is rejected in code before any work begins — the whole table cannot be pulled unbounded. An optional `season` narrows further, and `maxRecords` is the hard ceiling. One country's full history is typically a few thousand to tens of thousands of rows.

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `bathing_water_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 member-state code (e.g. ES, FR, IT). |
| `season` | integer | — | Optional bathing season / year to filter (e.g. 2023). |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per site-season assessment. Real example (values as published):

```json
{
  "record_id": "ES511:2023",
  "bathing_water_identifier": "ES511",
  "country_code": "ES",
  "season": 2023,
  "specialised_zone_type": "coastalBathingWater",
  "quality_original_classification": "E - Excellent",
  "quality": "1 - Excellent",
  "source": "European Environment Agency (EEA) Bathing Water Directive",
  "licence": "European Environment Agency (EEA) ... provided the source is acknowledged ...",
  "disclaimer": "Bathing-water quality-classification records ... labels are carried VERBATIM, including 'Not classified' ...",
  "observed_at": "2026-08-22T00:00:00Z"
}
```

An unbilled `RUN_RECEIPT` records the robots check, the country and season, rows seen and delivered, and whether charged equals delivered.

### Field reference

Each record is one site-season assessment. Identity: `record_id` (site id + season), `bathing_water_identifier`, `country_code`, and `season`. Character: `specialised_zone_type`, `reported_specialised_zone_type`, `monitoring_calendar`, and `management`. Classification (verbatim): `quality_original_classification` and `quality`. Reference: `uid`. Provenance: `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 bathing-water status table through the DiscoData SQL service, bounding the query to your `countryCode` (and optional `season`), and pages through the results. Each site-season is flattened to one record — carrying the classification labels **verbatim**, never upgrading a "not classified" or "not sufficiently sampled" to a settled quality — 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 classification history holds **over 679,000 site-season rows** across all reporting countries and seasons since the 1990s. A partition is required precisely because of that scale: one country's full history is a bounded, affordable pull, and a single `season` isolates one year. Because each record carries the `bathing_water_identifier` and `season`, a site's multi-year quality trajectory reconstructs by a simple join.

### Cost guidance

One `bathing_water_record` per delivered assessment: cost = rows delivered × your plan's per-record price. Always scope with `countryCode` and optionally `season`. 1,000 assessments is **$50** (Free) / **$33.50** (Gold). One country-season is typically a few hundred to a couple of thousand rows.

### Honest limitations

- **A classification register, not a live advisory.** These are season classifications as reported — not a real-time swimming-safety reading.
- **Partition required.** Every run must set a `countryCode`; the whole table cannot be pulled unbounded.
- **Verbatim labels.** "Not classified", "Missing data", and "not sufficiently sampled" are carried exactly as published and never upgraded.
- **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 — no existing fleet actor covers bathing-water quality. It is distinct from the fleet's other EEA water cells (waste-water treatment compliance and water-body determinand observations carry facility or chemistry data, not the bathing-water classification) and from any emissions cell. Its specific job is the **EEA Bathing Water Directive classification history** — site by site, season by season.

### The NexGen Signal family

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

- [EU Wastewater Compliance Records — EEA UWWTD](https://apify.com/nexgensignal/eu-wastewater-compliance-records)
- [EU Waterbody Quality Records — EEA WISE Waterbase](https://apify.com/nexgensignal/eu-waterbody-quality-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)
- [England Flood Station Records — EA Monitoring](https://apify.com/nexgensignal/england-flood-station-records)

*Source: European Environment Agency (EEA), Bathing Water Directive (BWD) 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. Classification register, not a real-time advisory; labels carried verbatim. Site-period grain; no person data of any kind.*

# Actor input Schema

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

REQUIRED 2-letter member-state code (e.g. ES, FR, IT). The full 679,622-row table cannot be pulled unbounded.

## `season` (type: `integer`):

Optional bathing season/year to filter (e.g. 2023).

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

Maximum records delivered and billed.

## Actor input object example

```json
{
  "countryCode": "ES",
  "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": "ES",
    "maxRecords": 500
};

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

# Run the Actor and wait for it to finish
run = client.actor("nexgensignal/eu-bathing-water-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 '{
  "countryCode": "ES",
  "maxRecords": 500
}' |
apify call nexgensignal/eu-bathing-water-quality-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-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/85u4wdBQsnIunyBkp/builds/M3XYbqvCavSDN61ec/openapi.json