EU Groundwater Quantity Failure Reason Records — EEA WISE avatar

EU Groundwater Quantity Failure Reason Records — EEA WISE

Pricing

from $33.50 / 1,000 gw quantity failure reason records

Go to Apify Store
EU Groundwater Quantity Failure Reason Records — EEA WISE

EU Groundwater Quantity Failure Reason Records — EEA WISE

Keyless pay-per-record EEA WISE WFD groundwater quantitative-status failure reasons — groundwater body, quantitative status, reason for failure (water balance), as filed. Distinct from chemical reasons. No person data. Gold $0.0335/record.

Pricing

from $33.50 / 1,000 gw quantity failure reason records

Rating

0.0

(0)

Developer

NexGen Signal

NexGen Signal

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

10 days ago

Last modified

Features

Limited permissions

Share

Keyless. Pay per record. The official reasons Europe's groundwater bodies fail quantitative status — as filed.

This actor turns the European Environment Agency (EEA) WISE Water Framework Directive (WFD) database into clean, per-record data — the official reasons reported for groundwater quantitative-status failure. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per failure-reason record, structured for water-status and catchment analysis, reusable with acknowledgement of the EEA, with no personal data of any kind.

What this is, in one paragraph

Under the Water Framework Directive, where a groundwater body fails quantitative status — its water balance, driven by abstraction against recharge — member states report the reason. This actor reads that quantitative-reasons table and delivers one record per groundwater body / reason / year: the country and river basin, the groundwater body, its quantitative status value, assessment year, confidence, and expected achievement date, and the reported REASON FOR FAILURE — carried as filed. It is the quantitative-failure-reason layer of Europe's groundwater assessment.

Who buys this and for what job

  • Groundwater and abstraction analysts categorising why bodies fail quantitative status
  • Water-resource and drought teams targeting the documented quantitative failure reasons
  • Researchers studying the drivers of groundwater over-abstraction across basins
  • Data engineers who want the WISE WFD groundwater quantitative failure reason 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 status labels as filed — not a compliance verdict.

Water-body grain — no person data

The unit of every record is a quantitative-failure reason for a groundwater body — a water body and its reported attributes, never a person. WISE reporting is at water-body / river-basin level: there is no contact, operator, or responsible-person field in the source table, and none is selected or emitted — the query reads only the water-body identity, the status/flags, and the quantitative status and reason for failure; the free-text 'other' pressure and impact narrative fields are excluded at field selection. A person-key guard runs on every record as a backstop. The file_url points to the official Eionet/CDR reporting file, never a person.

Sample output

Sample output — EU Groundwater Quantity Failure Reason Records — EEA WISE

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": ":Unpopulated:2010",
"reporting_year": 2010,
"country_code": "BE",
"country_name": "Belgium",
"eu_rbd_code": "BENOORDZEE_FED",
"rbd_name": "BELGIAN COAST",
"eu_groundwater_body_code": null,
"groundwater_body_name": null,
"quantitative_status_value": null,
"quantitative_assessment_year": null,
"quantitative_assessment_confidence": null,
"quantitative_status_expected_achievement_date": null,
"quantitative_reason_for_failure": "Unpopulated",
"file_url": null,
"source": "EEA WISE Water Framework Directive (WFD) — groundwater quantitative-status failure reasons",
"source_url": "https://discodata.eea.europa.eu/",
"licence": "European Environment Agency (EEA) WISE Water Framework Directive (WFD) database — groundwater quantitative-status failure reasons. 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 Water Framework Directive (WFD) database.",
"disclaimer": "Official reasons for groundwater QUANTITATIVE-status failure at groundwater-body / reason / year grain from the EEA WISE Water Framework Directive database. Each record names a groundwater body, its quantitative status value, assessment year, confidence and expected achievement date, and the reported REASON FOR FAILURE carried as filed. This is the QUANTITATIVE regime (water balance / abstraction), distinct from the chemical-failure-reason cell. Water-body grain — there is no contact, operator, or responsible-person field in the source, and none is selected or emitted (free-text 'other' pressure/impact fields excluded at field selection); a person-key guard runs on every record as a backstop.",
"observed_at": "2026-09-25T17:32:13Z"
}

Pricing

EventFree planBronzeSilverGold / Platinum / Diamond
gw_quantity_failure_reason_record$0.05$0.045$0.04$0.0335

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

Input

FieldTypeDefaultDescription
countryCodestring—Optional 2-letter country code (e.g. DE, FR).
yearinteger—Optional reporting cycle year to filter (e.g. 2016, 2022).
maxRecordsinteger500Ceiling on records delivered and billed.

Output

One JSON object per failure-reason record. Real example (values as reported):

{
"record_id": "ATGK100001:Abstraction exceeds recharge:2016",
"reporting_year": 2016,
"country_code": "AT",
"country_name": "Austria",
"eu_rbd_code": "AT1000",
"rbd_name": "DANUBE",
"eu_groundwater_body_code": "ATGK100001",
"groundwater_body_name": "Example GW Body",
"quantitative_status_value": "3",
"quantitative_reason_for_failure": "Abstraction exceeds recharge",
"source": "EEA WISE Water Framework Directive (WFD) \u2014 groundwater quantitative-status failure reasons",
"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 quantitative-failure reason. Identity: record_id, country_code, country_name, eu_rbd_code, rbd_name, eu_groundwater_body_code, groundwater_body_name, and reporting_year. Status and reason: quantitative_status_value, quantitative_assessment_year, quantitative_assessment_confidence, quantitative_status_expected_achievement_date, and quantitative_reason_for_failure. Plus file_url. 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 WFD groundwater quantitative failure reason table (filtered to your optional countryCode and optional year), and flattens each row to one record — carrying every status label and 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 49,329 rows across reporting countries, river basin districts, and the 2016 and 2022 WFD reporting cycles. Because each record carries the country_code, the water-body identity, and the reporting_year, segmenting by country, basin, or cycle is straightforward. Pull one country, or the whole table to seed a water-status warehouse.

Why the quantitative regime is its own table

Quantitative status is a fundamentally different question from chemical status: it is about water balance — whether abstraction exceeds recharge, whether groundwater-dependent ecosystems or surface waters are harmed, whether saline intrusion is drawn in — not about pollutants. That is why the source keeps quantitative failure reasons in a separate table from chemical ones, and why the two have near-identical but not equal row counts. This actor reads only the quantitative table, so every record here is a water-balance reason, never a chemical one.

Working with the data

The reasons are a categorisation layer, and the fields make them countable. Because every record pairs a quantitative_reason_for_failure with the body's quantitative_status_value and expected achievement date, an analyst can tally the documented reasons for quantitative failure — over-abstraction, saline intrusion, dependent-ecosystem damage — across a basin. The reporting_year tracks change between cycles.

Identifiers and joins

Every record carries the eu_groundwater_body_code, keying each reason to the fleet's groundwater pollutant-assessment, exemption, and surface-water-linkage cells for the same body, on a shared identifier.

Cost guidance

One gw_quantity_failure_reason_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. Status labels, reasons, and values are as filed by member states for the WFD reporting cycle; this actor reformats, it does not audit or recompute.
  • A label, not a verdict. These are reported classifications, assessments, and reasons, not an independent compliance assessment.
  • Two cycles merged. The table carries both the 2016 and 2022 reporting cycles; the reporting_year field distinguishes them.
  • Acknowledge the EEA. The acknowledgement travels on every record.
  • No person data of any kind.

Differentiation

It is distinct from eu-groundwater-chemical-failure-reason-records — that cell carries the CHEMICAL-status failure reasons, while this cell carries the QUANTITATIVE-status (water-balance) failure reasons; a separate table with a near-identical row count, verified independently by exact COUNT. Its specific job is the WFD groundwater quantitative-status failure reasons.

The NexGen Signal family

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

Source: European Environment Agency (EEA), WISE Water Framework Directive (WFD) 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. Groundwater-body / reason / year grain; no contact/operator/responsible-person field selected or emitted, free-text 'other' narrative excluded. No natural-person data of any kind. Values and status labels as filed, not a compliance verdict.