Presentation is loading. Please wait.

Presentation is loading. Please wait.

SMART INCO-MED 1 st Management Board Meeting, June 13-15 2003NCRS, Beirut WaterWare Data Requirements DDr. Kurt Fedra ESS GmbH, Austria

Similar presentations


Presentation on theme: "SMART INCO-MED 1 st Management Board Meeting, June 13-15 2003NCRS, Beirut WaterWare Data Requirements DDr. Kurt Fedra ESS GmbH, Austria"— Presentation transcript:

1 SMART INCO-MED 1 st Management Board Meeting, June 13-15 2003NCRS, Beirut WaterWare Data Requirements DDr. Kurt Fedra ESS GmbH, Austria kurt@ess.co.at http://www.ess.co.at Environmental Software & Services A-2352 Gumpoldskirchen DDr. Kurt Fedra ESS GmbH, Austria kurt@ess.co.at http://www.ess.co.at Environmental Software & Services A-2352 Gumpoldskirchen

2 WaterWare Data Requirements Domain definitionDomain definition RiverBasin OBJECTSRiverBasin OBJECTS Network topologyNetwork topology Driving forces (hydrometeorology) and rainfall-runoff model dataDriving forces (hydrometeorology) and rainfall-runoff model data Demand data, allocation rulesDemand data, allocation rules Observation data (calibration)Observation data (calibration) Cost functionsCost functions Domain definitionDomain definition RiverBasin OBJECTSRiverBasin OBJECTS Network topologyNetwork topology Driving forces (hydrometeorology) and rainfall-runoff model dataDriving forces (hydrometeorology) and rainfall-runoff model data Demand data, allocation rulesDemand data, allocation rules Observation data (calibration)Observation data (calibration) Cost functionsCost functions

3 WaterWare Data Requirements Domain definitionDomain definition RiverBasin OBJECTSRiverBasin OBJECTS Network topologyNetwork topology Driving forces (hydrometeorology) and rainfall-runoff model dataDriving forces (hydrometeorology) and rainfall-runoff model data Demand data, allocation rulesDemand data, allocation rules Observation data (calibration)Observation data (calibration) Cost functionsCost functions Domain definitionDomain definition RiverBasin OBJECTSRiverBasin OBJECTS Network topologyNetwork topology Driving forces (hydrometeorology) and rainfall-runoff model dataDriving forces (hydrometeorology) and rainfall-runoff model data Demand data, allocation rulesDemand data, allocation rules Observation data (calibration)Observation data (calibration) Cost functionsCost functions

4 WaterWare Data Requirements Domain definition 1.Location, size, boundaries 2.GIS data (topography, DEM, landuse, surface water, administrative boundaries, infrastructure ) 3.Imagery, hypertext, MM Domain definition 1.Location, size, boundaries 2.GIS data (topography, DEM, landuse, surface water, administrative boundaries, infrastructure ) 3.Imagery, hypertext, MM

5 WaterWare Data Requirements Domain definitionDomain definition RiverBasin OBJECTSRiverBasin OBJECTS Network topologyNetwork topology Driving forces (hydrometeorology) and rainfall-runoff model dataDriving forces (hydrometeorology) and rainfall-runoff model data Demand data, allocation rulesDemand data, allocation rules Observation data (calibration)Observation data (calibration) Cost functionsCost functions Domain definitionDomain definition RiverBasin OBJECTSRiverBasin OBJECTS Network topologyNetwork topology Driving forces (hydrometeorology) and rainfall-runoff model dataDriving forces (hydrometeorology) and rainfall-runoff model data Demand data, allocation rulesDemand data, allocation rules Observation data (calibration)Observation data (calibration) Cost functionsCost functions

6 WaterWare River Basin Object: –Sub-catchments –Reservoirs, hydraulic structures –Demand Nodes: cities, industries, irrigation areas, wetlands –Monitoring stations –River network (nodes, reaches) –Aquifers River Basin Object: –Sub-catchments –Reservoirs, hydraulic structures –Demand Nodes: cities, industries, irrigation areas, wetlands –Monitoring stations –River network (nodes, reaches) –Aquifers

7 WaterWare Sub-catchments 1.Location, boundaries, DEM 2.Land use distribution 3.Channel data (length, density, cross section) 4.Precipitation, temperature (min. one year daily data) 5.Surface/groundwater consumptive use within the catchment 6.Runoff observations for calibration Sub-catchments 1.Location, boundaries, DEM 2.Land use distribution 3.Channel data (length, density, cross section) 4.Precipitation, temperature (min. one year daily data) 5.Surface/groundwater consumptive use within the catchment 6.Runoff observations for calibration

8 WaterWare River Basin Object: –Sub-catchments –Reservoirs, hydraulic structures –Demand Nodes: cities, industries, irrigation areas, wetlands –Monitoring stations –River network (nodes, reaches) –Aquifers River Basin Object: –Sub-catchments –Reservoirs, hydraulic structures –Demand Nodes: cities, industries, irrigation areas, wetlands –Monitoring stations –River network (nodes, reaches) –Aquifers

9 WaterWare Reservoirs, hydraulic structures 1.Location, size, 2.volume/depth curve 3.Release policy/rules 4.Inflow/outflow time series Reservoirs, hydraulic structures 1.Location, size, 2.volume/depth curve 3.Release policy/rules 4.Inflow/outflow time series

10 WaterWare River Basin Object: –Sub-catchments –Reservoirs, hydraulic structures –Demand Nodes: cities, industries, irrigation areas, wetlands –Monitoring stations –River network (nodes, reaches) –Aquifers River Basin Object: –Sub-catchments –Reservoirs, hydraulic structures –Demand Nodes: cities, industries, irrigation areas, wetlands –Monitoring stations –River network (nodes, reaches) –Aquifers

11 WaterWare Demand Nodes: cities, industries, irrigation areas, wetlands 1.Location, type, size (area, production, population) 2.Daily/monthly demand 3.Conveyance loss, unit specific consumptive use, return flow (quality) 4.Cost functions Demand Nodes: cities, industries, irrigation areas, wetlands 1.Location, type, size (area, production, population) 2.Daily/monthly demand 3.Conveyance loss, unit specific consumptive use, return flow (quality) 4.Cost functions

12 WaterWare River Basin Object: –Sub-catchments –Reservoirs, hydraulic structures –Demand Nodes: cities, industries, irrigation areas, wetlands –Monitoring stations –River network (nodes, reaches) –Aquifers River Basin Object: –Sub-catchments –Reservoirs, hydraulic structures –Demand Nodes: cities, industries, irrigation areas, wetlands –Monitoring stations –River network (nodes, reaches) –Aquifers

13 WaterWare Monitoring stations 1.Location 2.Type (parameters) 3.Observation time series (daily) Monitoring stations 1.Location 2.Type (parameters) 3.Observation time series (daily)

14 WaterWare River Basin Object: –Sub-catchments –Reservoirs, hydraulic structures –Demand Nodes: cities, industries, irrigation areas, wetlands –Monitoring stations –River network (nodes, reaches) –Aquifers River Basin Object: –Sub-catchments –Reservoirs, hydraulic structures –Demand Nodes: cities, industries, irrigation areas, wetlands –Monitoring stations –River network (nodes, reaches) –Aquifers

15 WaterWare River network (nodes, reaches) 1.Formal node definitions derived from OBJECTS 2.Connectivity (network topology) 3.Reach characteristics (length, cross-sections, roughness) River network (nodes, reaches) 1.Formal node definitions derived from OBJECTS 2.Connectivity (network topology) 3.Reach characteristics (length, cross-sections, roughness)

16 WaterWare River Basin Object: –Sub-catchments –Reservoirs, hydraulic structures –Demand Nodes: cities, industries, irrigation areas, wetlands –Monitoring stations –River network (nodes, reaches) –Aquifers River Basin Object: –Sub-catchments –Reservoirs, hydraulic structures –Demand Nodes: cities, industries, irrigation areas, wetlands –Monitoring stations –River network (nodes, reaches) –Aquifers

17 WaterWare Aquifers 1.Location, extent 2.Depth, volume, porosity 3.Any observation data (head, flow, pumping tests, etc) 4.Recharge (natural and injection) 5.Withdrawals (pumping) Aquifers 1.Location, extent 2.Depth, volume, porosity 3.Any observation data (head, flow, pumping tests, etc) 4.Recharge (natural and injection) 5.Withdrawals (pumping)

18 WaterWare Data Requirements Domain definitionDomain definition RiverBasin OBJECTSRiverBasin OBJECTS Network topologyNetwork topology Driving forces (hydrometeorology) and rainfall-runoff model dataDriving forces (hydrometeorology) and rainfall-runoff model data Demand data, allocation rulesDemand data, allocation rules Observation data (calibration)Observation data (calibration) Cost functionsCost functions Domain definitionDomain definition RiverBasin OBJECTSRiverBasin OBJECTS Network topologyNetwork topology Driving forces (hydrometeorology) and rainfall-runoff model dataDriving forces (hydrometeorology) and rainfall-runoff model data Demand data, allocation rulesDemand data, allocation rules Observation data (calibration)Observation data (calibration) Cost functionsCost functions

19 WaterWare Data Requirements Network topology 1.Node-reach structure, abstract (topological) and georeferenced Network topology 1.Node-reach structure, abstract (topological) and georeferenced

20 WaterWare Data Requirements Domain definitionDomain definition RiverBasin OBJECTSRiverBasin OBJECTS Network topologyNetwork topology Driving forces (hydrometeorology) and rainfall-runoff model dataDriving forces (hydrometeorology) and rainfall-runoff model data Demand data, allocation rulesDemand data, allocation rules Observation data (calibration)Observation data (calibration) Cost functionsCost functions Domain definitionDomain definition RiverBasin OBJECTSRiverBasin OBJECTS Network topologyNetwork topology Driving forces (hydrometeorology) and rainfall-runoff model dataDriving forces (hydrometeorology) and rainfall-runoff model data Demand data, allocation rulesDemand data, allocation rules Observation data (calibration)Observation data (calibration) Cost functionsCost functions

21 WaterWare Data Requirements Driving forces (hydrometeorology) and rainfall-runoff model data 1.ALL hydrometeorological time series (as in observation nodes) 1.Precipitation 2.Temperature 3.River flow 4.Wells (pumping rates), springs Driving forces (hydrometeorology) and rainfall-runoff model data 1.ALL hydrometeorological time series (as in observation nodes) 1.Precipitation 2.Temperature 3.River flow 4.Wells (pumping rates), springs

22 WaterWare Data Requirements Domain definitionDomain definition RiverBasin OBJECTSRiverBasin OBJECTS Network topologyNetwork topology Driving forces (hydrometeorology) and rainfall-runoff model dataDriving forces (hydrometeorology) and rainfall-runoff model data Demand data, allocation rulesDemand data, allocation rules Observation data (calibration)Observation data (calibration) Cost functionsCost functions Domain definitionDomain definition RiverBasin OBJECTSRiverBasin OBJECTS Network topologyNetwork topology Driving forces (hydrometeorology) and rainfall-runoff model dataDriving forces (hydrometeorology) and rainfall-runoff model data Demand data, allocation rulesDemand data, allocation rules Observation data (calibration)Observation data (calibration) Cost functionsCost functions

23 WaterWare Data Requirements Demand data, allocation rules 1.Demand time series (scenario specific, unit use related; specific data requirements for irrigation water demand model, incl. crops, irrigation technology), 2.Release and allocation data Demand data, allocation rules 1.Demand time series (scenario specific, unit use related; specific data requirements for irrigation water demand model, incl. crops, irrigation technology), 2.Release and allocation data

24 WaterWare Data Requirements Domain definitionDomain definition RiverBasin OBJECTSRiverBasin OBJECTS Network topologyNetwork topology Driving forces (hydrometeorology) and rainfall-runoff model dataDriving forces (hydrometeorology) and rainfall-runoff model data Demand data, allocation rulesDemand data, allocation rules Observation data (calibration)Observation data (calibration) Cost functionsCost functions Domain definitionDomain definition RiverBasin OBJECTSRiverBasin OBJECTS Network topologyNetwork topology Driving forces (hydrometeorology) and rainfall-runoff model dataDriving forces (hydrometeorology) and rainfall-runoff model data Demand data, allocation rulesDemand data, allocation rules Observation data (calibration)Observation data (calibration) Cost functionsCost functions

25 WaterWare Data Requirements Observation data (calibration) 1.River flow measurements 2.Actual supply data 3.Reservoir storage levels Observation data (calibration) 1.River flow measurements 2.Actual supply data 3.Reservoir storage levels

26 WaterWare Data Requirements Domain definitionDomain definition RiverBasin OBJECTSRiverBasin OBJECTS Network topologyNetwork topology Driving forces (hydrometeorology) and rainfall-runoff model dataDriving forces (hydrometeorology) and rainfall-runoff model data Demand data, allocation rulesDemand data, allocation rules Observation data (calibration)Observation data (calibration) Cost functionsCost functions Domain definitionDomain definition RiverBasin OBJECTSRiverBasin OBJECTS Network topologyNetwork topology Driving forces (hydrometeorology) and rainfall-runoff model dataDriving forces (hydrometeorology) and rainfall-runoff model data Demand data, allocation rulesDemand data, allocation rules Observation data (calibration)Observation data (calibration) Cost functionsCost functions

27 WaterWare Data Requirements Cost functions ANY node may have cost functions associated; generic data: discount rate NPV calculations) 1.Supply costs: 1.Investment 2.Maintenance (OMR) 2.Demand side: benefits/unit water Cost functions ANY node may have cost functions associated; generic data: discount rate NPV calculations) 1.Supply costs: 1.Investment 2.Maintenance (OMR) 2.Demand side: benefits/unit water


Download ppt "SMART INCO-MED 1 st Management Board Meeting, June 13-15 2003NCRS, Beirut WaterWare Data Requirements DDr. Kurt Fedra ESS GmbH, Austria"

Similar presentations


Ads by Google