Esri Geodatabase (Personal Geodb) Writer Parameters

• If this option is unchecked (default) and a database already exists, then tables and features are written to the existing database.
• If this option is checked, any existing database is deleted before writing begins.

If no database exists when writing begins, a new database is created.

Note: After a database is deleted, it cannot be recovered – all data is lost.

If a template Personal Geodatabase is specified, the destination Personal Geodatabase is replaced with a copy of the template before writing begins.

Note: Since it is doing a complete copy, any data present in the template will also be copied to the destination. To remove unwanted data from tables or feature classes, set Truncate Table to Yes on each feature type. Alternatively, to copy only schema and not data, use ArcGIS to export the schema to an XML Workspace Document, then set the writer to import the resultant schema with the Import XML Workspace Document (Schema Only) parameter (below).

If specified, the writer will import the complete schema from the Esri XML workspace document specified into the destination Geodatabase. 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: The XML Workspace document may contain both schema and data; however, FME imports only the schema.

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 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. None differs from Transactions with a transaction interval of zero in that if the write fails, all successful features are committed for None, but are discarded for Transactions.

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.

The X-coordinate of the origin for all feature classes (individual origins can be set – see Geodatabase Table Representation in the FME Readers and Writers manual) and all feature datasets. This is used as an offset because coordinate data is stored as positive integers, relative to the origin, ranging from 0 to 2147483647 (so if the X origin is set below 0, then the maximum value will also drop, and vice versa). The value must be a real number. The default is 0.

Is the same as the X Origin except this it is for Y coordinate values.

This parameter is only used when creating new feature classes. It is not used by the File-based Geodatabase writer, as default values are used for the domain and resolution.

A scaling conversion factor from world units to integer system units for all feature classes and all feature datasets. This is used to specify the level of precision to keep when storing XY coordinates, since all coordinates are stored as integers.

The x,y scale is the inverse of the spatial reference's XY Resolution. The resolution is defined as the minimum unit in map units that separate unique x values and unique y values for feature coordinates.

Examples

• If the XY scale is defined to be 100, which corresponds to the XY resolution of .01 units, then an x value of 3.03 is considered different than 3.04, but the same as 3.033.
• If you have the coordinate (5.354, 566.35) and you set the XY scale to be 100, then the coordinate stored will be (5.35, 566.35).

For more information, see Esri's documentation on the properties of a Spatial Reference.

The default value is 100 when writing to an Enterprise Geodatabase and 0 when writing to a Personal Geodatabase.

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 select YES 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.

Is the same as the other origins, except it it is for Z coordinate values.

This is the same as X and Y Scale parameters, except it is for Z coordinates. The default value is 100 when writing to an Enterprise Geodatabase and 0 when writing to a Personal Geodatabase.

This parameter is only used when creating new feature classes. It is not used by the File-based Geodatabase writer as default values are used for the domain and resolution.

This sets the global grid 1 size for the whole translation. It may be overridden if the DEF line has the setting for GRID{1} parameter. For the Enterprise Geodatabase writer, the default is 1000 and for the Personal Geodatabase and File-based Geodatabase writers, the default is 0. This directive is only used when creating new feature classes.