Understanding Data Volume and Packages

This section provides preliminary information on 3DGlobe service’s data model classes that will help you understand how imported objects count toward the package you have purchased.

This topic contains the following sections:

This page discusses:

Data Universe and Pivot Object Definitions

This section provides preliminary information on 's data model classes that will help you understand how imported objects count toward the package you have purchased.

Data Universe

Data Universe defines the set of objects imported into the out-of-the-box application, organized in a predefined taxonomy of classes.

The out-of-the-box taxonomy of classes of 3DGlobe is as follows:

  • referential
  • source / document / layer
  • metadata
  • dataset
  • experience
  • geoitem / cruncheditem / geoitem proxy.

Pivot Objects

Pivot Objects are data and objects that are imported into the following classes:

GeoItem, CrunchedItem & GeoItem Proxy classes (and derivative classes of geoitem, cruncheditem & geoitem proxy, if any).

Note: To know if your instance of 3DGlobe has derivative classes, you can see its data model by going to Exalead CloudView Administration Console (http://<HOSTNAME>:<BASEPORT+1>/admin) > Data Model.

Volume of Data

The maximum number of Pivot Objects that can be imported into an instance of your 3DGlobe application depends on the package you purchased:

3 Millions Pivot Objects if you purchased the City Index (C4X) package.

Note: You can purchase several City Index (C4X) to increase this capacity.

Limitations

The use of documents indexed in the context of 3DGlobe is exclusively limited to City applications.

Unless specifically authorized, Data Universe cannot be enriched with custom classes. Only derivation of out-of-the-box pivot object classes is permitted.