EU Historical Flood Impact Records — EEA WISE Floods

Keyless. Pay per record. The recorded impacts of past floods across Europe, as reported by member states under the EU Floods Directive.

This actor turns the European Environment Agency (EEA) WISE Floods Directive database into clean, per-record data — the documented consequences of PAST flood events that EU member states reported in their Preliminary Flood Risk Assessment. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per reported impact, structured for flood-risk, insurance, 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 (2007/60/EC), every member state carries out a Preliminary Flood Risk Assessment that looks back at significant historical floods and records the harm they caused — to human health, to economic activity, to the environment, and to cultural heritage. This actor reads that impact-consequence table and delivers one record per reported consequence: the country, the EU floods hazard-area code, the consequence TYPE, and the reported degree of total damage, its damage class, its value expressed against GDP, and the fatalities count — all carried as filed. It is the historical-impact layer of Europe's official flood-risk picture.

Who buys this and for what job

• Catastrophe modellers and reinsurers calibrating flood loss models against officially reported historical impacts.
• Resilience and adaptation teams benchmarking which flood-hazard areas have the worst recorded consequences.
• Environmental and economic researchers analysing how flood harm splits across health, economy, environment, and heritage.
• Data engineers who want the WISE Floods PFRA impact-consequence 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 and classifications as filed by member states — not an independent loss assessment.

Flood-area grain — no person data

The unit of every record is a reported consequence for a flood hazard area — a place and its reported impacts, never a person. Floods Directive reporting is at hazard-area level: there is no contact, operator, or named-individual field in the source table, and none is selected or emitted. The fatalities field is an aggregate reported count for a historical flood event — a statistic, not an identifiable individual. The two free-text narrative fields the source carries (a free-text "other consequence" description and an "other damage" description) are EXCLUDED at field selection so no unstructured narrative can leak; only the structured code, type, and value fields are read. A person-key guard runs on every record as a backstop. The metadata_version_id, where present, points to the official EU reporting record, never a person.

A note on scale, honestly

The source table holds 37,136 rows as verified by an exact COUNT(*) at build time — which matches the planning index for this category exactly. It carries the current reporting round of the Floods Directive PFRA across reporting countries and hazard areas. This is the real, populated table for this category; 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_2024:culturalHeritage",
  "country_code": "AT",
  "country_name": "Austria",
  "eu_floods_hazard_area_code": "AT10101_2024",
  "type_impact_consequence": "culturalHeritage",
  "degree_total_damage": "-9999",
  "degree_total_damage_class": null,
  "degree_total_damage_gdp": null,
  "fatalities": null,
  "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 past-event impact consequences",
  "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": "Recorded impacts and consequences of PAST flood events reported by EU member states under the Floods Directive Preliminary Flood Risk Assessment, at flood-hazard-area / consequence-type grain. Each record carries the country, the EU floods hazard-area code, the consequence type (human health, economic activity, environment, cultural heritage), and the reported degree of total damage, damage class, damage-as-GDP, and fatalities count VERBATIM, plus reporting metadata. Free-text consequence and damage narrative fields are EXCLUDED at field selection. Flood-area grain — the fatalities figure is an aggregate reported count, not a person; there is no contact or named-individual field in the source, none is 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_impact_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).
typeImpactConsequence	string	—	Optional consequence type: humanHealth, economicActivity, environment, culturalHeritage.
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 reported impact. Representative example (values as reported):

{
  "record_id": "DE4000_2024:economicActivity",
  "country_code": "DE",
  "country_name": "Germany",
  "eu_floods_hazard_area_code": "DE4000_2024",
  "type_impact_consequence": "economicActivity",
  "degree_total_damage": "High",
  "degree_total_damage_class": "3",
  "degree_total_damage_gdp": null,
  "fatalities": null,
  "metadata_status_code": "valid",
  "source": "EEA WISE Floods Directive — Preliminary Flood Risk Assessment past-event impact consequences",
  "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 reported consequence for a flood hazard area. Identity: record_id, country_code, country_name, and eu_floods_hazard_area_code. Consequence: type_impact_consequence (which of the four Floods Directive consequence categories), degree_total_damage, degree_total_damage_class, degree_total_damage_gdp, and the aggregate fatalities count. 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 PFRA impact-consequence table (filtered to your optional countryCode and consequence typeImpactConsequence), ordered by the high-cardinality flood-hazard-area code, and flattens each row to one record — carrying every reported label and value verbatim, never anything person-shaped and never the free-text narrative fields — 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 37,136 rows across reporting countries, flood-hazard areas, and the four consequence categories. Because each record carries the country_code, the eu_floods_hazard_area_code, and the type_impact_consequence, segmenting by country, by area, or by consequence category is straightforward. Pull one country, one consequence type, or the whole table to seed a flood-risk warehouse.

Working with the data

The impacts are a resilience-analysis layer, and the fields make them actionable. Because every record pairs a consequence type with a reported damage degree and class, an analyst can rank which hazard areas carry the worst recorded economic or environmental consequences in a single group-by, and can compare the mix of health, economic, environmental, and heritage harm across countries. Joined to the hazard-area code, the impacts line up against the wider Floods Directive geography.

Cost guidance

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

Honest limitations

• As reported. Damage degrees, classes, and fatalities are as filed by member states for the Floods Directive reporting round; this actor reformats, it does not audit or recompute.
• Past events, not forecasts. These are recorded consequences of historical floods, not a forward-looking probability or scenario.
• Sentinel values kept verbatim. Where a member state filed a no-data sentinel (e.g. -9999), it is carried through as reported rather than silently blanked — filter it in your own layer if you wish.
• Narrative excluded. The two free-text description fields are not selected, by design.
• Acknowledge the EEA, and note there is no person data of any kind.

Differentiation

It is the historical PAST-EVENT impact layer of the Floods Directive, distinct from any hazard-map or probability-scenario product: the forward-looking flood-scenario tables in the EEA catalogue are not yet loaded, so this actor deliberately delivers the populated PFRA impact-consequence grain instead. It does not overlap the surface-water or groundwater WFD cells, which are about water status, not flood events.

The NexGen Signal family

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

• EU Waterbody Quality Records — EEA
• EU Bathing Water Quality Records — EEA
• EU Nitrate Monitoring Records — EEA
• EU Groundwater Chemical Exemption Records — EEA
• EU Industrial Emissions 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-area grain; the fatalities figure is an aggregate reported count, not a person; no contact, operator, or responsible-person field is selected or emitted, no natural-person data of any kind. Reported values and classifications as filed for the Floods Directive reporting round, not an independent loss assessment.