EU Water Monitoring Parameter Schedule Records — EEA WISE

Keyless. Pay per record. Which parameters each official European monitoring site is scheduled to test — role, frequency, cycle, and last-monitored year.

This actor turns the European Environment Agency (EEA) WISE Water Framework Directive (WFD) monitoring programme into clean, per-record data — the monitoring schedules of Europe's official water-monitoring sites: which parameters each site is set up to test, and how. Each run reads the EEA's keyless DiscoData SQL service and delivers one row per schedule row, structured for monitoring-network and water-management 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, member states report their monitoring programmes — which sites monitor which parameters, for which purpose, and how often. This actor reads that monitoring table and delivers one record per site-parameter schedule line: the country, river basin, water body, and monitoring site; the monitoring roles the site plays (ecological, chemical, quantitative, investigative, operational, surveillance); the parameter, matrix, and purpose; and the frequency, cycle, and last-monitored year — all carried verbatim. It is the monitoring SCHEDULE topology, not the measured values.

Who buys this and for what job

• Monitoring-network analysts mapping which parameters are scheduled where and how often across Europe
• Water-management and consultancy teams auditing monitoring coverage by parameter and site
• Researchers studying the design and frequency of national water-monitoring programmes
• Data engineers who want the WISE WFD monitoring schedule 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 as filed — not a compliance verdict.

Monitoring-site grain — no person data

The unit of every record is a site-parameter schedule line — a monitoring site and a scheduled parameter, never a person. The monitoring site name is a location/facility label; there is no contact, operator, or responsible-person field in the source, and none is selected or emitted. 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.

A required partition — this is a large dataset

The table holds 5,847,200 rows, so this actor requires a partition: every run must set a countryCode. The country bounds the run; there is no unbounded all-Europe pull. An optional year filter narrows further, and maxRecords is the hard ceiling.

A note on scale, honestly

The source table (Monitoring_MonitoringSite_ChemicalEcologicalQuantitativeMonitoring) holds 5,847,200 rows as verified by an exact COUNT(*) at build time — a genuine MONSTER carrying the 2016 and 2022 reporting cycles. This is why the run requires a countryCode partition; the live count is authoritative.

Pricing

Event	Free plan	Bronze	Silver	Gold / Platinum / Diamond
monitoring_schedule_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	—	REQUIRED 2-letter country code (e.g. DE, FR).
year	integer	—	Optional reporting cycle year to filter.
maxRecords	integer	500	Ceiling on records delivered and billed.

Output

One JSON object per schedule row. Real example (values as reported):

{
  "record_id": "AT359182:Nitrate:2022",
  "reporting_year": 2022,
  "country_code": "AT",
  "country_name": "Austria",
  "eu_rbd_code": "AT1000",
  "rbd_name": "DANUBE",
  "water_body_code": "ATGK100001",
  "monitoring_site_name": "Example Site",
  "eu_monitoring_site_code": "AT359182",
  "quantitative_monitoring": "Yes",
  "surveillance_monitoring": "Yes",
  "parameter_code": "Nitrate",
  "chemical_matrix": "Water",
  "frequency": "12",
  "cycle": "Annual",
  "last_monitored": "2021",
  "source": "EEA WISE Water Framework Directive (WFD) \u2014 monitoring site parameter schedule",
  "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 site-parameter schedule line. Identity: record_id, country_code, country_name, eu_rbd_code, rbd_name, water_body_code, water_body_name, water_body_category, monitoring_site_name, eu_monitoring_site_code, and reporting_year. Roles: ecological_monitoring, chemical_monitoring, quantitative_monitoring, investigative_monitoring, operational_monitoring, and surveillance_monitoring. Schedule: parameter_code, parameter_other, chemical_matrix, chemical_purpose, frequency, cycle, and last_monitored. 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 monitoring schedule table, and flattens each row to one record — carrying every 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 5,847,200 rows. Because each record carries the country_code, eu_monitoring_site_code, parameter_code, and reporting_year, segmenting is straightforward. Pull one slice, or the whole table to seed a warehouse.

Working with the data

The schedules are a network map, and the fields make them auditable. Because every record pairs a parameter_code with a frequency, cycle, and the site's monitoring roles, an analyst can see which parameters are monitored most intensively, which sites carry surveillance vs operational monitoring, and where a parameter is scheduled at all. The last_monitored year flags stale schedules, and the reporting_year lets the 2016 and 2022 programmes be compared.

Identifiers and joins

Every record carries the eu_monitoring_site_code and water_body_code, keying each schedule line to its water body across the fleet's other WISE cells — the water-body status, the failing pollutants, the exemptions — so a buyer can line up what a site is scheduled to measure against what its water body actually reports, on shared identifiers rather than a fuzzy name match.

Cost guidance

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

Differentiation

This is a net-new category for the NexGenData fleet. It is distinct from eu-nitrate-monitoring-records and eu-pesticide-water-monitoring-records, which deliver measured VALUES; this cell delivers the monitoring SCHEDULE topology (what is planned to be tested, where, and how often), not the measurements. It differs entirely from the status and exemption cells. Its specific job is the WFD monitoring-site parameter schedule.

The NexGen Signal family

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

• EU Water Monitoring Parameter Schedule Records — EEA WISE
• EU Surface Water Ecological Exemption Records — EEA WISE
• EU Waterbody Pesticide Exceedance Records — EEA WISE
• EU Waterbody Quality Records — EEA
• EU Nitrate Monitoring Records — EEA

Source: European Environment Agency (EEA), WISE (Water Information System for Europe) (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 / parameter / cycle grain; the site name is a location label, no contact/operator/responsible-person field selected or emitted. No natural-person data of any kind. Values as filed, not a compliance verdict.