4DMED project - Hydrological datasets
4DMED-Hydrology project aims at achieving this objective by developing and validating a novel and advanced set of EO-based products that together with additional information (in-situ data, model results) may provide an accurate reconstruction of the Mediterranean Land “Earth system”, its land-atmosphere interactions and relevant processes (also human activities) based on the latest advances in EO technology (4DMed-Hydrology dataset). Further information can be found on the official website: https://www.4dmed-hydrology.org/.
The data have been collected by the partners responsible for each site and organized in a project database to be shared among the team members, ensuring that all of them can work on the same data versions.
The database contains observations concerning the following variables: river discharge, in situ soil moisture, actual ET from eddy covariance stations, snow depth and snow water equivalent, groundwater and irrigation measurements.
Data sources
The 4DMED-Hydrology project involves a consortium led by CNR-IRPI and comprises the following organizations:
- Vienna University of Technology (TU Wien), hereinafter TUWIEN;
- Ghent University (Ghent University) hereinafter UGent;
- CIMA Research Foundation (CIMA RESEARCH FOUNDATION), hereinafter CIMA;
- Estellus (ESTELLUS SAS), at Paris Observatory, hereinafter ESTELLUS;
- Universitat Ramon Llull, Observatori de l’Ebre (OBSERVATORI DE L’EBRE), hereinafter OBSEBRE;
- KULeuven, Department of Earth and Environmental Sciences, Division Soil and Water Management (KATHOLIEKE UNIVERSITEIT LEUVEN), hereinafter KULeuven;
- VanderSat (VANDERSAT B.V.) hereinafter VANDERSAT;
- Eurac Research, Institute for Earth Observation (EURAC RESEARCH - ACCADEMIA EUROPEA DI BOLZANO), hereinafter EURAC;
- HydroSciences Montpellier (INSTITUT DE RECHERCHE POUR LE DÉVELOPPEMENT), hereinafter HSM.
Tables description
The fourdmed_hydro schema contains the time series (ts) tables listed below:
Table name | Description | Data type | Data provider |
---|---|---|---|
ts_hydro_soilmoisture_hourly | STEMS Soil moisture data at different from depth 10 cm to 50 cm with hourly temporal step (Po Basin, Italy) | real | STEMS |
ts_hydro_soilmoisture_hourly_france | Soil moisture data at different depth from 5 cm to 30 cm with hourly temporal step (France) | real | SMOSMANIA |
ts_hydro_soilmoisture_hourly_tunisia | Soil moisture data at 5 cm (Tunisia) | real | IRD institute |
ts_hydro_soiltemperature_hourly_france | Soil temperature data at different depth from 5 cm to 30 cm with hourly temporal step (France) | real | SMOSMANIA |
ts_hydro | Snow depth, discharge - streamflow, canal, hydroelectric, reservoir, piezometer - soil moisture 30 cm, soil moisture 5 cm -, precipitation depth (Italy, Spain, Marocco, Tunisia) | real | CIMA, SAIH |
ts_hydro_po_areas_daily | Irrigation and irrigation volumetric with daily temporal step related to areas of Budrio, Brunel, Faenza, Fosdondo (Italy) | real | Italian National Rainfall Network |
ts_hydro_po_areas_hourly | Irrigation, rainfall, temperature, soil moisture first layer, soil moisture second layer, irrigation volumetric with hourly daily step related to areas of Budrio, Brunel, Faenza, Fosdondo (Italy) | real | Italian National Rainfall Network, MERIDA Reanalysis product (Bonanno et al., 2019 |
ts_evaporation_soil_moisture | Various parameter related to Evaporation and soil moisture data collected by stations spread in various country | double precision | EFDC, FLUXNET-CH4, ICOS, ISMN |
Web Map Service
Station’s location is visible by means of a spatial layer that can be accessed by a GIS client (or R) to compose maps using the WMS service, with the keyword "4dmed" to filter the layer list.
A preview about stations location is provided here or by opening this MAP.
When clicking on each point, a small window will appear listing some useful information about the selected station.
Data Access
Access is possible using a RESTfull-API available for all users at this URL:
A generic request can be formulated as follows: 4dmed.eodchosting.eu/TABLENAME/OPTIONALFILTERS
.
The API provides datasets in JSON format that can be downloaded by many clients like a web browser, Linux shell, R, Python, etc. Documentation is available here: General documentation and Client-Side libraries.
Here you can find some examples describing preliminary queries to start using the database:
Example of querying data by Linux shell
curl --location --request GET 'https://4dmed.eodchosting.eu/4dmed_stations?id_station=eq.30009001&date=gte.2018-01-01' --header 'Authorization: Bearer SECRET_TOKEN_HERE'
To get the secret token, please write to bartolomeo.ventura@eurac.edu
To simplify the request it is possible to save the token in a local variable. Further information can be found here. You can find an example in the following lines:
export TOKEN="SECRET_TOKEN_HERE"
curl --location --request GET 'https://4dmed.eodchosting.eu/4dmed_stations' --header "Authorization: Bearer ${TOKEN}"
DB connection (only authorized users)
The direct connection to PostgreSQL 4dmed-DB is possible using different clients (R, Python, PgAdmin etc.) and/or by a basic, but powerful, web interface for data preview and queries. The connection is possible for all project partners. Here you can find the necessary information for the connection:
host: 4dmed.eodchosting.eu
name: 4dmed (schema: fourdmed_hydro)
Port: 2222
username: 4dmed_user (read-only)
password: write to <bartolomeo.ventura@eurac.edu> and/or <andrea.vianello@eurac.edu>
Example using JupyterLab notebook
A generic request can be formulated as follows: 4dmed.eodchosting.eu/TABLENAME/OPTIONALFILTERS
.
A more specific example is illustrated in the next lines:
#connection and query with filter:
import requests
url = 'https://4dmed.eodchosting.eu/ts_hydro?id_station=eq.30009001&date=gte.2018-01-01'
headers = {"Authorization": "Bearer SECRET_TOKEN_HERE"}
resp = requests.request("GET",url, headers=headers)
data = resp.json()
#print of the json file
data
Contacts
If you have any scientific questions, please contact:
For technical support about this documentation, please contact: