Input Mapping

Source and target maps are defined in the Input Mapping. The map is organised into attributes within classes.

1Integrate supports complex attributes such as arrays, references, and composite structures but loading data using those structures is less common as it depends on the data formats and the specific data store capabilities.

The Source The Source column shows the tables/classes/layers and columns/attributes from the schema for the external data source.

The Target column maps tables and columns to classes and attributes in 1Integrate.

Creating Input Mappings

After setting up the input connection details (see Input Connection), map the input schema to the 1Integrate schema by selecting existing classes and attributes from the external data source schema, and adding new classes and attributes where necessary.

You can override the name and type of each attribute (unless you are using an Ontology). By default, 1Integrate is populated with the same names as the external data source and the data types are selected based on the data type in external data source. 1Integrate also indexes geometry columns and the primary keys of the source data.

Only checked items will be analysed in 1Integrate.

Input Mapping Toolbar Icons

Icon	Description
	Refresh Reads the schema from the data source.  If the current input mapping is blank, it populates a default mapping using the same class and property names as the external data source schema, with all classes cleared.
	Delete all mappings Returns the mapping to its default state.
	Import all classes and attributes Selects every class and property. You can then clear the data that is not required.
	Clear all selected classes and attributes for import Clears every class and property. You must select at least one attribute from one class to use data from this data store.
	Add target class Create a class in the 1Integrate schema which is additional to the source map. The additional class might be used for temporary calculations or storage in rule and action processing. A new class is always created with a primary geometry column. The class may be written to the target data source, if the class already exists in the external source.
	Add target attribute Create an attribute, which is additional to the source map, on a target class. The attribute may be written to the target data source, if the attribute already exists in the external source.
	Map to Ontology Enable this to allow the Target Classes of the input mapping to be defined by an OWL ontology that you provide. This allows: The target model to be pre-defined to enable the easy re-use of existing rules. and/or The definition of virtual superclasses, which can simplify rule writing by targeting specific aggregations of source classes.
	Select ontology Reads an OWL ontology that defines the internal schema to be used within 1Integrate. This allows: The target model to be pre-defined to enable the easy re-use of existing rules. and/or The definition of virtual superclasses, which can simplify rule writing by targeting specific aggregations of source classes.

Primary Geometry

Note: Multiple geometry attributes per class are only supported for Oracle Datastores.

1Integrate 1Integrate supports multiple geometries for a class, but only one can be the primary geometry, as specified by the prm control.

When you import the data into 1Integrate, you define the primary geometry. The primary geometry is the column on which the spatial index is created in the cache, and is always named geometry.

If there are multiple geometry attributes then only one can be the primary geometry. This is marked as ‘Prm’ in the data store and is always referred to as ‘geometry’ when writing rules. The primary geometry is the indexed geometry for this class and is the one reported in non-conformance reports. Additional geometry attributes can also be loaded as secondary geometries, which are available to use in the rules but these are not indexed, and are not called ‘geometry’ but typically use the name of the column/attribute in the source data.

Index Flags

Each attribute has an index flag (denoted by a Index checkbox).

The Index flag determines whether or not the attribute is indexed by 1Integrate.

For optimum performance, index any attributes for which you want to define rules that will search for objects with a specific value for that attribute. It is recommended that you do not create an index for attributes that will not be queried within a rule or action.

By default, an index is created within 1Integrate if one already exists in the external data source.

Note: If an attribute is indexed, its value will be included in non-conformance reports even if the Reported flag is not selected.

Report Flags

Each attribute has a report flag (denoted by a Report checkbox).

The Report flag determines whether or not an attribute is reported in the rule conformance results XML and HTML reports (see Rule Conformance Results Report).