# EU Wastewater Compliance Records — EEA UWWTD (`nexgensignal/eu-wastewater-compliance-records`) Actor Keyless, pay-per-record EEA UWWTD data. One row per treatment plant — code, name, country, capacity, treatment stages, nutrient removal, BOD5/COD/TSS/N/P performance flags. Facility grain; EEA acknowledge; no person data. - **URL**: https://apify.com/nexgensignal/eu-wastewater-compliance-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 treatment plant 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 Wastewater Compliance Records — EEA UWWTD **Keyless. Pay per record. Every urban waste-water treatment plant in Europe, with its treatment and compliance data.** This actor turns the **European Environment Agency (EEA)** Urban Waste Water Treatment Directive (UWWTD) dataset into clean, per-plant records — the register of urban waste-water treatment plants that member states report under the Directive. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per treatment plant: its code and name, the country and location, the collecting system, the incoming load and capacity, the treatment stages applied, the nutrient-removal and disinfection steps, and the per-parameter performance flags. Facility / treatment 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 Urban Waste Water Treatment Directive, member states report every urban waste-water treatment plant, and the EEA aggregates and publishes the result. This actor reads that register and flattens each treatment plant into a single analysis-ready record: the plant code and name, the country and NUTS region, the coordinates, the collecting-system type, the load entering the plant and its design capacity in population equivalents, which treatment stages it applies (primary, secondary, other), whether it does nitrogen and phosphorus removal and UV / chlorination / ozonation / filtration, the compliance-performance flags for BOD5, COD, TSS, and total N and P, and the waste-water treated and reused figures. It is the facility-level compliance layer of Europe's waste-water infrastructure. Values are exactly as reported. You are billed only for records actually delivered. ### Who buys this and for what job - **Environmental-compliance, water-utility, and infrastructure teams** mapping treatment plants by country, capacity, treatment level, and compliance performance. - **ESG and due-diligence products** assessing waste-water treatment coverage and performance across a region or operator footprint. - **Researchers and NGOs** studying treatment levels, nutrient removal, and compliance across the EU. - **Data engineers** who want the UWWTD plant register as clean rows without writing SQL against the EEA service or paging a 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 single record. The data is treatment-plant compliance data as reported by member states — not a compliance verdict, an enforcement action, or a real-time reading. ### Facility grain — no person data This actor works at facility/treatment grain: the unit of every record is a treatment plant. The plant name (`plant_name`) is a **facility** name, not a person, and the dataset carries no natural-person fields; this actor emits none. A person-key guard runs on every record as a pure backstop. The plant, its location, its treatment configuration, and its performance flags are the entire payload. ### Sample output ![Sample output — EU Wastewater Compliance Records — EEA UWWTD](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-wastewater-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": "ATTP_1-00000001", "plant_code": "ATTP_1-00000001", "plant_name": "Andau", "country_code": "AT", "agglomeration_code": "ATAG_1-00000001", "nuts_code": "AT112", "latitude": 47.7786670957, "longitude": 17.0491364742, "collecting_system": "ISCON", "load_entering_pe": 4963, "capacity_pe": 13500, "primary_treatment": "True", "secondary_treatment": "True", "other_treatment": "True", "n_removal": "True", "p_removal": "True", "uv": "False", "chlorination": "False", "ozonation": "False", "sand_filtration": "False", "micro_filtration": "False", "bod5_performance": "P", "cod_performance": "P", "tss_performance": "NR", "n_total_performance": "NR", "p_total_performance": "NR", "bad_performance": null, "waste_water_treated": "302591.0", "waste_water_reuse": null, "specification": null, "begin_life": "2006-12-31", "end_life": null, "inspire_id_facility": null, "source": "European Environment Agency (EEA) UWWTD", "source_url": "https://discodata.eea.europa.eu/", "licence": "European Environment Agency (EEA) Urban Waste Water Treatment Directive (UWWTD) data. 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), Urban Waste Water Treatment Directive (UWWTD) dataset.", "disclaimer": "Urban waste-water treatment-plant compliance records as reported by member states under the UWWTD and published by the EEA. Facility/treatment grain — no natural-person data. Treatment types, capacity, load, and performance values are as reported; not a compliance verdict or an enforcement action.", "observed_at": "2026-09-25T17:34:40Z" } ``` ### Pricing | Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond | |-------|-----------|--------|--------|---------------------------| | `treatment_plant_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 member-state code (e.g. DE, FR, IT). | | `treatedOnly` | boolean | false | Keep only plants that report waste water treated. | | `maxRecords` | integer | 500 | Ceiling on records delivered and billed. | ### Output One JSON object per treatment plant. Real example (values as reported): ```json { "record_id": "DEAG_NW222958", "plant_code": "DEAG_NW222958", "plant_name": "Tecklenburg-Ledde", "country_code": "DE", "nuts_code": "DEA37", "latitude": 52.2425, "longitude": 7.80564, "collecting_system": "ISCON", "capacity_pe": 8000, "primary_treatment": "Y", "secondary_treatment": "Y", "n_removal": "Y", "p_removal": "Y", "bod5_performance": "Y", "bad_performance": "N", "source": "European Environment Agency (EEA) UWWTD", "licence": "European Environment Agency (EEA) ... provided the source is acknowledged ...", "disclaimer": "Urban waste-water treatment-plant compliance records ... facility/treatment grain — no natural-person data ...", "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 treatment plant. Identity: `record_id` / `plant_code`, `plant_name`, `country_code`, `agglomeration_code`, `nuts_code`, and `inspire_id_facility`. Location: `latitude` and `longitude`. Capacity and load: `collecting_system`, `load_entering_pe`, and `capacity_pe` (population equivalents). Treatment configuration: `primary_treatment`, `secondary_treatment`, `other_treatment`, `n_removal`, `p_removal`, `uv`, `chlorination`, `ozonation`, `sand_filtration`, and `micro_filtration`. Compliance performance: `bod5_performance`, `cod_performance`, `tss_performance`, `n_total_performance`, `p_total_performance`, and `bad_performance`. Throughput: `waste_water_treated` and `waste_water_reuse`. Lifecycle: `specification`, `begin_life`, and `end_life`. 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 UWWTD treatment-plant table through the DiscoData SQL service, pushing your optional `countryCode` and `treatedOnly` filters into the query so the dataset is bounded server-side, and pages through the results. Each plant is flattened to one record — reading only facility, treatment, and performance fields, never a person — 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 UWWTD treatment-plant table holds on the order of **26,000+ plants** across reporting member states. Because each record carries `country_code`, `nuts_code`, and the treatment and performance flags, segmenting by country or region and filtering by treatment level or compliance is straightforward. Pass a `countryCode` to scope to one country (recommended for a focused view), or pull the whole table to build a Europe-wide treatment-compliance map. ### Cost guidance One `treatment_plant_record` per delivered plant: cost = plants delivered × your plan's per-record price. Scope with `countryCode` to keep runs bounded — one country is typically a few hundred to a few thousand plants. 1,000 plants is **$50** (Free) / **$33.50** (Gold); the whole ~26,000-plant table is a one-time seed you then keep fresh with small country pulls. ### Honest limitations - **Compliance data, not a verdict.** These are treatment-plant records as reported by member states — not a compliance judgment, an enforcement action, or a penalty. - **As reported.** Treatment configuration and performance flags are exactly as the EEA distributes them; this actor reformats, it does not recompute or audit. - **Acknowledge the EEA.** Reuse requires acknowledging the EEA as the source; the acknowledgement travels on every record. - **No person data** of any kind. ### Differentiation Critically, it is distinct from the fleet's **Eurostat waste-statistics cells** (waste generation and waste treatment), which carry **statistical aggregates** by country and category — this actor carries **facility-level compliance records**, plant by plant, with the treatment configuration and per-parameter performance. Aggregates answer "how much waste, by country"; this answers "which plant, at what capacity, treating to what level, compliant on which parameters." It is also distinct from the fleet's industrial-emissions facility register (IED installations ≠ waste-water plants). ### The NexGen Signal family Part of the NexGen Signal family of pay-per-record data products: - [EU Industrial Emissions Records — EEA IED Facilities](https://apify.com/nexgensignal/eu-industrial-emissions-records) - [EU Vehicle CO2 Records — EEA New-Car Monitoring](https://apify.com/nexgensignal/eu-vehicle-co2-records) - [EU Regulatory Change Records — CELLAR](https://apify.com/nexgensignal/eu-regulatory-change-records) - [Air Quality Monitor Records — US EPA AQS](https://apify.com/nexgensignal/air-quality-monitor-records) - [EPA Facility Compliance Records — Envirofacts](https://apify.com/nexgensignal/epa-facility-compliance-records) *Source: European Environment Agency (EEA), Urban Waste Water Treatment Directive (UWWTD) 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. Facility/treatment compliance data, not a compliance verdict. Facility grain; no person data of any kind.* # Actor input Schema ## `countryCode` (type: `string`): Optional 2-letter member-state code (e.g. DE, FR, IT). ## `treatedOnly` (type: `boolean`): Keep only plants that report waste water treated. ## `maxRecords` (type: `integer`): Maximum records delivered and billed. ## Actor input object example ```json { "treatedOnly": false, "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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "maxRecords": 10 }; // Run the Actor and wait for it to finish const run = await client.actor("nexgensignal/eu-wastewater-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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "maxRecords": 10 } # Run the Actor and wait for it to finish run = client.actor("nexgensignal/eu-wastewater-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-wastewater-compliance-records --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-wastewater-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 ` 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/Zf2i4bBXFlSa6fVqU/builds/fkVQxw0BHbwDa0uEX/openapi.json