Schemas

The schema of data defines it’s structure in terms of the list of classes, their hierarchy and the attributes defined within those classes.

There are a number of ways of changing or making use of the schema of the data being read in from data stores. Schemas are defined by Data Stores and are inferred from the data within a data store and can also be modified by adding custom classes and attributes to the data store’s input mapping.

Schema Mapping

Schema mapping refers to changing the names of the input/output classes or attributes so that they match a central naming convention used by rules and actions.

Use schema mapping for simple name changing but it cannot handle more complex transformations such as the attributed values themselves need to be converted, or when not all features in a class are transformed. For more complex transformations use the Schema Transformation tool.

Schema mapping is performed in the data store input and output mapping user interfaces.

For more information see Schema mapping.

Schema Transformation

Schema Transformation is a Session Task that reads input data classes and creates new objects in the output classes. This is achieved by copying the objects from the input classes, so the session will contain both the source and the target objects at the same time.

For more information, please see Schema Transform.

System Schema Classes

As well as the classes of the data defined by the Data Stores in the Open Data tasks, other classes are available for writing rules and actions.

These are:

• Standard superclasses:All

• All:geometric

• All:Non-Geometric (added whenever Use Schema is enabled).

These represent any feature in the 1Integrate cache, any feature from a geometric class and any feature from a non-geometric class respectively.

Note: A feature with a null geometry still counts as being in the All:geometric class.

System Schema Classes

System Schema classes which are added whenever Use Schema and Use System Schema are enabled and include:

• Singleton. A helper class which contains just one object and is useful to run rules or actions only once per session. See Singleton Class for more information.

• Topology classes (node, edge, face) which are only populated when a build topology task is run on a session. See Topology Primitives for more information.

• Connectivity network class which is only populated when calling network connectivity check built-in operations using Network Graphs. See Networks for more information.