# EU Significant Flood Risk Area Records — EEA WISE (`nexgensignal/eu-significant-flood-risk-area-records`) Actor

Keyless pay-per-record EEA WISE Floods Directive APSFR designations — risk-zone code, unit of management, country and cross-border status, as filed. Risk-zone grain, no person data. Gold $0.0335/record.

- **URL**: https://apify.com/nexgensignal/eu-significant-flood-risk-area-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 significant flood risk area 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 Significant Flood Risk Area Records — EEA WISE

**Keyless. Pay per record. Every officially designated Area of Potential Significant Flood Risk in Europe.**

This actor turns the **European Environment Agency (EEA) WISE Floods Directive database** into clean, per-record data — the Areas of Potential Significant Flood Risk (APSFR) that EU member states designate under the Floods Directive. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per designated area, structured for flood-risk and planning analysis, reusable with acknowledgement of the EEA, with no personal data of any kind.

### What this is, in one paragraph

The Floods Directive asks each member state to identify, from its preliminary flood risk assessment, the areas where significant flood risk exists or is likely — the Areas of Potential Significant Flood Risk that then drive hazard mapping and management planning. This actor reads that designation table and delivers one record per area: the EU floods risk-zone code, the unit of management, the country, and whether the area is cross-border — all carried as filed. It is the risk-area designation layer of Europe's flood-risk picture, distinct from the flood-event and flood-impact cells.

### Who buys this and for what job

- **Flood-risk and planning teams** enumerating the officially designated risk areas by country and basin.
- **Insurers and catastrophe modellers** aligning exposure to the designated APSFRs.
- **Cross-border basin authorities** finding areas flagged as transboundary.
- **Data engineers** who want the WISE Floods APSFR designation 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 designations as filed — not an independent assessment.

### Risk-zone grain — no person data

The unit of every record is a designated flood-risk area — a risk-zone code and its attributes, never a person. Floods Directive reporting is at risk-zone / unit-of-management level: there is **no contact or named-individual field** in the selected columns, and none is emitted. The three free-text "other characteristics / other mechanism / other source of flooding" description fields are **EXCLUDED at field selection**. A person-key guard runs on every record as a backstop.

### A note on scale, honestly

The source table holds **9,320 rows** as verified by an exact `COUNT(*)` at build time, which matches the planning index for this category exactly (and the figure confirmed in an earlier probe of this table). It spans reporting countries and units of management. The live count above is authoritative.

### Sample output

![Sample output — EU Significant Flood Risk Area Records — EEA WISE](https://api.apify.com/v2/key-value-stores/IXCaMKjxSmUTLHhmq/records/eu-significant-flood-risk-area-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": "ATFR10001",
  "eu_floods_risk_zone_code": "ATFR10001",
  "eu_floods_unit_of_management_code": "AT1000",
  "country_code": "AT",
  "country_name": "Austria",
  "cross_border_relationship": "no",
  "metadata_version_id": "https://reportnet.europa.eu/dataflow/1509/dataset/84813/snapshot/90335",
  "metadata_begin_life_span_version": "2025-07-16T12:00:02",
  "metadata_status_code": "accepted",
  "source": "EEA WISE Floods Directive — Areas of Potential Significant Flood Risk (APSFR designation)",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) WISE database under EU environmental 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 Floods Directive database (discodata.eea.europa.eu).",
  "disclaimer": "Areas of Potential Significant Flood Risk (APSFR) designated by EU member states under the Floods Directive, at flood-risk-zone grain. Each record carries the EU floods risk-zone code, the unit of management, the country, and the cross-border relationship VERBATIM, plus reporting metadata. The three free-text 'other characteristics / other mechanism / other source of flooding' description fields are EXCLUDED at field selection. Risk-zone grain — no contact or named-individual field is selected or emitted, and a person-key guard runs on every record.",
  "observed_at": "2026-09-25T17:34:05Z"
}
```

### Pricing

| Event | Free plan | Bronze | Silver | Gold / Platinum / Diamond |
|-------|-----------|--------|--------|---------------------------|
| `significant_flood_risk_area_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). |
| `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 designated area. Representative example (values as reported):

```json
{
  "record_id": "ATFR10001",
  "eu_floods_risk_zone_code": "ATFR10001",
  "eu_floods_unit_of_management_code": "AT1000",
  "country_code": "AT",
  "country_name": "Austria",
  "cross_border_relationship": "no",
  "metadata_status_code": "valid",
  "source": "EEA WISE Floods Directive — Areas of Potential Significant Flood Risk (APSFR designation)",
  "observed_at": "2026-08-30T00: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 designated risk area. Identity: `record_id`, `eu_floods_risk_zone_code`, `eu_floods_unit_of_management_code`, `country_code`, and `country_name`. Attribute: `cross_border_relationship`. Reporting metadata: `metadata_version_id`, `metadata_begin_life_span_version`, and `metadata_status_code`. 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 WISE Floods APSFR designation table (filtered to your optional `countryCode`), ordered by the high-cardinality risk-zone code, and flattens each row to one record — carrying every value **verbatim**, never anything person-shaped and never the free-text descriptions — 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 **9,320 rows** across reporting countries and units of management. Because each record carries the `country_code`, the `eu_floods_unit_of_management_code`, and the `cross_border_relationship`, segmenting by country, unit, or transboundary status is straightforward. Pull one country, only transboundary areas, or the whole table to seed a flood-risk warehouse.

### Working with the data

The designations are a scoping layer, and the fields make them actionable. Because every record ties a risk-zone code to a unit of management and a cross-border flag, an analyst can enumerate the designated risk areas per basin, isolate transboundary areas for cross-border coordination, and — joined to the flood-event and flood-impact cells on the geography — connect designated areas to the events and consequences reported for them.

### Where APSFRs sit in the Floods Directive

The Floods Directive runs on a six-year cycle with three stages: a preliminary flood risk assessment, then the designation of Areas of Potential Significant Flood Risk, then flood hazard and risk maps and management plans for those areas. This table is the **second stage** — the official list of areas a member state decided warrant the full mapping-and-planning treatment. That makes it the natural index for the rest of the flood data: every hazard map, risk map and management measure downstream is scoped to one of these risk zones. Because each record carries the unit-of-management code, an analyst can roll the designated areas up to the basin level a country manages them at, and because the cross-border flag is explicit, the areas that need coordination between member states fall out with a single filter. The risk-zone code is stable across the reporting, so this list also serves as the join key that ties the flood family together.

### A note on identifiers

The `eu_floods_risk_zone_code` is the stable EU-wide identifier for a designated area, and the `eu_floods_unit_of_management_code` places it in the basin unit its country manages flood risk at. Both are official Floods Directive codes — places, never people — and both are the join keys you use to bring designations, events and impacts together for a single area or basin. Because the same codes are used across the flood family, building a complete per-area picture needs no fuzzy matching.

### Cost guidance

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

### Honest limitations

- **As reported.** Designations and cross-border flags are as filed by member states; this actor reformats, it does not audit or recompute.
- **Designation, not hazard.** This is the risk-area designation; hazard maps and consequences live in other Floods Directive tables.
- **Narrative excluded.** The three free-text flooding-description fields are not selected, by design.
- **Acknowledge the EEA**, and note there is **no person data** of any kind.

### Differentiation

It is the AREA-DESIGNATION grain, distinct from **eu-historical-flood-event-records** (the flood events) and **eu-historical-flood-impact-records** (the impact consequences) — both named here as siblings. Its area-consequence sibling table was ruled the wrong grain in an earlier build and is deliberately not used. Its specific job is the **WISE Floods APSFR designations**.

### The NexGen Signal family

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

- [EU Water Abstraction Records — EEA](https://apify.com/nexgensignal/eu-water-abstraction-records)
- [EU Renewable Freshwater Resource Records — EEA](https://apify.com/nexgensignal/eu-renewable-freshwater-resource-records)
- [EU Waterbody Quality Records — EEA](https://apify.com/nexgensignal/eu-waterbody-quality-records)
- [EU Historical Flood Event Records — EEA](https://apify.com/nexgensignal/eu-historical-flood-event-records)
- [EU Protected Site Positive Impact Records — EEA](https://apify.com/nexgensignal/eu-protected-site-positive-impact-records)

*Source: European Environment Agency (EEA), WISE Floods Directive 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. Risk-zone grain; no contact or named-individual field is selected or emitted, no natural-person data of any kind. Reported designations as filed, not an assessment.*

# Actor input Schema

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

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

## `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-significant-flood-risk-area-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-significant-flood-risk-area-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-significant-flood-risk-area-records --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,nexgensignal/eu-significant-flood-risk-area-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/GPK42I5cW3J6T8Ic7/builds/fOdSQSGObMHLnuFry/openapi.json