FME can store data in and retrieve data from Esri’s File Geodatabase, based on the File Geodatabase API.
No additional software is required to use this format, but less functionality is available than with some other Esri Geodatabase formats.
The Esri Geodatabase (File Geodb Open API) reader/writer provides Geodatabase support without an installed Esri product on Windows and Linux; however, it is a limited set of geometry and works only with 10.0 File Geodatabases or higher. For example, annotation is unsupported.
For more information, see:
- Notes on FME and Esri Versions and Compatibility
- Comparison of FME Readers/Writers for SDE and Geodatabase
The Geodatabase reader and writer translates several different types of features:
- reading and writing of point, line, polygon, and multipoint feature classes
- partial reading of some of the other File Geodatabase types (e.g., dimensions, parcel fabrics) exposed using the basic geometric types listed above
- reading and writing of non-spatial tables
- Programmatic Table Creation: Feature classes and tables need not be created before a data import operation. All table creation details are handled by FME.
- When FME creates a feature class, it consults the first feature destined for the corresponding feature type to determine if Z and/or measure values should be included.
- Index Creation: Attribute fields can be flagged as indexed. When the associated feature class or table is created, attribute indices are created as well.
- Table Selection: A subset of tables and feature classes to read can be selected from a list. Feature classes within a feature dataset are listed together for easy selection.
- Attribute Query Support: SQL “where” clauses can be specified to limit the data being exported.
- Spatial Query Support: A bounding box can be specified to limit the data being exported. This can be configured in the reader settings or accessed via the FeatureReader transformer.
- Fully Automatic Import and Export: FME supports fully automated import and export of data through its graphical interfaces, e.g. FME Quick Translator. This is ideal for quick data imports and exports.
- Unicode Support: Geodatabase text columns are stored in the UTF-16 encoding on Windows platforms, and in UTF-32 encoding on Linux platforms. FME can read and write this data.
- Feature Datasets: Feature datasets are read and written. On read, they are included in FME’s feature type names. On write, they are created as necessary.
- Domains and Subtypes: Coded domain and subtype fields are read and written using descriptions, not coded values. For example, if a coded value Res has a description Residential, when writing to a field that contains a domain, ensure that you pass in the description. In the current release, FME does not support creating tables or feature classes with subtypes or domain restrictions, and does not include this metadata on the schema.
- Coordinate Systems: Features are tagged with their spatial reference (coordinate system) on read. Feature classes are created with the spatial reference associated with incoming features. Note that the File Geodatabase API supports a fixed list of coordinate systems. Data in other coordinate systems cannot be read or written.
- Measures: In addition to reading and writing X, Y, and optional Z ordinates, measure values are supported as well. The writer will write measures if the feature contains the <default_measure> and the destination feature class includes measure values. The reader will automatically load the <default_measure> if there are measures on the source feature class.
The reader extracts data from the selected File Geodatabase using the File Geodatabase API.
ArcGIS feature classes and tables become FME feature types, and ArcGIS features and rows become FME features. For feature classes within a feature dataset, the FME feature type name is formed as follows:
<feature dataset name>/<feature class name>.
As with other database readers in FME, the Format Parameters are used to determine which feature classes and tables to read. WHERE clauses and bounding box constraints can be used to further limit the data read.
The writer exports data to a new or existing File Geodatabase using the File Geodatabase API.
Note that, because they are considered to have complex behavior, the Geodatabase API writer does not support writing to tables that participate in a relationship.
Other tables/feature classes that are not supported:
- Annotation and Dimension feature classes
- Relationship Classes
- Networks (GN and ND)
- Parcel Fabrics