Data checklist: 2005

A general introduction on the data and information requirements for a Waterware application can be found in the

• User Manual
• OPTIMA case study profile

ITEM DESCRIPTION	Status, comments, manual links
background image for the main header image, digital photos or high-resolution color scan (TIFF) or glossy color picture of good quality, approx. A5 size.	Non-critical: this is only used for "beautification" of the interface, not for any calculations
logos (GIF ot TIFF, 200x300 pixels minimum) for the client and/or partner organisation	Non-critical: the logo is only used for the GUI/identification
domain definition in lat/long or map coordinates; should be covering a square, portrait, or landscape aspect ratio region; this should be based on hydrographic boundaries	Currently used is the entire Yangtze catchment with DEM, basin boundaries and river network from public domain sources.
case study areas definitions: for any sub-domain, as above; however, the topological river network can be defined for any arbvitrary area.	Relevant primarily for initial GIS data. We assume that the entire Yangzte basin is the primary case study; possible sub-areas are individual sub-catchments e.g, for the RRM model.
background maps for overall domain (ArcInfo export format) should be in a equidistant rectangular format, covering te above domain.	Currently used for the embedded GIS: DEM, basin boundaries and river network from public domain sources
background maps for any sub-domain(s) (ArcInfo export format) should be in a equidistant rectangular coordinate system.	As above. High-resolution maps and DEM would be very useful for smaller sub-catchments, the latter for hydrographic boundary detection. Also, all OBJECTS such as monitoring stations are shown on a zoomed in local map
DEM (1000, 500, 250, 100, 50, or 25 meter horizontal resolution, depending on domain sizes	a 1 km global DEM (public domain ETOPO30) is used as initial data set.
river basin objects (and/or ASCII attribute and geometry data files) for georeferencing.	Demos for several object classes and interactive editors are available. See: river basin object classes for available classes, definitions and data requirements.
river network: map coverage (and/or ASCII attribute and geometry data files) for river network (linked to basin objects)	To date, no USEFUL (classified) GIS coverage of the river network exists. network specifications
meteorological data observation time series: half-hourly to daily values for one calender years minimum for: air temperature, precipitation, humidity; Optional: wind speed, cloud cover, solar radiation. Please note that the time series of meteorological monitoring data have the same format and data base representation as the flow data below.	No monitoring stations defined yet. OBJECT class in installed and populated with three demo data sets of multi-year monthly flow from public domain sources.
flow data, half-hourly to daily, for at least one calender year (should match the meteorological observation period); should be related to the corrsponding river basin objects.	As above.
water quality observation data, half-hourly to daily, for at least one calender year (should match the meteorological observation period); a minimum of three stations are required for the spatial analysis functions. Please note: same data format as above; for display and analysis, only regular time series are supported.	No water quality data are available or have been implemented as of yet.
model input data, for RRM, WRM, IWDM, LUC, etc; for at least one (water) year that does not necessarily start in January and should match the available meteorological observation periods; These data consist of two main groups: parameters, and time series (dynamic inputs).	For RRM and WRM, the input data for the model scenarios are managed by interactive on-line editors including user authentication and scenario management tools.