# EU Air Quality Measure Records — EEA AQ Plans (`nexgensignal/eu-air-quality-measure-records`) Actor

Keyless pay-per-record EEA air-quality plan measures — type, status, cost, timeline, impact. Partition by country; no person data. EEA acknowledge. GOLD $0.05 ladder.

- **URL**: https://apify.com/nexgensignal/eu-air-quality-measure-records.md
- **Developed by:** [NexGen Signal](https://apify.com/nexgensignal) (community)
- **Categories:** Business, 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 measure 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 Air Quality Measure Records — EEA AQ Plans

**Keyless. Pay per record. Every European air-quality remediation measure — type, status, cost, timeline — as one clean catalogue.**

This actor turns the **European Environment Agency (EEA) Air Quality e-Reporting** plan-measures dataset into clean, per-measure records — the remediation measures that member states apply under EU air-quality plans to bring polluted zones back into compliance. Each run reads the EEA's keyless DiscoData SQL service for the country you choose and delivers one row per measure: its code and name, description, classification and type, administration level and time scale, estimated and actual cost, implementation status and dates, expected emission reduction and concentration impact, the source sector and spatial scale, the air pollutant and protection target it addresses, and the zone and attainment it links to. Measure / type / status / cost / timeline grain, structured for engineering use, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

When a European air-quality zone exceeds a limit value, the member state reports an air-quality plan and the concrete measures it will take — a low-emission zone, a variable speed limit, a fuel-switch subsidy, a retrofit programme. The EEA collects those measures across Europe. This actor reads that dataset and flattens each measure into a single analysis-ready record: the measure code and name, its description, classification (traffic, industry, residential, and so on) and type, the administration level and time scale, the estimated and actual cost with currency, the implementation status and planned/actual start and end dates, the expected emission reduction and concentration/exceedance impact, the source sector and spatial scale, the air pollutant and protection target, and the zone and attainment identifiers. A measure is an **administrative action** — an organisation-level policy, never a person. Values are carried **verbatim** as published. You are billed only for records actually delivered.

### Who buys this and for what job

- **Environmental-policy, city, and consultancy teams** cataloguing the air-quality measures applied by country, sector, and pollutant.
- **Clean-air, transport, and ESG products** benchmarking measure types, costs, and expected impacts across Europe.
- **Researchers and NGOs** studying which remediation measures member states deploy and at what stage.
- **Data engineers** who want the AQ plan-measures catalogue as clean rows without writing SQL against the EEA service.

### 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. The data is a catalogue of reported policy measures as published — not a compliance verdict or an assessment of a measure's effectiveness.

### Measure grain — no person data

The unit of every record is a policy measure — an administrative action, never a person. The source carries **no contact or responsible-person field**, and this actor emits none: it selects only the structured measure attributes plus the measure name and description (which describe the action — a speed limit, a subsidy — not a person), and the free-text comment fields are excluded at field selection. A person-key guard runs on every record as a backstop, and the acceptance suite injects a responsible-person and contact field into a source row and asserts neither the key nor the value can ever appear in output.

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `measure_record` | $0.05 | $0.045 | $0.04 | $0.0335 |

Delivered before charged. Blocked runs and empty results cost nothing.

### A required partition — this is a multi-million-row dataset

The EEA plan-measures dataset holds **over 1.38 million 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. Optional `year` and `pollutant` filters narrow further, and `maxRecords` is the hard ceiling.

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `countryCode` | string | — | **Required** 2-letter country code (e.g. DE, FR, IT). |
| `year` | integer | — | Optional reporting year to filter. |
| `pollutant` | string | — | Optional air pollutant (e.g. NO2, PM10, PM2.5, O3). |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per measure. Real example (values as published):

```json
{
  "record_id": "MEA.AT_05_01",
  "measure_id": "MEA.AT_05_01",
  "code": "AT05_M01",
  "country": "Austria",
  "country_code": "AT",
  "reporting_year": 2014,
  "name": "Variable speed limit A10",
  "description": "Variable speed limit on motorway A10",
  "measure_classification": "traffic-speed",
  "measure_type": "integrated",
  "administration_level": "regional",
  "estimated_costs": 4500000.0,
  "currency": "EUR",
  "implementation_status": "implementation",
  "emission_reduction": 30.0,
  "impact_conc_delta": 2.5,
  "source_sector": "transport",
  "air_pollutant": "NO2",
  "protection_target": "Health",
  "source": "EEA Air Quality e-Reporting — plan measures",
  "licence": "European Environment Agency (EEA) ... provided the source is acknowledged ...",
  "disclaimer": "Air-quality remediation MEASURE records ... no contact or responsible-person field ...",
  "observed_at": "2026-08-22T00:00:00Z"
}
```

An unbilled `RUN_RECEIPT` records the robots check, the country/year/pollutant filters, rows seen and delivered, and whether charged equals delivered.

### Field reference

Each record is one measure. Identity: `record_id` / `measure_id`, `code`, and `aq_plan_id`. Scope: `country`, `country_code`, and `reporting_year`. Description: `name`, `description`, `measure_classification`, and `measure_type`. Delivery: `administration_level`, `time_scale`, `implementation_status`, `planned_implementation_beg`/`_end`, `actual_implementation_beg`/`_end`, and `full_effect_date`. Cost: `estimated_costs`, `actual_cost`, and `currency`. Expected effect: `emission_reduction`, `impact_conc_delta`, `impact_exceedance_delta`, and `implementation_indicators`. Target: `source_sector`, `spatial_scale`, `air_pollutant`, `protection_target`, `objective_type`, and `reporting_metric`. Links: `zone_id`, `attainment_id`, and `source_data_url`. 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 queries the plan-measures table through the DiscoData SQL service filtered to your `countryCode` (and optional `year` and `pollutant`), and flattens each measure to one record — selecting only the structured attributes and the measure name and description, never a contact or responsible-person field — 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 dataset spans the reporting countries, with **1.38 million+ measure rows** in total. Because each record carries the `country_code`, `measure_type`, `source_sector`, and `air_pollutant`, segmenting by country, measure type, sector, or pollutant is straightforward. Pull one country, or one pollutant within a country, to seed a measures table.

### Working with the catalogue

The catalogue is built to be compared, and the fields carry the structure to do it. The `measure_classification` and `measure_type` group measures into families — traffic, industry, residential heating — so an analyst can compare how different countries tackle the same pollutant. The `estimated_costs` and `actual_cost` sit alongside the `emission_reduction` and `impact_conc_delta`, so a cost-effectiveness view falls out of the same row, and the `implementation_status` with the planned and actual dates supports a delivery-tracking view across a plan's lifetime. Because the `air_pollutant` and `protection_target` travel on every measure, the catalogue joins cleanly to any zone- or attainment-keyed air-quality dataset, and two country pulls can be diffed to see which measures advanced between reporting rounds.

### Cost guidance

One `measure_record` per delivered measure: cost = measures delivered × your plan's per-record price. Scope with `countryCode`, `year`, or `pollutant`. 1,000 measures is **$50** (Free) / **$33.50** (Gold).

### Honest limitations

- **A catalogue, not a verdict.** These are reported policy measures as published — not a compliance judgment or an effectiveness assessment.
- **Partition required.** Every run must set a `countryCode`.
- **As published.** Costs, dates, and expected impacts are carried verbatim; this actor reformats, it does not audit.
- **No person data** of any kind.

### Differentiation

This is a **net-new** category for the NexGenData fleet — no existing fleet actor covers air-quality remediation measures. It is distinct from any monitoring or emissions cell (which carry pollutant readings or facility emissions, not the policy responses), and it is the measures companion to the fleet's air-quality **scenario** records. Its specific job is the **EEA air-quality plan-measures catalogue** — the remediation actions, measure by measure.

### The NexGen Signal family

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

- [EU Air Quality Scenario Records — EEA AQ Plans](https://apify.com/nexgensignal/eu-air-quality-scenario-records)
- [EU Industrial Emissions Records — EEA IED Facilities](https://apify.com/nexgensignal/eu-industrial-emissions-records)
- [EU GHG Inventory Records — EEA](https://apify.com/nexgensignal/eu-ghg-inventory-records)
- [EU Bathing Water Quality Records — EEA BWD](https://apify.com/nexgensignal/eu-bathing-water-quality-records)
- [EU Maritime Environmental Measure Records — WISE](https://apify.com/nexgensignal/eu-maritime-environmental-measure-records)

*Source: European Environment Agency (EEA), Air Quality e-Reporting — plan measures 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. Measure / type / status / cost / timeline grain; organisation-level policy actions, no contact or responsible-person field, no person data of any kind. Reported measures as published, not a compliance verdict.*

# Actor input Schema

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

REQUIRED 2-letter country code (e.g. DE, FR, IT) — the full measures table is a MONSTER and cannot be pulled unbounded.

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

Optional reporting year to filter.

## `pollutant` (type: `string`):

Optional air pollutant to filter (e.g. NO2, PM10, PM2.5, O3).

## `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-air-quality-measure-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-air-quality-measure-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-air-quality-measure-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-air-quality-measure-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/78Y3Pa8vPWZcma9az/builds/tf9KMNJotCTdmfrsN/openapi.json