EU Riverine Pollutant Load Records — EEA WISE

Keyless. Pay per record. River-borne pollutant loads measured at Europe's monitoring sites — pollutant, load, and unit, verbatim.

This actor turns the European Environment Agency (EEA) WISE State of Environment (Waterbase) dataset into clean, per-record data — the river-borne pollutant loads measured at Europe's water-monitoring sites. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per load record, structured for water-pollution and riverine-flux analysis, reusable with acknowledgement of the EEA, with no personal data of any kind.

What this is, in one paragraph

The EEA compiles national measurements of the pollutant loads carried by rivers past monitoring sites into the WISE State of Environment (Waterbase) riverine-input-loads dataset. This actor reads that table and delivers one record per site / pollutant / year: the country and monitoring site, the reference year, the pollutant (determinand code and label), the load VALUE and UNIT in the source units verbatim, and the estimate-detail and observation-STATUS flags. It is the riverine-flux layer — how much of a pollutant a river actually carries past a point.

Who buys this and for what job

• Water-pollution analysts quantifying river-borne pollutant loads at monitoring sites
• Flux and catchment-modelling teams feeding measured riverine loads into transport models
• Researchers comparing riverine pollutant fluxes across sites and years
• Data engineers who want the WISE riverine input loads 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.

Monitoring-site grain — no person data

The unit of every record is a river-borne pollutant load at a monitoring site — a flux figure, never a person. The site identifier is a location code; there is no contact, operator, or responsible-person field in the source, and none is selected or emitted; the free-text remark fields are excluded at field selection. A person-key guard runs on every record as a backstop.

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": "EESJA0088000:CAS_14265-44-2:2023",
  "country_code": "EE",
  "monitoring_site_identifier": "EESJA0088000",
  "monitoring_site_identifier_scheme": "euMonitoringSiteCode",
  "reference_year": "2023",
  "determinand_code": "CAS_14265-44-2",
  "determinand_label": "Phosphate",
  "load_value": 6.13322158654741,
  "load_uom": "t/a",
  "estimate_detail": "OutY",
  "observation_status": null,
  "source": "EEA WISE State of Environment (Waterbase) — riverine input loads",
  "source_url": "https://discodata.eea.europa.eu/",
  "licence": "European Environment Agency (EEA) WISE State of Environment (Waterbase) — river-borne pollutant loads at monitoring sites. 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 State of Environment (Waterbase).",
  "disclaimer": "River-borne pollutant loads measured at monitoring sites, at site / pollutant / year grain from the EEA WISE State of Environment (Waterbase) riverine input loads dataset. Each record carries the monitoring site, the reference year, the pollutant (determinand code and label), the load VALUE and UNIT in the SOURCE UNITS VERBATIM, and the estimate-detail and observation-STATUS flags carried verbatim. Monitoring-site grain — the site identifier is a location code; there is no contact, operator, or responsible-person field in the source, and none is selected or emitted (free-text remark fields excluded at field selection); a person-key guard runs on every record as a backstop.",
  "observed_at": "2026-09-25T17:34:05Z"
}

Pricing

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

Output

One JSON object per load record. Real example (values as reported):

{
  "record_id": "AT00001:CAS_7439-92-1:2016",
  "country_code": "AT",
  "monitoring_site_identifier": "AT00001",
  "monitoring_site_identifier_scheme": "eionetSchema",
  "reference_year": "2016",
  "determinand_code": "CAS_7439-92-1",
  "determinand_label": "Lead and its compounds",
  "load_value": 123.4,
  "load_uom": "t/a",
  "estimate_detail": "measured",
  "observation_status": "A",
  "source": "EEA WISE State of Environment (Waterbase) \u2014 riverine input loads",
  "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 riverine load. Identity: record_id, country_code, monitoring_site_identifier, monitoring_site_identifier_scheme, and reference_year. Pollutant: determinand_code and determinand_label. Measurement: load_value, load_uom, estimate_detail, and observation_status. 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 riverine input loads 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 19,620 rows. Because each record carries the monitoring_site_identifier, determinand_label, and reference_year, segmenting is straightforward. Pull one slice, or the whole table to seed a warehouse.

Working with the data

The loads are a flux ledger, and the fields make them additive. Because every record pairs a determinand_label with a load_value and load_uom at a monitoring_site_identifier, an analyst can build a site's pollutant-flux time series without unit-guessing, and the estimate_detail and observation_status flags travel so estimated or provisional loads are handled explicitly. The reference_year frames each load in time.

Identifiers and joins

Every record carries the monitoring_site_identifier, keying each load to any monitoring-site reference a buyer maintains, and the country_code and pollutant code line it up with the fleet's water-emission and input-inventory cells for a full picture of what enters, moves through, and leaves a basin.

Riverine loads versus basin emissions

A riverine load is a MEASURED flux at a point on a river — how much of a pollutant actually flowed past a monitoring site — whereas a basin emission load is the ESTIMATED input entering a river basin from its sources. The two are complementary: emissions say what went in, riverine loads say what the river carried past a point downstream. Keeping them as separate actors lets an analyst compare inputs against measured fluxes to study retention and loss along the river network.

Estimate detail and status

A measured riverine load is only as trustworthy as its method, so the estimate_detail field — measured, calculated, or estimated — and the observation_status travel on every record. That lets a flux model down-weight or exclude estimated loads rather than mixing them with directly measured ones, and because the load value and unit are carried verbatim in the source units, no rescaling is imposed before the buyer decides how to treat each figure.

Cost guidance

One riverine_load_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, values, and flags are as filed; this actor reformats, it does not audit or recompute.
• A label, not a verdict. These are reported classifications and outcomes, not an independent compliance or health assessment.
• Acknowledge the EEA. The acknowledgement travels on every record.
• No person data of any kind.

Differentiation

It is distinct from eu-water-emission-load-records — that cell carries the basin-level EMISSIONS to water by source category (estimated inputs), while this cell carries the MEASURED riverine loads at monitoring sites; site fluxes vs basin source emissions. Its specific job is the WISE riverine input loads.

The NexGen Signal family

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

• EU Waterbody Pressure Source Records — EEA WISE
• EU Groundwater Pollutant Failure Records — EEA WISE
• EU Surface Water Priority Substance Records — EEA WISE
• EU Waterbody Quality Records — EEA
• EU Water Emission Load Records — EEA WISE

Source: European Environment Agency (EEA), WISE State of Environment (Waterbase) (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. Monitoring-site / pollutant / year grain; the site identifier is a location code; free-text remarks excluded, no contact/operator/responsible-person field selected or emitted. No natural-person data of any kind. Values and status labels as filed, not a compliance verdict.