Writer Feature Type Parameters

To access feature type parameters, click the gear icon on a feature type in the workspace. This opens the Feature Type Parameter Editor.

Tip  To always display the editor in FME Workbench, you can select View > Windows > Parameter Editor.

General

All feature types share similar General parameters, which may include Feature Type Name, Reader or Writer information, and Geometry.

In most Writer Feature Type parameter dialogs, you can also control Dynamic Schema Definitions. Some database formats accept Table or Index Qualifier prefixes on the output table feature type.

Important  These parameters apply only to a selected feature type, not to the entire writer. If a feature type parameter listed here conflicts with a writer-level parameter, then the writer parameter will be ignored and this feature type parameter will be used.

Table Settings: General

This parameter lets the user specify how features will be written into the destination table. Supported feature operations are:

  • Insert: Append rows onto the destination table using attributes on features.

Controls how the feature type handles destination tables:

  • Use Existing – Write to an existing table If the destination table does not exist, the translation will fail.
  • Create If Needed – Create the destination table if it does not exist.
  • Drop and Create – (This option is not available in all formats.) Drop the destination table if it exists, and then create it. The writer will drop and re-create the table before writing any features to it. Tables will be overwritten when the first input feature is processed. If no features are sent to a feature type, then the corresponding table will not be overwritten.
  • Truncate Existing – (This option is not available in all formats.) If the destination table does not exist, the translation will fail. Otherwise, delete all rows from the existing table.

Indicates which model should be used for storing geometry.

  • Relational: This is the default value, and the normal value when working with the relational model.
  • Enhanced Relational: This optional value places the writer into a mode that supports the additional features described in Enhanced Relational Operation.

Table Creation

Specifies the minimum geometric identifier that should be used.

Default: The greater of 0, or the largest GID present in the layer.

Specifies the number of ordinates that will be present in the <layerName>_SDOGEOM table.

Default: 64

Specifies whether the layer contains a third ordinate.

Default: No

Extents and Tolerances

Column Type for First/Second/Third Ordinate in SDOGEOM

Specifies the column type in the <layerName>_SDOGEOM table for the first/second/third ordinate.

First/Second/Third Ordinate Name

Specifies the name to use for the first/second/third ordinate. This name is used when the <layerName>_SDOGEOM table is created.

Minimum First/Second/Third Ordinate

The minimum value for the first/second/third ordinate expected in the dataset. If first/second/third ordinate values less than this value are supplied, the data is still written. However, querying the spatial index outside its extents will produce undefined results.

For best spatial search performance, this value should be as close to the true minimum as possible.

Maximum First/Second/Third Ordinate

The maximum value for the first/second/third ordinate expected in the dataset. If first/second/third ordinate values greater than this value are supplied, the data is still written. However, querying the spatial index outside its extents will produce undefined results.

For best spatial search performance, this value should be as close to the true maximum as possible.

Comparison Tolerance for First/Second/Third Ordinate

Specifies the comparison tolerance for the first/second/third ordinate. Ordinates that are closer than this value are considered equal.

Table Settings: Spatial

When FME opens up MYTABLE for writing, it performs a SQL query to determine the highest value of MY_ID in the table MYTABLE.

If this value is 34, the next row written by FME will place a value of 35 into MY_ID and then 36 for the next row, etc. (If the table contains no data, the first row for the oracle_gid_name column will be given a value of 1.)

Note  If a feature to be written to an Oracle Spatial Relational table contains an attribute with the same name as the GID column, the Oracle writer will assume that the attribute’s value should be used when writing the feature to the database. No check will be made to determine whether this value conflicts with any existing values in the table’s GID column.

Create Spatial Index

Indicates whether or not a spatial index is to be created as part of the data writing. Valid choices are Yes, No, or Incremental.

  • Yes or Incremental: Attribute indices on SDO_GID columns in the <layername> and <layerName>_SDOGEOM tables are created, and a compound index is created on the SDO_GID and SDO_CODE columns in that <layername>_SDOINDEX.
  • Yes: The <layername>_SDOINDEX table will be populated using the SDO_ADMIN.POPULATE_INDEX function.
  • Incremental: The <layername>_SDOINDEX table will be populated for only the features just loaded using the SDO_ADMIN.UPDATE_INDEX function.

Index Commit Interval

When Incremental index creation is used, a commit will be performed each time the number of features specified here have been indexed.

Tessellation Levels

Specifies the number of tessellation levels used to create the spatial index for the layer. The larger the number, the longer spatial index creation will take; however, the granularity of the index will be finer. The range is any integer between 1 and 64 for the quadtree algorithm. To use the R-Tree algorithm, set the value to 0.

For Oracle 11g+ users, it is highly recommended that you use the R-Tree algorithm.

Oracle 10g users should use the quadtree algorithm.