Esri File Geodatabase

The Esri File Geodatabase Data Store is available for reading and writing data in 1Integrate.

Read and Write Support

Read	Write		FME Desktop Required
Read	Commit	Copy To	FME Desktop Required

Data Support

Data	Support	Notes
Non-Spatial
2D
Measured
Heighted
3D		Note: Support for 3D is in BETA when using this Data Store. For more information about 3D data in 1Integrate, please refer to Full 3D Support.

Parameters

Read and Commit

Parameter	Description
Source Files Required: .gdb Zipped: .zip/.gz	Click the button and drag and drop the file anywhere or click to browse. Note: You can only upload one .gdb file to a Data Store, each table is represented as a separate Class. Warning: Ensure that the .gdb folder is at the root of the zip. If it isn't, the Geodatabase will not be read by 1Integrate.
Commit Destination Files (.gdb)	Results are available to download by clicking Download.
Coordinate Reference System	This parameter can be used to specify a Coordinate Reference System (CRS) code of the input data. 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). Note: Coordinate Reference System parameters are required in a session that will write data to Oracle. 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.
Enable full 3D geometries (BETA)	Select to enable full 3D geometries. Note: This parameter will only appear with an additional license enabling 3D support within 1Integrate. For more information on full 3D in 1Integrate, please see Full 3D Support.
Fix ring direction and inclusion errors	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.
For X, Y, Z, M data:	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.
For coded field domains	Coded Field Domains declare a map of key value pairs (similar to a look-up). Use the following options to configure how 1Integrate handles these coded field Domains: Read the stored values, do not resolve: This is the default behaviour for 1Integrate. Values are read ignoring the coded field domain mappings. Read the resolved values: Convert the data read using the coded domains as a guide. This means that the value for the attribute will be replaced with any values retrieved from the coded field domains. Read both the stored and resolved values: A combination of the two options above. Creates new attributes postfixed with "`_RESOLVED`" for each required coded field domain mapping. The original attributes will contain the value read, and the newly created attributes will contain the value retrieved from the coded field domain.
Convert attribute names to upper case	If selected, attribute names will be converted to upper case.
Dissolve holes	If selected, dissolves adjacent holes in polygons.
Retain attribute order	Enable to retain the order of the attributes from your source data. This can be useful if the order is important at a later stage when performing a Commit or Copy-To Task e.g. some data standards may mandate the order in which attributes should appear.

Copy To

Parameter	Description
Destination Files (.gdb)	Results are available to download by clicking Download.
Force geometry to be written with X, Y, Z, M	Select to output a fourth z or m ordinate for objects. Only takes effect if the geometry to be written has 3 ordinates.
For X, Y, Z, M data: Use zero rather than NULL or NaN when writing ignored ordinate	Select to write ignored values as zero in place of null/NaN (NaN is used for the PostGIS data store).

Parameter

Description

Destination Files (.gdb)

Results are available to download by clicking Download.

Force geometry to be written with X, Y, Z, M

Select to output a fourth z or m ordinate for objects.

Only takes effect if the geometry to be written has 3 ordinates.

For X, Y, Z, M data: Use zero rather than NULL or NaN when writing ignored ordinate

Select to write ignored values as zero in place of null/NaN (NaN is used for the PostGIS data store).