D5.1: E-HYPE (v4.3.2 - 2025) historical model data set - river water and substance flows at Europe's coastal outlets

Open data API in a single place

Provided by Zenodo

Get early access to D5.1: E-HYPE (v4.3.2 - 2025) historical model data set - river water and substance flows at Europe's coastal outlets API!

Let us know and we will figure it out for you.

Dataset information

Country of origin
Updated
2025.12.18 00:00
Created
2025.01.01
Available languages
English
Keywords
coastal river outlets, HYPE, FOCCUS, streamflow
Quality scoring

Dataset description

Description The dataset is an element of FOCCUS (WP 5: Building, validation and demonstration of improved model interfaces in the Land-Ocean Continuum), included in Deliverables 5.1 and 5.2. The dataset is produced with help of E-HYPE hydrological model (v4.3.2 - 2025), and covers the time period 2000-2024 at 5302 coastal outlet points within Europe. Simulated variables provided at a daily time-step and include streamflow, nitrogen and phosphorus in several forms, and suspended sediment concentrations. NOTE: the current version outputs are completely different from the previously published dataset https://zenodo.org/records/17936484.  Technical details The dataset is produced at SMHI with use of E-HYPE continental hydrological model version 4.3.2 executed with HYPE code v.5.26.0.  Outlet point description: “EH432_coast_outlets.csv" file describes metadata for EH4 outlet points discharging into coastal zones. Smaller rivers and creeks along the coastline may be aggregated into one catchment with one virtual outlet point that does not represent any particular river. Columns in this file: SUBID: E-HYPE v4.3.2 catchment identification number (similar to E-HYPE v4.2.3 published within D4.1 in 2024) POURX: WGS 1984 longitude of the outlet point [decimal degrees] POURY: WGS 1984 latitude of the outlet point [decimal degrees] AREA: catchment area, square meters [m2] UPAREA: upstream area draining to the catchment, square meters [m2] Data description: Daily time series of EH4 v4.3.2 outputs are provided for each coastal outlet (identified by “SUBID”) in and plain text files. The following variables are provided: cout: freshwater discharge (eh432pp ML-based postprocessed), cubic meters/second [m3/s] cout: freshwater discharge, cubic meters/second [m3/s] ccin: simulated concentration of inorganic nitrogen, microgram per liter [μg/L] ccon: simulated concentration of organic nitrogen, microgram per liter [μg/L] cctn: simulated concentration of total nitrogen, microgram per liter [μg/L] ccsp: simulated concentration of soluble (reactive) phosphorus, microgram per liter [μg/L] ccpp: simulated concentration of particulate phosphorus, microgram per liter [μg/L] cctp: simulated concentration of total phosphorus, microgram per liter [μg/L] ccts: simulated concentration of total suspended solids, milligram per litre  [mg/L] Note. Streamflow discharge COUT is provided in two files and have certain particularities that users need to be aware about: COUT_eh432postprocessed_2000_2024_coast.txt - ML-postprocessed time-series include improved discharge time series at the coastal outlets. This improvement covers only coastal outlet locations. Recommended to use as an inflow to coastal zones of seas. COUT_eh432_2000_2024_coast.txt - original E-HYPE outputs. Simulated streamflow is more balanced along the watercourses within the model routine. This dataset provides consistency between coastal outlets and upstream sectors of rivers, which could be useful in the e.g. river deltas (if bifurcations are represented in E-HYPE).  Spatial coverage 5302 coastal outlet points along the coastline of E-HYPE4 domain (Europe)  Period and time-step 2000-2024 (daily) Contact information Pavel Terskii, researcher, SMHI. pavel.terskii@smhi.se
European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.
190K+
indexed dataset pages
32
countries and EU institutions
2019
API-first since
Free API quota
for evaluation and prototypes
SLA
history and push on production APIs
FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.
Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.
Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.
Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.
Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

European data discovery with free evaluation access and production-grade API options.

Copyright © 2026. Made by Apitalks