Hierarchical Manager Solution for Oracle Data Warehouse

The 21st century is the century of information, and the competition of comprehensive national strength is, to a large extent, the competition of information utilization. In recent years, with the proposal and implementation of the "digital earth" and "Digital Land" strategies, massive data in the field of geology is growing rapidly, and data storage, analysis, management, and processing become increasingly complex. With the maturity of Oracle technology, especially the emergence of Oracle Spatial after version 8.15, Data Warehouses have unparalleled advantages in massive data storage, analysis, and expression. At the same time, due to the huge amount of information, the traditional data storage and display methods are insufficient for large-scale data quick browsing. In this way, it is necessary to change the storage mode of spatial data and load the required spatial data, avoid repeated loading and uninstallation of unnecessary data.

Layered Manager

1. Hierarchical Manager architecture:

The layered manager is a key part for quick browsing of large-scale data. It controls the layer-by-layer refinement of the table structure and metadata definition and assignment, and defines the key information in the component table, the spatial data sources, data mining rules, layer loading ranges, and graphic editing, output, and storage are provided. The layered Manager consists of two parts:

A) a group of spatial data tables stored in the Oracle data warehouse are used to refine each detail layer in layers. These tables are called component tables;

B) an empty table that contains the structure definition of the table and the special metadata used to describe the component table. This table is called a layer-by-layer refined table. Any layer-by-layer refinement application requires layer-by-layer refinement of tables, from which you can understand the layer-by-layer keyword descriptions of layers in layer-by-layer refinement, and the hierarchical association between them. When layering, the layering manager acts as a part of the program and determines the layer and Keywords of the sub-Picture Elements to be added, so as to determine the information of the elements to be added and deleted in layer-by-layer refining layers.

A layer-by-layer refined layer is a special map layer. It is a blank layer with its own table structure and uses metadata to specify rules and restrictions for all layers to be loaded, the displayed map information is extracted from other tables or databases according to the rules specified by metadata. When a layer-by-layer refinement layer is displayed in the map, the layer manager creates a temporary table and copies the elements in the component table to the temporary table. The elements displayed in layer-by-layer refinement layers are actually copies of elements in the component table. In this way, you can flexibly load the required information on the layer. When the application ends, the temporary table is discarded. To save useful topic chart information, you can save the extracted layers. At this time, if you view the layer information, the layer-by-layer refinement layer will still be a single layer.

A layer-by-layer table refinement requirement is the core part of the organization of the layered manager. It defines metadata keywords and three standard columns: keywords, layers, and labels. It also has its own set of syntax:

(1) The begin_metadata keyword marks the beginning of the metadata section in the table layer-by-layer refinement.

(2) Each row of metadata contains two elements: keywords and values. All keywords and values are enclosed in double quotation marks.

(3) A layer-by-layer refined table must contain the \ IsDrilldown keyword. The value of this keyword must be True.

(4) Each keyword starts with "\" (backslash.

(5) Metadata keywords can be nested in hierarchies. Each layer in the hierarchy is marked with a backslash.

(6) Metadata includes the \ DDMap \ ComponentMaps \ keyword hierarchy. Specify four metadata keywords for each component table in this hierarchy.

As shown in the layered schematic of the layered manager, the layered Manager consists of two parts: a component table and a layer-by-layer refined table, the layer manager extracts data from the Oracle Data Warehouse by means of Data Mining according to system requirements to form a layer in the component table, and then determines the name and part of the layer to be loaded, and load it to a layer-by-layer table. If this is the first time a table is loaded, the layer-by-layer refinement table is a blank layer. During the loading process, the layer-by-layer refinement table continuously adds and deletes the metadata information, in this way, some information in each component table is displayed in the layers shown in the layer-by-layer refined table. In this way, output the required layer and edit it. Because layer-by-layer data refinement in the table is a copy of the component table, you need to save the edited layer to form a topic chart.

The layer manager first forms a blank layer, uses the layer manager to extract data from the Oracle Data Warehouse with data mining tools, and forms a level-1 layer according to the metadata rules of the layer manager. In this layer, by responding to the event, we can determine the name of the layer that loads the second-level layer and the loaded part of the layer. The layer-3 and layer-4 data are loaded accordingly, and various topic diagrams are formed at the same time. Of course, the implementation of the hierarchical manager function is achieved through GIS components (MapX, MO, AO, etc.) and programming languages (VB, VC, Delphi, etc.

1 2 3 Next Page

[Content navigation]
Page 1st: Oracle Data Warehouse's hierarchical Manager Solution	Page 2nd: Oracle Data Warehouse's hierarchical Manager Solution
Page 3rd: Oracle Data Warehouse's hierarchical Manager Solution