Esri Geodatabase (File Geodb ArcObjects) Writer Parameters
Note: The values populated in the parameter box set the values for writer directives and for feature type parameters. Since some feature type parameters have equivalent writer-level directives, the parameter box value will be used in two places. The feature type parameters take precedence over writer directives. The only time the writer-level directives will be used is when there is no equivalent feature type parameter, or the parameter was not supplied.
General Parameters
If checked, deletes the existing database.
Indicates which transaction mechanism the Geodatabase writer should use. Within ArcGIS, there are currently two transaction mechanisms: edit sessions and (regular) transactions. An edit session corresponds to a long transaction. During an edit session, edits made by other users do not become visible until the edit session is ended. If a translation does not complete successfully and the Geodatabase writer is using an edit session, then all the edits will be discarded.
- Edit Session: Starts an edit session and then ends it when the translation is finished. This value should be used when edits are made to the tables that have custom behavior associated with them.
- Transactions: Starts the (regular) transaction mechanism. This can be used only when writing to non-versioned tables that do not have custom behavior.
- None: No transaction mechanism is used. This can be used only when writing to non-versioned tables that do not have custom behavior.
If specified, tells FME to import the complete schema from the template file into the database. Enter the pathname of the Esri XML workspace document to import. The import occurs after opening the Geodatabase for writing, but before any tables are created or features are written. Any error that occurs during import will cause the translation to fail.
Note that although the template file may contain both schema and data, FME only imports the schema.
Geometry Settings
ArcGIS geometry has to satisfy certain constraints to be considered valid. For example, polygons must have more than 2 vertices. This parameter allows you to specify whether geometry that breaks those constraints will be simplified to ensure only valid geometry is written.
Note that simplifying geometries can be resource-intensive.
For details on the conditions for invalid geometry and how it is simplified, please refer to ArcGIS documentation: Simplifying a Geometry and Calling the Simplify Method.
Determines whether or not the dataset contains z coordinates. Valid values are Yes, No, or Auto Detect. The default is Auto Detect.
Because Geodatabase does not allow mixed 2D and 3D features in the same feature class, it is best to choose a value of Yes for this parameter if you have mixed dimensions. The 2D features will be forced to 3D.
When set to Auto Detect, the writer determines the dimension of the feature class by checking the dimension of the first feature headed for that feature class.
Advanced
This parameter determines what version of Geodatabase should be created: 9.3, 10.0, or CURRENT (which is the default).