OPTIMA: Optimisation   for Sustainable
Water Resources Management
   

Case Study Profiles

WP01 objectives include: (see also:   /OPTIMA/ADMIN/wp01.html )
  • To compile comprehensive lists of water management issues, problems, and respective information requirements across the set of case studies; this should also be done with the involement of the local actors and stakeholders;
  • To list and document the data requirements of the proposed methods;
  • To analyse local data availability against these requirements.
Among these initial steps, basic data for all case studies in a common framework should be compiled; a proposal for a common template is given below; please note that while some of the data below may come up again in another context, there is a hierarchical structure with increasing refinements up to the level of the very detailed model data requirements (See also:   modeltools.html)

Please note: these data requirements are organised hierarchically, with decreasing importance; while we are SURE that the first few items will ALWAYS be available, some or the more detailed ones may be more difficult to outright impossible. If you are NOT SURE where to place a specific item, just addd it to the basic descriptive TEXT that should be provided for each topic/item !

Data Requirements for WP01 are described in the data lis below, but are also covered in separate tasks or work packages include. The data requirements for a case study include:

    CASE STUDY BASIC DATA as described in the TABLE below;
    WATER ISSUES On-line ISSUES QUESTIONNAIRE
    ACTORS and STAKEHOLDERS On-line STAKEHOLDER DATA BASE
    REGULATORY FRAMEWORK for water rights, ownership, utilities and services, allocation, pricing, pollution control, etc.
    GIS and RS DATA covered in more details in WP5, but the basic elements are also part of the intial basin description and data.
    TECHNO-ECONOMIC DATA are generic, across cases, but will contain local, specific parameter sets such as local costs

Case Study Basic Profiles

Please refer to the objectives of   Work Package 1   (and Deliverables D1.1 and D1.2) for the overall context.

To start, a first compilation in free text format is sufficient, plain text with simple headings, but please try to cover ALL ITEMS, even if the only information at this point is: NOT AVAILABLE (would be useful to know whether this is a temporary or principle problem in each case); Please note: this task is not so much about collecting these data, but to assess data availability in the case studies;
another on-line data base to compile the data in a common and consistent format is being prepared.

Main topicDescription of component items
Identification: For any and all items, always consider a plain text, free format summary, and do place any information item you consider relevant but that does not fit into the structure proposed into the free text !
  • Case study (and river/basin) name
  • country (can be more than one)
  • province or any other applicable administrative unit;
  • major settlements: enumerate municipalities, cities and major settlements up to some reasonable size threshold: provide name, population (and area); as a simple rule, try to cover 90% of size/volume, collect more than 10 and less than 100 objects in any class !
Description: this is basically an extension of the initial descriptions of the individual cases on-line in /OPTIMA/cases.html
  • Texfile: hypertext description, preferrably in plain text format or HTML (clean);
  • Images (separet files, with maximum size/resolution, GIF, JPEG, PNG formats)
  • Links (URL),
  • Documents: doc, pdf, PPT presentations, etc.
Location: Please note that the bounding box (RECTANGLE ....) should cover the ENTIRE area of interest, which may go beyond the immediate hydrographic catchment wherever major elements of the water resources system are located outside watershed boundaries (usually CITIES as major water users, e.g., in Turkey or Cyprus cases). Alternatively, the area of interest may CUT OFF some upstream part of a river ctachment, when the upstream part is considered as INPUT to the main system (e.g., on the Litani and in the Gulf od Tunis)
  • Bounding box (lat/long of upper left and lower right corner minimally),
  • Associated map/GIS data, satellite imagery (e.g., LANDSAT, SPOT);
For GIS data, please clearly specify the format and information on projection and coordinate system (so we can merge data from different sources !), please add information on legends, scales of original maps, reference years, ownership and copyright (see the Meta Data Section below);
Basin: data describing the basin physiography (for text and imagery, please refer to Description above):
  • Hydrographic catchment area, are study area in km2; where we have a good, high-resolution DEM, this can be determined automatically
  • Minimum and maximum elevation, m.a.s.l.; area-elevation table and curve in 100 m steps; associated GIS data: DEM (digitial elevation model)
  • River network: longest branch (mains stream), total perennial channel length for drainage density; if there is no perennial channel at all, use your judgement; associated GIS (line) coverage, preferably classified by stream/branch order. This obiously involves some subjective judgement: rivers are fractal in nature, so please do explain (in the META DATA) which rules or assumptions where used to facilitate comparison between cases !
Land use: describing land-use and land-cover, using CORINE land-use classification with special emphasis on wetlands, protected areas, etc.   For a possible use of the land use distribution (see also the land-use change model manual pages), corresponding GIS coverage, polygon or raster layers;
  • area of forest (absolute or in %)
  • agriculture (rainfed/irrigated, pastures, meadows, parks, reserves),
  • built up (urban/industrial, recreation/tourism)
  • others, including desert, beaches, dunes, mining, construction etc;
A short free-text description summarising the land-use and land-cover situation as well as any recent and current/continuing trends would also be useful. A few selected images (digital photograps) of characteristic areas illustrating the numerical data would be very useful.
Meteorology: annual total/average precipitation and temperature; min/max/average, monthly total/average time series of daily values, for any or all monitoring stations in the area of interest, including any synthetic data deemed representative for the basin/area; daily time series (representative year), examples, where available, for flood and drought conditions, long-term (multiple years) daily time series of:
  • precipitation (mm/day)
  • temperature (degC)
  • optionally:
    • humidity (%)
    • radiation/cloud cover (1/8)
    • wind speed (m/s)
    • potential evapotranspiration (mm/day)
The format of the time series data that can be imported to the case study data bases is defined in the WaterWare Manual.
Hydrology: total runoff, flow data at selected (as many as possible ..) flow monitoring stations (m³/s); groundwater: main aquifer(s), extent, volume, prorosity, conductivity, head changes, springs, wells and well fields, pumping - down to time series for larger wells and well fields, groundwater recharge; use whatever unit is natural (described in the META DATA) but ALSO convert to/use m3/s as a standard unit for comparison.
For a description of the corresponding model elements, see the Waterware Manual.
The format of the time series data that can be imported to the case study data bases is defined in the corresponding WaterWare Manual pages.
Monitoring infrastructure: list of all monitoring stations, description (text), images, related publications like hydrographic yearbooks, URLs ?
  • station name,
  • location: lat/long/elevation),
  • parameters covered (including water quality),
  • instrumentation used,
  • temporal resolution and coverage,
  • availability (in real-time ?), telemetry, analsysis.
Water budget: a basic average annual water budget in mm for easy comparison; please specify the reference year and or period the data apply to reference area (possibly use Mm³3 as a parallel unit). Components should include:
  • precipitation
  • imports (inter-basin transfers)
  • evapotranspiration,
  • groundwater extractions/recharge
  • water use (by primary sector)
  • runoff/exports
  • balance
Structures: these include all major constructions that affect water flow or quality;
  • major dams/reservoirs: name, location, size/geometry (area, depth, volume, for levels such as dead storage, active storage, flood/spill level), construction year and method, use (hydropower ?), release policy or time series.
    See also the description of the detailed model data requirements for dams/reservoirs.
  • (major) water water treatment plants
  • (major) water treatment/purification plants
  • desalination plants
  • major rticificial channels, associated weirs, gates and sluices.
Water Resources: water use by sector (domestic, industrial, agricultural, services, see the definitions in the WaterWare on-line manual), interbasin transport; Also include environmental water use, and water/flow requirements for indirect use (transportation, recreation). Water supply: surface and groundwater sources (see also: Water Budget), unconventional sources. Distribution networks and utilities, sanitation (sewering and treatment).
Demography: basic description of population and trends; please specify reference period and area (population densities); major settlements, distribution (map ?)
  • total population
  • urban/rural split/distribution
  • migration patterns
  • family/household size,
  • growth rates, birth/mortality rates
  • age/sex distribution,
  • spatial distribution (census tracts ?)
  • trends, forecasts ?
Economics: major economic activities/industries, GRP/GNP, income distribution, per capita-, family/household income, sectoral distribution, growth rates (sectoral), inflation; water prices, wastewater fees/charges.
List major entreprises/industries that are major water users or polluters.

Meta Data

To make a reliable interpretation of the data possible, they should always include, for every item:
  1. Author/source, copyright where applicable,
  2. Reference time (year/period),
  3. Method (of derivation/extimation),
  4. Unit/comments.
  5. For maps, additionally: format, projection, origin, scale/coordinate system, copyright.

© Copyright 1995-2018 by:   ESS   Environmental Software and Services GmbH AUSTRIA | print page