Date post: | 05-Dec-2014 |
Category: |
Education |
Upload: | cafe-geoframe |
View: | 898 times |
Download: | 4 times |
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
GEOFRAME
Prof. Riccardo RigonIng. Andrea AntonelloIng. Silvia Franceschi
Ing. Davide Giacomelli
Trento, 17 gennaio 2007
Contents
The Nuovo Adige model is a hydrologicaI model:
working in continuous; with real time data acquired from database; fit to simulate low water periods on the whole basin; calculating water balance; built on international standards (CUAHSI, OPENMI).
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
NUOVO ADIGE MODEL
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
DECISION MAKING
EVALUATION OF STRATEGIES THROUGH MODELS
STRATEGIES FOR POLICY MAKERSDATA INTERPRETATION
EVALUATION OF STRATEGIES THROUGH MODELSEVALUATION OF STRATEGIES THROUGH
MODELS
DATA INTERPRETATIONDATA INTERPRETATION
STRATEGIES FOR POLICY MAKERSSTRATEGIES FOR POLICY MAKERS
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
HYDROLOGICAL MODELS
DataParametersEquations
Mass, momentum and energy conservation. Chemical transformations
Forcings and observables
Equation’s constant. In time! In space they are heteorgeneous
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
HYDROLOGICAL MODELS
DataParametersEquations
Mass, momentum and energy conservation. Chemical transformations
Forcings and observables
Equation’s constant. In time! In space they are heteorgeneous
Numerics, boundary and initial conditions
Data Assimilation. Data Models. Tools for Analysis.
Calibration, derivation from proxies
Reservoirs and
withdrawals
EvapotranspirationRainfall
Runoff and Routing
Snow
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
HYDROLOGICAL SUBMODELS
EASY
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
Interacting in the simplest way in line with the complexity
of the problem
USER’S POINT OF VIEW
EASY
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
Interacting in the simplest way in line with the complexity
of the problem
USER’S POINT OF VIEW
OPEN SOURCE
NOT bound to closed and reserved
architectures
EASY
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
Interacting in the simplest way in line with the complexity
of the problem
USER’S POINT OF VIEW
OPEN SOURCE
NOT bound to closed and reserved
architectures
FLEXIBLE
A system that can evolve in time if new demand are manifested
FLEXIBILITY from modeling point of view means allowing new models integration, by the way the knowledge of dynamics increases or new numeric methods are defined, with no change on EXTERNAL system structure (i.e. Implementing “plug-ins” method)
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
COMPONENTS
AnalysisTools (UNITN/R)
Database (PostgresSQL/PostGIS/HSQL/H2/CUAHSI)
Models(UNITN/OpenMI)
Interfaces(Java/udig/JGrass/BeeGIS)
users webexternal database
• JGrass – Is GIS platform developed by CUDAM,
Hydrologis and ICENS, E’ la piattaforma GIS
sviluppata da CUDAM, Hydrologis e ICENS,
GRASS and ESRI compatible. All data and
model interface development is based upon
JGRASS 3.0 standards
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
GLOSSARY
• CUAHSI - Consortium of Universities for the
Advancement of Hydrologic Science (representing
more than one hundred United States universities)
provides web services, tools, standards and
procedures that enhance access to more and better
data for hydrologic analysis. CUDAM is CUAHSI
international member. Nuovo Adige is developed
upon consortium specifications.
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
GLOSSARY
• OPENMI - I a set of specification for models integration. Originally developed in the HarmonIT EU project (DHI and Wallingfort software, among others).
All model OpenMI compliant can be connected and used
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
GLOSSARY
• PostgreSQL/PostGIS is an Open Source relational database including geographic extensions (i.e. the management of geometric features)
• Arc Hydro, is the database archietecture adopted by CUAHSI as base of its hydrological data management system.
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
GLOSSARY
• DSpace - Is the DIGITAL archive developed by MIT for the management of several (non geographic data sets)
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
GLOSSARIO
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
Nuovo Adige Implements the concept of
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
FROM CUAHSI PROJECT
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
From Maidment, 2006
Hydrovolume
Geovolume
FROM CUAHSI PROJECT
Residence time distribution
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
Discharge rating curve From Maidment, 2006
FROM CUAHSI PROJECT
AdB Adige – CUDAM - Bilancio idrico di superficie di primo livello
J-HYDRO:The network structure
Resolution level 5Resolution level 4Resolution level 3Resolution level 2Resolution level 1
AdB Adige – CUDAM - Bilancio idrico di superficie di primo livello
J-HYDRO:The network structure
Resolution level 4Resolution level 3Resolution level 2Resolution level 1
AdB Adige – CUDAM - Bilancio idrico di superficie di primo livello
J-HYDRO:The network structure
Resolution level 3Resolution level 2Resolution level 1
AdB Adige – CUDAM - Bilancio idrico di superficie di primo livello
J-HYDRO:The network structure
Resolution level 2Resolution level 1
AdB Adige – CUDAM - Bilancio idrico di superficie di primo livello
J-HYDRO:The network structure
Resolution level 1
AdB Adige – CUDAM - Bilancio idrico di superficie di primo livello
Database (PostgresSQL/PostGIS/CUAHSI)
Netnode related to network and basins
Time series are linked to monitoring points:
AdB Adige – CUDAM - Bilancio idrico di superficie di primo livello
Database (PostgresSQL/PostGIS/CUAHSI)
Summary of all monitoring points in database
AdB Adige – CUDAM - Bilancio idrico di superficie di primo livello
Database (PostgresSQL/PostGIS/CUAHSI)
Database (PostgresSQL/PostGIS/CUAHSI)
Lasa
An example of time series linked to a monitoring point, extracted from database
Rainfall (id=216) Wind velocity (id=217)
Temperature (id=219)Wind direction (id=218)
AdB Adige – CUDAM - Bilancio idrico di superficie di primo livello
• Geometries insertion;
• Positioning of cross sections;
• Lake intersections;
• Computation of water withdrawal;
• Time series updating.
AdB Adige – CUDAM - Bilancio idrico di superficie di primo livello
Database (PostgresSQL/PostGIS/CUAHSI)
Tools have been developed to managing insertion and creation of geometries and time series data, necessary to models’ run:
GEOMETRIES INSERTION
• Copying geometries from shapefiles to database tables; • Extracting topological nodes from net geometries;• Creating links between different geometries (nets, net nodes,basins).
AdB Adige – CUDAM - Bilancio idrico di superficie di primo livello
Database (PostgresSQL/PostGIS/CUAHSI)
POSITIONING OF CROSS SECTIONS
• Finding intersections between network and CROSS sections;• Computation of new nodes progressive distance, and network updating;• Copying new informations to analysis tables.
AdB Adige – CUDAM - Bilancio idrico di superficie di primo livello
Database (PostgresSQL/PostGIS/CUAHSI)
LAKE INTERSECTIONS
• Finding intersections between network and lake geometries;• Labeling intake nodes and outtake nodes;• Copying new node informations to node tables.
AdB Adige – CUDAM - Bilancio idrico di superficie di primo livello
Database (PostgresSQL/PostGIS/CUAHSI)
COMPUTATION OF WATER WITHDRAWAL
• Evaluating maximum available discharge to withdrawal, for different destination uses and different time periods.
AdB Adige – CUDAM - Bilancio idrico di superficie di primo livello
Database (PostgresSQL/PostGIS/CUAHSI)
TIME SERIES UPDATING
• Rewriting input file to SQL;• Linking time series to related monitoring points;• Creating new metadata.
AdB Adige – CUDAM - Bilancio idrico di superficie di primo livello
Database (PostgresSQL/PostGIS/CUAHSI)
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
Models (UNITN/OpenMI)
AdB Adige – CUDAM - Difesa idrogeologica e bilancio idrico nel bacino dell’Adige
Models (UNITN/OpenMI)
The approach to hydrological modeling is different for peripheral zones
of Adige basin, where natural outflow is preponderant, and for main
river channels where instead is fundamental to consider artificial
works: Basin peripheral area: a Rainfall-Runoff model (called GEOcuencas) is
used; Main river: a 1D routing model is used for discharge evaluation,
counting both natural and artificial intakes and withdrawals, if there
are.
Models (UNITN/OpenMI)
Reservoirs and
withdrawals
EvapotranspirationMeteo Forcing
Runoff and Routing
Snow
Modelli (UNITN/OpenMI)
Meteo Forcing
Evapotranspiration Evapotranspiration evaluation model
•Kriging rainfall spatial interpolationTemperature spatial interpolation
Snow Snow height evaluation on different quote layers model
Runoff
Infiltration Partitioning rainfall/infiltration model
Geomorphological runoff model
Models (UNITN/OpenMI)
Hydrological modeling data automatically extracted from DB are:
geometries (network structure) time series (hydrometers and weather stations) withdrawals data reservoirs data
The hydrological model can be run in any of the critical points in the basin:
• nodes: points in basin like: hydrometers, artificial reservoirs, lakes, points where you
want to evaluate discharge; macrobasins: areas marked by drainage divides and a node, o located between two
consecutive nodes; basic basins: basic hydrologic unit; with surface < 2 km2.
Models (UNITN/OpenMI): the digital watershed
Geometries for model execution are created for any single simulation, thanks to a
hierarchical numbering scheme, based on Pfafstetter numbering scheme (Verdin and
Verdin, 1999).
Models (UNITN/OpenMI): dynamic database
In this way one can extract upstream elements, starting from current net Pfafstetter
number, so you can navigate the whole network and build related basins. Then
macrobasins are created, closed on the node selected by the user for current
simulation.
Modelli (UNITN/OpenMI): network geometries creation
Models (UNITN/OpenMI): selecting closure nodes
Models (UNITN/OpenMI): selecting closure nodes
Models (UNITN/OpenMI): viewing macro basins
non active nodes
Models (UNITN/OpenMI): macro basins
Meteorological data used by models are: rainfall temperature pressure moisture wind velocity solar radiation
These data are evaluated on basic basins.
Meteo Forcing Needed and Managed
Meteo Forcing
Distributed model splits any basic basin (max area 5 km2) in altitude
layers and bands; evaluates stored rain water depth and possible snow melting;Create a filter between measured rain water and hydrological model,
modifying model input
Snow
Runoff
•Routing model solves Saint Venant equations, and sets the
required hydrodynamic 1D parameters;Numerical integration of 1D model uses difference finite
scheme;The initial condition is given by uniform flow upon the whole
domain;Boundary conditions are defined upstream/downstream
depending on flow regime;Generic cross sections could be used;Intakes and withdrawals are evaluated;
Routing
withdrawal: to Montecatini channel
Routing: intakes and withdrawals
intake to Adige from Montecatini channel
withdrawal from Adige to Biffis channel
Routing: intakes and withdrawals
Routing: intakes and withdrawals
Villa Lagarina Marco
Routing: longitudinal profile
User Interfaces(Java/JGRASS)
Open Source GIS developed by CUDAM and Department of Civil and Environmental Engineering of University of Trento, collaborating with HydroloGIS
•Open Source GIS developed by CUDAM and Department of Civil and Environmental Engineering of University of Trento, in collaboration with HydroloGIS•Mainly targeted environmental analysis, joins a user friendly interface and a complex analysis engine, partially developed on purpose, partially derived from GRASS
User Interfaces(Java/JGRASS)
•Open Source GIS developed by CUDAM and Department of Civil and Environmental Engineering of University of Trento, in collaboration with HydroloGIS•Mainly targeted environmental analysis, joins a user friendly interface and a complex analysis engine, partially developed on purpose, partially derived from GRASSDisplays vector data from database
User Interfaces(Java/JGRASS)
INTERFACCIA GRAFICA: JGrass
DATABASE CONNECTION
LAYERS VIEW
User Interface (JGRASS)
ATTRIBUTE TABLE VIEW
User Interface (JGRASS)
User Interface (JGRASS)
•Open Source GIS developed by CUDAM and Department of Civil and Environmental Engineering of University of Trento, in collaboration with HydroloGIS•Dedicated mainly to environmental analysis, joins a user friendly interface and a complex analysis engine, partially developed on purpose, partially derived from GRASS•Displays vector data from databaseDisplays several different data (not in DB) like shapefiles, rasters, DEM, satellite images…
User Interface (JGRASS)
User Interface (JGRASS)
User Interface (JGRASS)
•Open Source GIS developed by CUDAM and Department of Civil and Environmental Engineering of University of Trento, in collaboration with HydroloGIS•Dedicated mainly to environmental analysis, joins a user friendly interface and a complex analysis engine, partially developed on purpose, partially derived from GRASS•Displays vector data from database•Displays several different data (not in DB) like shapefiles, rasters, DEM, satellite images… •Sets closure point, to evaluate flood hydrograph
User Interface (JGRASS)
User Interface (JGRASS)
•Open Source GIS developed by CUDAM and Department of Civil and Environmental Engineering of University of Trento, in collaboration with HydroloGIS•Dedicated mainly to environmental analysis, joins a user friendly interface and a complex analysis engine, partially developed on purpose, partially derived from GRASS•Displays vector data from database•Displays several different data (not in DB) like shapefiles, rasters, DEM, satellite images… •Sets closure point, to evaluate flood hydrograph •Rules models’ run•Sets models are going to be used
User Interface (JGRASS)
User Interface (JGRASS)
•Open Source GIS developed by CUDAM and Department of Civil and Environmental Engineering of University of Trento, in collaboration with HydroloGIS•Dedicated mainly to environmental analysis, joins a user friendly interface and a complex analysis engine, partially developed on purpose, partially derived from GRASS•Displays vector data from database•Displays several different data (not in DB) like shapefiles, rasters, DEM, satellite images… •Sets closure point, to evaluate flood hydrograph •Rules models’ run•Sets models are going to be used•Turning on/off monitoring points like reservoirs and hydrometers
User Interface (JGRASS)
•Open Source GIS developed by CUDAM and Department of Civil and Environmental Engineering of University of Trento, in collaboration with HydroloGIS•Dedicated mainly to environmental analysis, joins a user friendly interface and a complex analysis engine, partially developed on purpose, partially derived from GRASS•Displays vector data from database•Displays several different data (not in DB) like shapefiles, rasters, DEM, satellite images… •Sets closure point, to evaluate flood hydrograph •Rules models’ run•Sets models are going to be used•Turning on/off monitoring points like reservoirs and hydrometers•Setting simulation parameters
User Interface (JGRASS)
User Interface (JGRASS): setting simulation parameters
•Open Source GIS developed by CUDAM and Department of Civil and Environmental Engineering of University of Trento, in collaboration with HydroloGIS•Dedicated mainly to environmental analysis, joins a user friendly interface and a complex analysis engine, partially developed on purpose, partially derived from GRASS•Displays vector data from database•Displays several different data (not in DB) like shapefiles, rasters, DEM, satellite images… •Sets closure point, to evaluate flood hydrograph •Rules models’ run•Sets models are going to be used•Turning on/off monitoring points like reservoirs and hydrometers•Setting simulation parameters•Viewing simulation resultPossible simulation saving in both HSQL and PostgreSQL/Postgis database
User Interfaces (JGRASS)
Viewing simulation result:Measured and forecasting discharge
Rainfall and snow contribution
User Interface (JGRASS): simulation run
12/09/2007 - 14-09/2007
Routing: flood hydrograph in Villa Lagarina
Routing: Leno intake
Routing: Montecatini withdrawal
Routing: uniform flow profile
Routing: activation of intakes and withdrawals
Leno intake
Routing: activation of intakes and withdrawals
Montecatini withdrawal
Routing: activation of intakes and withdrawals
Leno intake
Routing: activation of intakes and withdrawals
Montecatini withdrawalLeno intake
Snow
MODELS INTEGRATIONOpenMi: standard way to models integrationPossible changing models for the same computationManaging temporal cycle directly from JGrassPossible different languages models integration: Java, Fortran, CPossible run of several OpenMi compliant models (Sobek, HecRAS, Mike 11...)
Thank you!