FOTO-NL chemical pollution monitoring data for Dutch surface waters This archive contains the data products underlying the FOTO-NL workflow for long-term analysis of chemical pollution in Dutch surface waters. The data were collated from the 21 current Dutch regional water boards and from Rijkswaterstaat for the rivers Rhine and Meuse. The dataset covers the Netherlands and the period from 1954-01-14 to 2020-01-08. The package contains both the final harmonized datasets and the supporting input/output bundles needed to reproduce the workflow. The workflow starts from heterogeneous provider-specific raw files, reconstructs standardized per-board input tables in script₀, harmonizes and cleans the data in script₁, applies Dutch spatial filtering in script₂, and generates summary statistics and example outputs in script₃. The two main final datasets are provided directly as CSV files: fotoₙldatasetᵣaw. csv: broader raw-derived collated dataset with 51, 557, 114 records fotoₙldatasetclean. csv: cleaned and harmonized dataset with 35, 756, 662 records containing only those measurements with valid CAS-numbers. In these files: Location identifiers and X and Y coordinates Sampling dates Parameter codes (Aquocodes) and CAS-numbers (added where missing) Sample pretreatment flags (e. g. filtered vs unfiltered) Measured values and original units Archive contents waterboarddataₛcript₀ᵢnput. zipOriginal raw board-delivered input tree used as input to script₀. This archive contains the heterogeneous source exports received from the 21 Dutch water boards, including CSV files, text exports, Excel workbooks, and provider-delivered zip bundles. These are the original source files used to reconstruct the standardized per-board inputs. auxiliaryworkflowᵢnput. zipAuxiliary workflow inputs that are not part of the original raw provider delivery tree. This archive includes supplementary coordinate files, Rijkswaterstaat support workbooks, the Dutch boundary file used in spatial filtering, and board-specific lookup and adjustment tables used during script₀. Examples include parameter lookup tables for Rivierenland, Rijnland, Scheldestromen, and Hollands Noorderkwartier, as well as SI₂ₜable. xlsx which contains CAS-codes for innitially unrecognized substances. workflowₒutputs/script₀ₒutput. zipStandardized per-board outputs produced by script₀. For each board, this archive contains a boardᵢnput. csv file. These files are the direct outputs of script₀ and the direct inputs to script₁. workflowₒutputs/fotoₙldatasetᵣaw. csvBroader raw-derived final dataset, provided as plain CSV for direct reuse. It preserves the full collated record set after workflow reconstruction and spatial processing, including physicochemical variables and other measurements that are not retained in the final cleaned subset. workflowₒutputs/fotoₙldatasetclean. csvCleaned and harmonized final dataset, provided as plain CSV for direct reuse. This dataset contains the workflow-standardized observations used for downstream analyses and reporting. workflowₒutputs/rdsₒutputs. zipRDS versions of the two final datasets: fotoₙldatasetᵣaw. rds fotoₙldatasetclean. rds workflowₒutputs/summaryₛtatistics. zipSummary tables and figures generated by script₃. This archive includes yearly counts of measurements, substances, and sample sites; water-board by year summaries; heatmaps; sample-day summaries; interquartile-range tables; and example plots for selected general chemistry, metals, and pesticides. workflowₒutputs/exampleₚesticidesdelfland. zipExample Delfland case-study outputs produced by PesticesDelfland. R. This archive includes compound-specific extracted datasets for chloride, nitrate, imidacloprid, and tolclofos-methyl; threshold values used in the plots; summary tables; and the generated point, violin, and GAM figures. MANIFEST. txtFile inventory for the Zenodo package contents. Notes The rendered workflow HTML reports are distributed with the accompanying GitHub repository https: //github. com/rivm-syso/FOTO-NL, not with this Zenodo data package. Original board-delivered files and workflow helper files are intentionally separated: original source data are stored in waterboarddataₛcript₀ᵢnput. zip lookup tables and helper files are stored in auxiliaryworkflowᵢnput. zip
Hofman et al. (Fri,) studied this question.