Input Connection

Drag and drop your file into the window, or click within the upload box and navigate to the file on your network.

A .zip archive can be uploaded if more than one file is required.

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.

DWG/DXF data includes a number of standard attributes that are the same for all data. FME classifies these as format attributes and does not expose them by default, so they must be explicitly specified here as a comma separated list in order to import them.

To browse the list of possible attributes in FME Desktop, open an Autodesk AutoCAD DXF/DWG reader, look at the parameters, expand the Schema Attributes section, and next to Additional Attributes to Expose click on the ... button.

Note: Text entities in a DWG file get loaded as points. In order to access the text string, you need to add "autocad_text_string" to the list of format attributes to expose.

Drag and drop your file into the window, or click within the upload box and navigate to the file on your network.

A .zip archive can be uploaded if more than one file is required.

Polygon rings are assumed to be encoded using the right-hand rule, i.e. outer rings are anti-clockwise and inner rings are clockwise.

If the service does not guarantee that encoding, then set this flag to have polygon rings automatically oriented on import to avoid later problems when processing the data.

Note: This requires a small amount of additional processing so only set if the ring direction is not guaranteed.

Override the global origin of X, measured in UORs, from the lower left corner of the design plane/cube.

Override the global origin of Z, measured in UORs, from the lower left corner of the design plane/cube.

The number of UORs per sub unit. Must be an unsigned integer ratio.

Used only if Units of Resolution (UOR) scale is not populated.

Controls whether or not curve elements will be stroked into lines by adding vertices.

If selected, the control points of the curve are connected into a line. This option preserves the original control points and the end slopes. This is primarily used for DGN-to-DGN translations.

If deselected, The control points are used to interpolate a linear representation of the curve. It strokes (vectorizes) the curve (that is, it preserves the shape of the curve).

The number of points per segment when the curve is interpolated into a line.

Used only if Preserve Curves is not selected.

If selected, the multi-text is split into text nodes, and the member text elements are output as individual text elements.

If the multi-text had any linkage attributes, these will be propagated to the component elements.

These linkage values can be used to join the graphical data held in the design file to the MSLINK field in the related database table. The entity number that is extracted is used to determine the relevant table that holds the attributes (the database contains a table called MSCATALOG which maps entity numbers to table names).

Note: Only the first three linkage values will be extracted.

Drag and drop your file into the window, or click within the upload box and navigate to the file on your network.

A .zip archive can be uploaded if more than one file is required.

If the field names (or column names) are specified in the file, this option ensures that the names will be extracted from the file.

Otherwise, the columns of the DSV table are given default names (col0, col1, ... , colN).

Enter the number of header lines to skip when reading the datastore.

Note: This can be used if any header lines include information you do not want included as a column name.

The URL location of the Esri feature service.

Note: If you use a map service you will encounter a session error.

Note: If you are attempting to connect to a secured ArcGIS server and it has not been secured by a certificate provided by a trusted certificate authority you need to configure Java to trust it. Please refer to relevant WebLogic or Java (for WildFly installations) documentation.

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.

Enter the location of the zip file containing the .gdb folder, or click Upload to navigate to the file on your network.

Note: Ensure that the .gdb folder is at the root of the zip. If it isn't, the Geodatabase will not be read by 1Integrate.

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.

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.

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.

Drag and drop your file into the window, or click within the upload box and navigate to the file on your network.

A .zip archive can be uploaded if more than one file is required.

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.

Controls how measure data associated with geometric data or attributes on the incoming features is handled.

If selected, measure data is created from the z values on the incoming features, if the z values exist. If measure data exists, it is not overwritten by the z values on the feature.

If unselected, measures will be preserved on the features.

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.

If you have data that is recorded as X,Y,Z,M, you must opt to ignore either Z or M values by choosing to use X, Y and M or X, Y and Z only.

Note: If the default is left on and X,Y,Z,M is uploaded then an exception will be thrown as 1Integrate only supports X,Y,M or X,Y,Z.

A .json file containing your credentials, generated from Google BigQuery.

The dataset name, taken from BigQuery.

Drag and drop your file into the window, or click within the upload box and navigate to the file on your network.

A .zip archive can be uploaded if more than one file is required.

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.

Polygon rings are assumed to be encoded using the right-hand rule, i.e. outer rings are anti-clockwise and inner rings are clockwise.

If the service does not guarantee that encoding, then set this flag to have polygon rings automatically oriented on import to avoid later problems when processing the data.

Note: This requires a small amount of additional processing so only set if the ring direction is not guaranteed.

Controls which character encoding is used to interpret text attributes.

If blank, the character encoding will be automatically detected.

This parameter is only applicable when opening datasets of Type FME. If the auxillary FME dataset is a database reader, then MapInfo willl not automatically put the password for the source database in the tab file. This parameter allows the user to specify the password dynamically.

If the password is hardcoded into the tab file, then this parameter will supercede that password.

If you have data that is recorded as X,Y,Z,M, you must opt to ignore either Z or M values by choosing to use X, Y and M or X, Y and Z only.

Note: If the default is left on and X,Y,Z,M is uploaded then an exception will be thrown as 1Integrate only supports X,Y,M or X,Y,Z.

Polygon rings are assumed to be encoded using the right-hand rule, i.e. outer rings are anti-clockwise and inner rings are clockwise.

If the service does not guarantee that encoding, then set this flag to have polygon rings automatically oriented on import to avoid later problems when processing the data.

Note: This requires a small amount of additional processing so only set if the ring direction is not guaranteed.

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.

If selected, geography will be used as the spatial type.

If unselected, the default of geometry will be used instead.

If you have data that is recorded as X,Y,Z,M, you must opt to ignore either Z or M values by choosing to use X, Y and M or X, Y and Z only.

Note: If the default is left on and X,Y,Z,M is uploaded then an exception will be thrown as 1Integrate only supports X,Y,M or X,Y,Z.

When consuming data with 3 ordinates, you must also select one of the two options:

• Select X,Y,Z to read in heighted data.

• Select X,Y,M to read in measured data.

Schema containing the required data.

The identifier with which Oracle or JBoss identifies this database.

The port number of the host.

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.

If you have data that is recorded as X,Y,Z,M, you must opt to ignore either Z or M values by choosing to use X, Y and M or X, Y and Z only.

Note: If the default is left on and X,Y,Z,M is uploaded then an exception will be thrown as 1Integrate only supports X,Y,M or X,Y,Z.

Polygon rings are assumed to be encoded using the right-hand rule, i.e. outer rings are anti-clockwise and inner rings are clockwise.

If the service does not guarantee that encoding, then set this flag to have polygon rings automatically oriented on import to avoid later problems when processing the data.

Note: This requires a small amount of additional processing so only set if the ring direction is not guaranteed.

The URL location of the OAuth token.

Note: OAuth can only be used in conjunction with the OS Data Hub.