Esri Geodatabase (File Geodb Open API) User Attributes
Readers: For information on the parameters in this dialog that are common to all readers, see:
Writers: For information on the parameters in this dialog that are common to all writers, see:
User attributes for this format are defined below.
For example: If reading a dataset that has attributes named for the years 2023 and 2024, the writer schema will list these attributes as _2023 and _2024.
Using an AttributeRenamer transformer to rename the attribute or add a specific prefix will prevent the underscore from being added, as long as the new name does not also begin with a number.
|
Name |
The name of the field to be written. |
|
Type |
This format supports the following field types. This type is used to represent 16-bit signed integers. This type is used to represent 32-bit signed integers. This type is used to represent 32-bit float values. This type is used to represent 64-bit values. This type is used to store and retrieve date information within the Geodatabase. When a date field is read by the Geodatabase, it is placed in the FME feature with the form HHMMSS, YYYYMMDD, or YYYYMMDDHHMMSS. The time portion is specified using the 24-hour clock. When writing, the date attribute must also be in one of these three forms. These forms are compatible with all other FME dates. This type is used to represent object IDs. There is (at most) one per row. This field type is read only; values will be automatically assigned on write. This type is used to represent global IDs. There is one per row. This field type is read only. This type is used to represent GUIDs. This type is used to represent arbitrary length binary data. This type is used to represent XML data. This type is used to represent character values with a length not exceeding n characters. FME will read from and write to geodatabases using the UTF-16 (on Windows platforms) or UTF-32 (on Linux platforms) encodings. |
|
Index |
There is only one supported index type: Indexed. The specified indexes are created along with tables or feature classes; they are never added to existing tables or feature classes. |
Geometry Definition
In formats that support reading or controlling the writing of geometric (spatial) data, a Geometry Definition table is visible in the User Attributes tab of a feature type.
For more information, see:
- Geometry Definition describes placement in the User Attributes dialog, and defines the possible column names.
- The FME Support Center article Introducing Geometry (Spatial) Definition Tables describes the purpose of Geometry Definition tables and gives instructions on how to use them.