This page documents only additional information for use of Asset Inventory in Client/Server.
It is recommended to read first Manage Asset Inventory Themes.
Optionally, you may want to organize each feature extraction project in a separated Inventory Database :
Optionally, you may need other GIS reference resources :
Optionally, you may want to organize each feature extraction project in a separated Orbit Workspace :
Create new Inventory Themes
Review Dataset Permissions of newly added Themes.
Roles on extensions and permissions on datasets can be managed via the EOS Console, see EOS Roles and Permissions.
The Asset Inventory administration procedures, Create, Import, and Remove Theme affect the Orbit EOS configuration.
To operate these procedures the user must belong to the EOS usergroup “administrators”, see EOS Console.
At Import and Export Theme the EOS Service requires file access to the selected resource files and/or file directory. Import or Export will be successful if the EOS Service can read the files and directory using the path defined by Desktop Client user.
Note mapped network drives are not available to an Operating System service, see Orbit Enterprise Service > File Access and Permissions.
Any server side available database connection can be used as inventory database. No restrictions nor conditions.
Define the database connections in the EOS console > Resources > Databases.
Inventory Themes are special datasets. All “dataset conditions” are automatically fulfilled when using the Asset Inventory administration procedures, see Manage Asset Inventory Themes.
However, it is possible to create and configure manually the Inventory Theme database table scheme. Following conditions must be respected :
Theme Table Scheme
Use the database management tool (Workbench, Navicat, Toad, …) to update Table Design and Add Table Columns.
OG_ObBJ_ID
(integer), AIM_CREATE_DATE_TIME
(string), AIM_CREATE_USER
(string), AIM_LAST_MOD_DATE_TIME
(string), AIM_LAST_MOD_USER
(string), AIM_REF_ID
(string), AIM_ANNOTATION
(string)
Theme Declaration
Configure the Dataset as Inventory Theme by adding its internal EOS registry name into the themes.xml configuration file:
<Orbit installation directory>/server/data/datasets/inventories/themes.xml
Dataset Legend
Add the dataset (<theme>.odb) as Local Resources (not via EOS) to the Orbit Desktop Client and update the Dataset Legend, see Local vs EOS resources.
<Orbit installation directory>/server/data/datasets/inventories
Theme Snapshot and Documents
Inventory Snapshots and Documents are stored in an open file structure by Inventory Theme and Object ID.
The default storage location is :
<Orbit installation directory>/client/data/inventories/<theme>/<object id>/
Storage location and configuration can be adjusted via the according service configuration file1). :
<Orbit installation directory>/server/program/services/ext_inventory_suite/properties.ini
On doing Asset Inventory on large scale (+ 100,000 objects for one Theme) the Theme Snapshot Table can become very large. Indexing database the table columns “Name”, “Obj_id” and “Theme” is advised when an Inventory Object insert takes increasingly more time.
A newly created inventory theme is been by default a 3D dataset. All objects will be saved with X,Y and Z.
If required it is possible to set the theme to a 2D dataset :
Edit and adjust the coordinate model tag in the appropriated .odb file from “3D” to “2D” using a text editor.
<Orbit Installation>/server/data/datasets/inventories/<inventory database>/<theme>.odb
Only possible for point datasets.
Existing 3D points can be converted into 2D objects by updating their Z values using a database query :
Update <table_name> Set OG_COORD_Z = 0
Unload the EOS dataset to take advantage of the updated dataset structure, see Resources > Datasets > Dataset Setup