|
Track: Federal Systems
Ernie Bergan
United States Government
333 SW 1st Ave
Portland, OR 97204-3440
Telephone: 503-326-2559
Fax: 503-326-5745
E-mail: ebergan@hevanet.com
Bob Varner, Dave O'Hara
Integrating the ArcView Query Builder with Highly Normalized Oracle Tables
In the face of tremendous pressure from Congress and the American public for more accountability and in the midst of huge budget cuts, downsizing, and spending moratoria, the USDA Forest Service is in the process of migrating from legacy tabular systems to an integrated information paradigm in a distributed client/server graphical environment. Large volumes of data exist in the legacy system within the Oracle RDBMS. Forest Service application developers are attempting to migrate various legacy tabular data sources into a highly normalized tabular corporate database, simultaneously linking that data with spatial data that will reside in ArcInfo. The complexity of meeting the business needs and enterprise requirements for a production decision support application to serve such a diverse user community, including users in intraagency and interagency roles as well as the American public, requires that applications developed in the Forest Service are bulletproof, flexible, intuitive, and easy to use. A
solution using the standard tools in ArcView is very compelling since ArcView meets the requirements for an easy-to-use GUI, and USDA FS personnel are trained to use the Query Builder. Query Builder can be used as it stands to formulate queries against normalized Oracle databases, but it does not meet a "point-and-click" directive for the GUI. A user must know the Query Builder constructs, SQL, and have an intimate knowledge of the Oracle table structures and definitions, a skill mix that few users can reasonably be expected to have. This paper discusses a USDA Forest Service solution to interface the ArcView Query Builder with highly normalized corporate data structures modeling complex dynamic segmentation event data. Example Avenue code and supporting operating system constructs necessary to implement this solution are provided.
|
|
