The Geodatabase reader begins by opening the Geodatabase dataset that resides within a server/file system. Once opened, the Geodatabase reader queries the Geodatabase and passes the resulting features – that is, rows – to FME for processing. Every feature that is read is tagged with its original integer object ID (this is the object ID that Geodatabase assigns to it) under the attribute name geodb_oid.
The Geodatabase reader has several different reader types to account for file- and enterprise-based datasets, as well as for vector and raster:
|
Geodatabase Reader |
Reader Type (Format Short Name) |
|---|---|
|
Enterprise Geodatabases |
– GEODATABASE_SDE – GEODATABASE_SDE_RASTER_DATASET – GEODATABASE_SDE_RASTER_CATALOG |
|
File-based Geodatabases (a folder ending in .gdb) |
– GEODATABASE_SDE – GEODATABASE_SDE_RASTER_DATASET – GEODATABASE_SDE_RASTER_CATALOG |
|
Mobile Geodatabase (a file ending in .geodatabase) |
– ESRI_MOBILE_GEODATABASE |
When reading features from the Geodatabase, the tables from which features are retrieved are specified in the workspace using the Tables parameter.
The Geodatabase reader locates the tables from which data is to be retrieved. If no tables or feature types are selected and the Enterprise Geodatabase reader is used, then no features are read from the database. However, if no tables or feature types are specified and the File-based Geodatabase reader is used, then all features are read from the database.
The table below summarizes the different feature retrieval modes supported by the Geodatabase reader module. The word table refers to both non-spatial tables and feature classes. However, feature class applies only to feature classes and not tables.
|
Search Type |
FME Workbench Reader Parameter |
Description |
|---|---|---|
|
Non-Spatial and Spatial Retrieval |
Tables |
Specifies the tables from which features are to be retrieved. If there are no specified tables and the File-based Geodatabase reader is being used, then all features are retrieved. If there are no specified tables and the Enterprise Geodatabase reader is being used then no features are retrieved. |
|
WHERE Clause |
Specifies the attribute constraint that a feature must have to be retrieved. The WHERE clause follows the SQL syntax of the underlying database, except that ORDER BY, GROUP BY, nested queries, and aggregate functions (that is, MAX, COUNT) cannot be used. |
|
|
Spatial Retrieval |
Use Search Envelope |
Specifies the spatial extent of the feature retrieval. Note Only features that have the relationship specified by Search Method with the envelope are returned. This cannot be specified at the same time as a Search Feature is specified.
|
|
Search Feature |
Specifies a feature with an arbitrary number of coordinates as the search feature. Note Only features that have the relationship specified by Search Method with the envelope are returned. This cannot be specified at the same time as a Search Feature is specified.
When specifying the Search Feature, make sure it has a simple geometry. If it does not have a simple geometry, then its geometry is always simplified by the Geodatabase reader. |