EU Historical Flood Event Records — EEA WISE Floods

Keyless. Pay per record. Europe's official flood events — dates, duration, return period and cross-border status.

This actor turns the European Environment Agency (EEA) WISE Floods Directive database into clean, per-record data — the flood EVENTS that EU member states reported in their Preliminary Flood Risk Assessment, one row per event. Each run reads the EEA's keyless DiscoData SQL service and delivers one record per flood event, structured for flood-risk and resilience analysis, reusable with acknowledgement of the EEA, with no personal data of any kind.

What this is, in one paragraph

Under the EU Floods Directive, member states catalogue the flood events relevant to their risk assessment — each with a code and name, a date and duration, a return period, and whether it crossed a border. This actor reads that flood-event table and delivers one record per event: the flood-event code and name, the EU floods unit of management, the country, whether the event is past or future, the date of commencement, the duration, the RETURN PERIOD, and the cross-border relationship — all carried as filed. It is the event layer of Europe's flood-risk picture, the sibling of the impact-consequence cell.

Who buys this and for what job

• Catastrophe modellers and reinsurers building event catalogues of official European floods.
• Resilience and civil-protection teams benchmarking return periods and durations by unit of management.
• Cross-border basin authorities tracking which events were reported as transboundary.
• Data engineers who want the WISE Floods event 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 events as filed — not an independent catalogue of this actor's making.

Flood-event grain — no person data

The unit of every record is a flood event — a code, a place name, a date and a return period, never a person. Floods Directive reporting is at event / unit-of-management level: there is no contact or named-individual field in the selected columns, and none is emitted. The flood_event_name is a place or event label (a town, a river reach), never a person. The free-text event-reference field is EXCLUDED at field selection. A person-key guard runs on every record as a backstop.

A note on scale, honestly

The source table holds 12,896 rows as verified by an exact COUNT(*) at build time, which matches the planning index for this category. It spans reporting countries, units of management, and both past events and future scenarios (the event_type_past_future field distinguishes them). The live count above is authoritative.

Sample output

Real rows from a live run of this actor (first 5 rows, selected columns).

One full record from the same run, exactly as delivered:

{
  "record_id": "AT10101",
  "flood_event_code": "AT10101",
  "flood_event_name": "Eisenstadt",
  "eu_floods_unit_of_management_code": "AT1000",
  "country_code": "AT",
  "country_name": "Austria",
  "event_type_past_future": "future",
  "date_of_commencement": null,
  "duration_of_flood": null,
  "return_period": "100--300",
  "cross_border_relationship": "no",
  "metadata_version_id": "https://reportnet.europa.eu/dataflow/1509/dataset/84811/snapshot/90333",
  "metadata_begin_life_span_version": "2025-07-16T12:00:02",
  "metadata_status_code": "accepted",
  "source": "EEA WISE Floods Directive — Preliminary Flood Risk Assessment flood events",
  "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": "Official flood EVENTS reported by EU member states under the Floods Directive Preliminary Flood Risk Assessment, at flood-event grain. Each record carries the flood-event code and name, the EU floods unit of management, the country, whether the event is past or future, the date of commencement, the duration, the RETURN PERIOD, and the cross-border relationship VERBATIM, plus reporting metadata. The free-text event reference field is EXCLUDED at field selection. Flood-event grain — the event name is a place/event label, never a person; there is no contact or named-individual field selected or emitted, and a person-key guard runs on every record.",
  "observed_at": "2026-09-25T17:32:53Z"
}

Pricing

Event	Free plan	Bronze	Silver	Gold / Platinum / Diamond
historical_flood_event_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).
eventType	string	—	Optional: past or future flood event.
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 flood event. Representative example (values as reported):

{
  "record_id": "AT10101",
  "flood_event_code": "AT10101",
  "flood_event_name": "Eisenstadt",
  "eu_floods_unit_of_management_code": "AT1000",
  "country_code": "AT",
  "country_name": "Austria",
  "event_type_past_future": "future",
  "date_of_commencement": null,
  "duration_of_flood": null,
  "return_period": "100--300",
  "cross_border_relationship": "no",
  "source": "EEA WISE Floods Directive — Preliminary Flood Risk Assessment flood events",
  "observed_at": "2026-08-27T00: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 flood event. Identity: record_id, flood_event_code, flood_event_name, eu_floods_unit_of_management_code, country_code, and country_name. Event: event_type_past_future, date_of_commencement, duration_of_flood, return_period, and 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 event table (filtered to your optional countryCode and eventType), ordered by the high-cardinality flood-event code, and flattens each row to one record — carrying every value verbatim, never anything person-shaped and never the free-text reference — 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 12,896 rows across reporting countries, units of management, and past/future event types. Because each record carries the country_code, the eu_floods_unit_of_management_code, the event_type_past_future, and the return_period, segmenting by country, unit, event type or return period is straightforward. Pull one country, only past events, or the whole table to seed a flood-risk warehouse.

Working with the data

The events are a catalogue layer, and the fields make them actionable. Because every record pairs a flood event with a return_period, a duration_of_flood and a cross_border_relationship, an analyst can build an event set by return period, isolate transboundary events for cross-border coordination, and — joined to the impact-consequence cell on the geography — line events up against the harm they caused.

Cost guidance

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

Honest limitations

• As reported. Dates, durations and return periods are as filed by member states; this actor reformats, it does not audit or recompute.
• Past and future merged. The event_type_past_future field distinguishes recorded events from future scenarios — filter on it if you want one.
• Return period kept verbatim. Ranges such as 100--300 are carried through as reported rather than parsed.
• Acknowledge the EEA, and note there is no person data of any kind.

Differentiation

It is the EVENT grain — one row per flood event — distinct from eu-historical-flood-impact-records, which records the impact consequences at hazard-area / consequence-type grain on a different table. Its specific job is the WISE Floods flood-event catalogue.

The NexGen Signal family

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

• EU Waterbody Quality Records — EEA
• EU Nitrate Monitoring Records — EEA
• EU Bathing Water Quality Records — EEA
• EU Industrial Emissions Records — EEA
• EU Surface Water Priority Substance Records — EEA

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. Flood-event grain; the event name is a place/event label, not a person; the free-text reference is excluded; no contact or named-individual field is selected or emitted, no natural-person data of any kind. Reported events as filed, not an independent catalogue.