Object Data Base
The object oriented data base in WaterWare is implemented on industry standard relational data base engines
(RDBMS) such as ORACLE, MySQL, or PostgreSQL, with a high level of normalization.
The data base implementation supports basic numerical, symbolic, and hypermedia formats (text, imagery, video),
as well as an easy-to-use interactive menu driven interface,
and display, editors, and analysis tools. OBJECTS are dynamically instantiated when accessed,
so the system is always up-to-data, in real time.
See also: Object data base, Manual pages.
The (River Basin) OBJECT data base, that covers any and all functional elements in the system
including extensive META DATA, descriptive and administrative information beyond
the structured attribute sets that are used by the various models and analytical tools.
The range of initial OBJECT classes (open for easy extension) is listed
in the software description attached; typical examples relate to the NODES and REACHES
of the basin network representation, and include classes such as (sub)catchments,
wells, reservoirs, cities/municipalities, irrigation districts, industries,
monitoring stations/sensors, the river (channel segments) itself, aquifers, etc.
All these objects are georeferenced.
The objects are accessible from various links from related OBJECTS or model scenarios, and from a central
OBJECT CLASS selector. On-line example of an
OBJECT CLASS selector and OBJECTS data base
(Damodar test/demo case). A good, generic exmaple to explore is:
Cities, that are major demand nodes in Waterware. Please note that "guest" access is read-only !
| River basin (sub-catchment) object and associated time series
|| City (edmand) object, including land use and economic data summary
|| Farm object, economic data editor
|| Reservoir object, editor and unit conversion tool
Please note: each of the thumbnail screendumps leads to a full resolution version of that screendump.