Input Connection

The Input Details tab of the Data Stores page is used to configure a connection to an external data store, from which you want to import data into 1Integrate.

Once the Input Details have been entered, Schema Mapping must be performed (see Input Mapping).

Note: The Data Engineer role is required in order to configure Input Details (see Roles).

Enter Input Connection Details

  1. Navigate to the Data Stores page.

  2. From the Navigation Pane, select the data store to be configured.

  3. Open the Input Details tab.

  4. Select the required Data Store Type from the drop-down menu.

    Note: Different parameters will appear depending on which Data Store Type is selected.

  5. Enter the details for your selected Data Store Type.
  6. Click Save.
  7. Click Test Connection to verify the data can be accessed.

Input Details Parameters

When setting up an Input Connection, the Data Store Type you select will determine which parameters appear.

The following tables detail the parameters required for each available Data Store Type.

ClosedAutodesk AutoCAD DWG/DXF

ClosedBentley MicroStation Design (V8)

ClosedComma Separated Value (CSV)

ClosedEsri Enterprise Geodatabase

Note: In order to use the Esri Enterprise Geodatabase datastore format, ArcMap (64-bit) and FME Desktop Esri Edition must be installed and a licence for each available on the machine(s) running 1Integrate (and all session queues). For full details, see the FME knowledge centre.

Parameter Description
Source Database

The name of the database.

Coordinate Reference System

Coordinate Reference System parameters are required in a session that will write data to Oracle.

This parameter can be used to specify a Coordinate Reference System (CRS) code of the input data, if it cannot be deduced automatically.

This will not re-project the data, but allows its current CRS to be defined (e.g to enable multiple data stores to open where one does not have a CRS defined).

See Coordinate Reference System for more information on when this is required.

Import FME Log File Download the FME log file created during import (to help identify any errors).
Allow invalid geometries

Allows features with invalid geometries (e.g. duplicate vertices, self-intersections) to be imported.

This is necessary if they need to be imported in order to be validated or corrected. If not ticked then features with invalid geometries are not imported and are logged as feature errors in the open data task.

Fix ring direction and inclusion errors

Selecting this option will, where possible, correct polygons that do not correctly identify which rings form the outer boundary and which are holes or that have rings that do not conform to the OGC standard for clockwise/anti-clockwise direction.

Reverse Coordinate axis order (y, x) Reverse the x and y co-ordinate values. Select this if the coordinates are in (y,x) order and are not being read or written in the correct order.
Connection File Select a connection file (.sde) to be used to connect to the Esri Enterprise Geodatabase.
Dataset The name of the dataset from which features will be retrieved.
Server The name of the Geodatabase server used to read data from the dataset.
Instance Name

The name of the Enterprise Geodatabase instance.

Note: The typical value for systems with a single ArcSDE instance is esri_sde8.

User ID User ID of the Enterprise Geodatabase user.
Password Password for the User ID.
Retrieve All Schemas

Must be checked to allow import schema refresh.

Remove Table Qualifier

Specifies whether to keep or remove the table name prefix.

For example, if set, "ROAD_NETWORK.NONCONFORMANCE" will become "NONCONFORMANCE".

Clip to envelope

If selected, causes features that overlap the bounding box (defined in the Search Envelope parameter) to be clipped and the outer part discarded.

Note: This should only be used when a session is loading a subset of the data by defining an extent as a bounding box or polygon. If set, it causes features that overlap the extent to be clipped and the outer part discarded. If not selected then the whole geometry of features that intersect the extent will be loaded including the parts of their geometry that are outside the extent.

Version If you're using a versioned dataset and you want to connect to a specific version, then you need to enter the version name and specify VERSIONING as the Transaction Type. If using a non-versioned database or if connecting to the DEFAULT version, then leave this blank.
Transaction Type

Specify the type of transaction to use when accessing and updating the data. The types are VERSIONING, EDIT_SESSION, TRANSACTIONS or NONE. If not specified then the default is TRANSACTIONS.

For further information about transaction types refer to FME documentation.

If using a non-versioned database, leave this blank.

ClosedEsri File Geodatabase

ClosedEsri Shape

ClosedMapInfo Tab

ClosedMicrosoft SQL Server Spatial

ClosedOracle

ClosedPostGIS

Standard

Parameter Description
Source Database The name of the PostGIS-enabled PostgreSQL database. The database must exist in the RDBMS.
Coordinate Reference System

Coordinate Reference System parameters are required in a session that will write data to Oracle.

This parameter can be used to specify a Coordinate Reference System (CRS) code of the input data, if it cannot be deduced automatically.

This will not re-project the data, but allows its current CRS to be defined (e.g to enable multiple data stores to open where one does not have a CRS defined).

See Coordinate Reference System for more information on when this is required.

Allow invalid geometries

Allows features with invalid geometries (e.g. duplicate vertices, self-intersections) to be imported.

This is necessary if they need to be imported in order to be validated or corrected. If not ticked then features with invalid geometries are not imported and are logged as feature errors in the open data task.

Import host name The host name for the PostGIS database.
Import port number The port name for the PostGIS database.
Import username The username for the PostGIS database.
Import password The password for the PostGIS database

FME Only

Parameter Description
Source Database The name of the PostGIS-enabled PostgreSQL database. The database must exist in the RDBMS.
Coordinate Reference System

Coordinate Reference System parameters are required in a session that will write data to Oracle.

This parameter can be used to specify a Coordinate Reference System (CRS) code of the input data, if it cannot be deduced automatically.

This will not re-project the data, but allows its current CRS to be defined (e.g to enable multiple data stores to open where one does not have a CRS defined).

See Coordinate Reference System for more information on when this is required.

Import FME Log File Download the FME log file created during import (to help identify any errors).
Allow invalid geometries

Allows features with invalid geometries (e.g. duplicate vertices, self-intersections) to be imported.

This is necessary if they need to be imported in order to be validated or corrected. If not ticked then features with invalid geometries are not imported and are logged as feature errors in the open data task.

Fix ring direction and inclusion errors

Selecting this option will, where possible, correct polygons that do not correctly identify which rings form the outer boundary and which are holes or that have rings that do not conform to the OGC standard for clockwise/anti-clockwise direction.

Reverse coordinate axis order (y, x) Reverse the x and y co-ordinate values. Select this if the coordinates are in (y,x) order and are not being read or written in the correct order.
Command timeout The timeout, in seconds, after which to terminate a query to the database if it has not yet returned a result. If set to zero, there is no timeout.
Retrieve all schemas

Must be checked to allow import schema refresh.

Import host name The host name for the PostGIS database.
Import port number The port number for the PostGIS database.
Import username The username for the PostGIS database.
Import password The password for the PostGIS database.
WHERE clause Define a WHERE clause to limit the rows read by the reader from each table (e.g. LENGTH > 2000 would select only the features where the length is greater than 2000).
Clip to envelope

If selected, causes features that overlap the bounding box to be clipped and the outer part discarded.

Note: This should only be used when a session is loading a subset of the data by defining an extent as a bounding box or polygon. If set, it causes features that overlap the extent to be clipped and the outer part discarded. If not selected then the whole geometry of features that intersect the extent will be loaded including the parts of their geometry that are outside the extent.

Read cache size Used to determine the number of rows that are retrieved at once from the data source (10 by default).
Assume one SRID per column If selected, assume that a single SRID (Spatial Reference ID) is used within a given column (as is common practice).
Exposed attributes

Allows the selection of format attributes to be explicitly added to the reader feature type.

Enter a comma-separated list of attribute names and types that will be added to the schema features.