# EU Air Quality Station Statistic Records — EEA (`nexgensignal/eu-air-quality-station-statistic-records`) Actor

Keyless pay-per-record EEA air-quality station statistics — station, pollutant, aggregation, pollution level and unit in source units, coverage/verification flags, verbatim. Required country partition. No person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-air-quality-station-statistic-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 aq station statistic 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 Air Quality Station Statistic Records — EEA

**Keyless. Pay per record. Every annual air-quality statistic for Europe's monitoring stations — pollutant, level, and unit, verbatim.**

This actor turns the **European Environment Agency (EEA) Air Quality e-Reporting dataflows** into clean, per-record data — the annual air-quality statistics reported for Europe's monitoring stations. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per station statistic, structured for air-quality and environmental-health analysis, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

Under the EU Air Quality Directives, member states report annual statistics for each monitoring station and pollutant. This actor reads that station-statistics dataflow and delivers one record per station / pollutant / year / aggregation: the country and monitoring station (network, EoI code, name, type, area, and coordinates), the pollutant, the data-aggregation process (annual mean, days above a threshold, and so on), the reporting and statistics year, and the AIR POLLUTION LEVEL and its UNIT in the source units verbatim, plus data-coverage, capture, and verification flags. It is the measured-statistics layer of Europe's air-quality network.

### Who buys this and for what job

- **Air-quality analysts and environmental-health teams tracking pollutant levels by station across Europe**
- **Modelling and forecasting products calibrating against official station statistics**
- **Researchers and journalists building air-quality time series by station and pollutant**
- **Data engineers** who want the air-quality station statistics 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.

### Station grain — no person data

The unit of every record is a station-pollutant-year statistic — a monitoring station and a measured value, never a person. The station coordinates are an asset location; 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.

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

The table holds **6,482,701 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.

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `aq_station_statistic_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 year to filter. |
| `maxRecords` | integer | 500 | Ceiling on records delivered and billed. |

### Output

One JSON object per station statistic. Real example (values as reported):

```json
{
  "record_id": "AL0203A:SO2:Annual mean:2019",
  "country": "Albania",
  "country_code": "AL",
  "aq_station_name": "Example Station",
  "air_quality_station_eoi_code": "AL0203A",
  "air_pollutant": "SO2",
  "data_aggregation_process": "Annual mean",
  "year_of_statistics": 2019,
  "reporting_year": 2020,
  "air_pollution_level": 12.3,
  "unit_of_air_pollution_level": "ug/m3",
  "air_quality_station_type": "Background",
  "air_quality_station_area": "urban",
  "latitude": 40.61,
  "longitude": 20.78,
  "source": "EEA Air Quality e-Reporting \u2014 annual station statistics",
  "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 station statistic. Identity: `record_id`, `country`, `country_code`, `air_quality_network_name`, `air_quality_station`, `air_quality_station_eoi_code`, `aq_station_name`, `air_quality_station_type`, `air_quality_station_area`, `longitude`, `latitude`, `altitude`, and `city`. Measurement: `air_pollutant`, `air_pollutant_code`, `air_pollutant_group`, `data_aggregation_process`, `year_of_statistics`, `reporting_year`, `air_pollution_level`, `unit_of_air_pollution_level`, `data_coverage`, `data_capture`, `verification`, and `observation_frequency`. 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 air-quality station statistics table (filtered to your required `countryCode` and optional `year`), 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 **6,482,701 rows**. Because each record carries the `country_code`, `air_quality_station_eoi_code`, `air_pollutant`, and `reporting_year`, segmenting is straightforward. Pull one slice, or the whole table to seed a warehouse.

### Working with the data

The statistics are a measured record, and the fields make them analysable. Because every record pairs an `air_pollutant` with an `air_pollution_level` and `unit_of_air_pollution_level` for a `data_aggregation_process`, an analyst can build a station's pollutant time series without unit-guessing, and the `data_coverage`/`data_capture`/`verification` flags travel so weak or unverified statistics can be filtered rather than silently trusted. The station type and area classify urban vs background sites.

### Identifiers and joins

Every record carries the `air_quality_station_eoi_code` and coordinates, so statistics join to the fleet's air-quality assessment-regime and method cells (via zone/pollutant) and map cleanly against any spatial layer, on stable station identifiers rather than a fuzzy name match.

### Why the flags matter

Air-quality statistics are only as good as their coverage. A station's annual mean built from 40% data capture is not comparable to one built from 95%, and an unverified value may be revised. This actor carries `data_coverage`, `data_capture`, and `verification` on every record precisely so a downstream consumer can set a quality bar — filter to verified statistics above a coverage threshold — rather than treating every reported number as equally solid. The `observation_frequency` and `data_aggregation_process` complete the picture, telling you what was measured and how it was rolled up, so two stations are only compared on a like-for-like basis.

### Cost guidance

One `aq_station_statistic_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 thresholds are as filed; this actor reformats, it does not audit or recompute.
- **A label, not a verdict.** These are reported statistics/regimes/volumes/loads, 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-air-quality-measure-records** and **eu-air-quality-scenario-records** (which carry planned MEASURES and projection SCENARIOS) and from **air-quality-monitor-records** (a different monitoring source) — this cell carries the annual measured STATION STATISTICS. Its specific job is the **EU air-quality station statistics**.

### The NexGen Signal family

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

- [EU Air Quality Assessment Method Records — EEA](https://apify.com/nexgensignal/eu-air-quality-assessment-method-records)
- [EU Air Quality Assessment Regime Records — EEA](https://apify.com/nexgensignal/eu-air-quality-assessment-regime-records)
- [EU Air Quality Measure Records — EEA](https://apify.com/nexgensignal/eu-air-quality-measure-records)
- [EU Air Quality Scenario Records — EEA](https://apify.com/nexgensignal/eu-air-quality-scenario-records)
- [Air Quality Monitor Records](https://apify.com/nexgensignal/air-quality-monitor-records)

*Source: European Environment Agency (EEA), Air Quality e-Reporting dataflows (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. Station / pollutant / year / aggregation grain; station coordinates are an asset location, 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 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-air-quality-station-statistic-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-station-statistic-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-station-statistic-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-station-statistic-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/K695OBRJkSoSerqJA/builds/vDEuDgxFmC5VmaNsH/openapi.json