SMART INCO-MED
1st Management Board Meeting,
June 13-15 2003NCRS, Beirut
WaterWare Data Requirements
DDr. Kurt Fedra
[email protected]
ESS GmbH, Austria
http://www.ess.co.at
Environmental Software & Services A-2352 Gumpoldskirchen
WaterWare Data Requirements
•
•
•
•
Domain definition
RiverBasin OBJECTS
Network topology
Driving forces (hydrometeorology) and
rainfall-runoff model data
• Demand data, allocation rules
• Observation data (calibration)
• Cost functions
WaterWare Data Requirements
•
•
•
•
Domain definition
RiverBasin OBJECTS
Network topology
Driving forces (hydrometeorology) and
rainfall-runoff model data
• Demand data, allocation rules
• Observation data (calibration)
• Cost functions
WaterWare Data Requirements
Domain definition
1. Location, size, boundaries
2. GIS data (topography, DEM,
landuse, surface water,
administrative boundaries,
infrastructure )
3. Imagery, hypertext, MM
WaterWare Data Requirements
•
•
•
•
Domain definition
RiverBasin OBJECTS
Network topology
Driving forces (hydrometeorology) and
rainfall-runoff model data
• Demand data, allocation rules
• Observation data (calibration)
• Cost functions
WaterWare
River Basin Object:
– Sub-catchments
– Reservoirs, hydraulic structures
– Demand Nodes: cities, industries,
irrigation areas, wetlands
– Monitoring stations
– River network (nodes, reaches)
– Aquifers
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
WaterWare
River Basin Object:
– Sub-catchments
– Reservoirs, hydraulic structures
– Demand Nodes: cities, industries,
irrigation areas, wetlands
– Monitoring stations
– River network (nodes, reaches)
– Aquifers
WaterWare
Reservoirs, hydraulic structures
1. Location, size,
2. volume/depth curve
3. Release policy/rules
4. Inflow/outflow time series
WaterWare
River Basin Object:
– Sub-catchments
– Reservoirs, hydraulic structures
– Demand Nodes: cities, industries,
irrigation areas, wetlands
– Monitoring stations
– River network (nodes, reaches)
– Aquifers
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
WaterWare
River Basin Object:
– Sub-catchments
– Reservoirs, hydraulic structures
– Demand Nodes: cities, industries,
irrigation areas, wetlands
– Monitoring stations
– River network (nodes, reaches)
– Aquifers
WaterWare
Monitoring stations
1. Location
2. Type (parameters)
3. Observation time series (daily)
WaterWare
River Basin Object:
– Sub-catchments
– Reservoirs, hydraulic structures
– Demand Nodes: cities, industries,
irrigation areas, wetlands
– Monitoring stations
– River network (nodes, reaches)
– Aquifers
WaterWare
River network (nodes, reaches)
1. Formal node definitions derived
from OBJECTS
2. Connectivity (network topology)
3. Reach characteristics (length,
cross-sections, roughness)
WaterWare
River Basin Object:
– Sub-catchments
– Reservoirs, hydraulic structures
– Demand Nodes: cities, industries,
irrigation areas, wetlands
– Monitoring stations
– River network (nodes, reaches)
– Aquifers
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)
WaterWare Data Requirements
•
•
•
•
Domain definition
RiverBasin OBJECTS
Network topology
Driving forces (hydrometeorology) and
rainfall-runoff model data
• Demand data, allocation rules
• Observation data (calibration)
• Cost functions
WaterWare Data Requirements
Network topology
1. Node-reach structure, abstract
(topological) and georeferenced
WaterWare Data Requirements
•
•
•
•
Domain definition
RiverBasin OBJECTS
Network topology
Driving forces (hydrometeorology) and
rainfall-runoff model data
• Demand data, allocation rules
• Observation data (calibration)
• Cost functions
WaterWare Data Requirements
Driving forces (hydrometeorology)
and rainfall-runoff model data
1. ALL hydrometeorological time series
(as in observation nodes)
1.
2.
3.
4.
Precipitation
Temperature
River flow
Wells (pumping rates), springs
WaterWare Data Requirements
•
•
•
•
Domain definition
RiverBasin OBJECTS
Network topology
Driving forces (hydrometeorology) and
rainfall-runoff model data
• Demand data, allocation rules
• Observation data (calibration)
• Cost functions
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
WaterWare Data Requirements
•
•
•
•
Domain definition
RiverBasin OBJECTS
Network topology
Driving forces (hydrometeorology) and
rainfall-runoff model data
• Demand data, allocation rules
• Observation data (calibration)
• Cost functions
WaterWare Data Requirements
Observation data (calibration)
1. River flow measurements
2. Actual supply data
3. Reservoir storage levels
WaterWare Data Requirements
•
•
•
•
Domain definition
RiverBasin OBJECTS
Network topology
Driving forces (hydrometeorology) and
rainfall-runoff model data
• Demand data, allocation rules
• Observation data (calibration)
• Cost functions
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