| Database Connections |
|---|
|
Connections store authentication information. For general information about sharing database connections, please see Using Database Connections. Note: Depending on context and/or database format, you might see different combinations of Database Connection parameters.  Connection
Select an existing connection, or Add Database Connection to define a new connection. The new connection can be made visible only to the current user, or can be shared among multiple users. |
Database Connection
Connection File
This parameter identifies the pathname of a connection file to be used to connect to an Enterprise Geodatabase.
A connection file provides the necessary information to connect to the SDE server, such as the server name or the username.
The connection file must be a *.sde file and have the proper format for a connection file as defined by Esri. Connection files can be created in ArcCatalog.
Override Credentials
Check this option to override the User and Password from the connection file. Overriding credentials is required for Connection Files that do not have saved credentials.
Note: This parameter is ignored if the Connection File is using OS Authentication.
Username and Password
Enter the username and password to access the database, user account, or wherever authentication is required.
Constraints
Table List
After you have specified the database connection, click the Browse button to select tables for import. A connection window appears while the system compiles a table from the database.
Once the table list appears, you can select one or more tables, and then click OK to dismiss the window. The table name(s) will appear in the Table List field in the parameter box.
Feature Read Mode
When set to Features, the reader outputs features stored within tables.
When set to Metadata, provides the ability to read table-level metadata. In this mode, the reader outputs one feature per feature type. The geodb_type of the feature is geodb_metadata and the entire XML metadata document belonging to the Geodatabase table is found in the attribute geodb_metadata_string.
Where applicable, the following attributes are also supplied:
- fme_feature_identifier – indicates the name of the object ID field,
- fme_num_entries (Personal Geodb only) – indicates the number of features in the table,
- fme_contains_spatial_column – indicates whether the table has a geometry column (or, in Esri ArcGIS terms, whether the table is a feature class)
- fme_geometry{0} – indicates the types of geometry the feature class contains
- fme_dimension – indicates whether the feature class is 2D or 3D.
If the table is a feature class, the geometry of the metadata feature returned is a polygon, representing the extents of the feature class, and the coordinate system of the feature class also gets set on the feature.
When reading metadata, the Feature Type parameters are used to determine which feature types should have metadata read from them.
Mosaic Parameters
Mosaic Method
A Mosaic Dataset is a collection of rasters that can be combined to produce a single raster image for viewing or analysis. This parameter provides options to combine the rasters to produce the desired result. They do not apply to raster datasets. The options are based on the mosaic options provided for mosaic datasets in ArcGIS. See Esri documentation for a more detailed explanation.
The following values are supported:
- None – Rasters will be ordered in the order they appear in the mosaic dataset catalog table.
- By Attribute – Rasters will be ordered by how close the value of the attribute given by Order Field is to the value supplied in Order Base Value.
- Closest to Center – Rasters are ordered by how close they are to the center of the combined image.
- Lock Raster – Only those rasters given in Lock Raster ID will be combined in the order listed
- North-west (default) – Rasters are ordered by how close they are to the north-west of the combined image.
- Seamline – Rasters will be combined using the existing seamlines.
Order Field
When the value of Mosaic Method is set to By Attribute then this parameter specifies which field in the mosaic dataset’s attribute table will be used to compare values.
Order Base Value
When the value of Mosaic Method is set to By Attribute then rasters will be ordered by how close the value of the field given by Order Field is to the value given in this parameter.
Lock Raster ID
This parameter lists the ObjectIDs as a comma-separated list that will be used to give the order of the rasters when the value of Mosaic Method is set to Lock Raster.
Mosaic Order
Gives the option to reverse the order the rasters will be combined.
- Ascending – Those ordered first will be placed on top.
- Descending – Those ordered first will be placed on the bottom.
Mosaic Operator
It is possible for more than one raster to overlap in any given area. The mosaic operator specifies how the cells in the overlapping area are combined:
- First – The cell from the first raster is chosen.
- Last – The cell from the last raster is chosen.
- Min – The cell with the smallest value is chosen.
- Max – The cell with the largest value is chosen.
- Mean – The average of all the cells is chosen.
- Blend – Overlapping cells will blended together based on a weight-based algorithm that uses the distance of the cells to the edge within the overlapping area.
- Sum – The total value of all the pixels added together from overlapping raster datasets.
Schema Attributes
Additional Attributes to Expose
Use this parameter to expose Format Attributes in Workbench when you create a workspace:
- In a dynamic scenario, it means these attributes can be passed to the output dataset at runtime.
- In a non-dynamic scenario, you can use this parameter to expose additional attributes on multiple feature types.
Use Search Envelope
Using the minimum and maximum x and y parameters, define a bounding box that will be used to filter the input features. Only features that intersect with the bounding box are returned.
If all four coordinates of the search envelope are specified as 0, the search envelope will be disabled.
Clip to Search Envelope
When selected, this parameter removes any portions of imported features being read that are outside the Search Envelope.
The example below illustrates the results of the Search Envelope when Clip to Search Envelope is not selected (set to No) and when it is selected (set to Yes).
- No: Any features that cross the search envelope boundary will be read, including the portion that lies outside of the boundary.
- Yes: Any features that cross the search envelope boundary will be clipped at the boundary, and only the portion that lies inside the boundary will be read. The underlying function for the Clip to Search Envelope function is an intersection; however, when Clip to Search Envelope is selected, a clipping operation is also performed in addition to the intersection.
Advanced
Persistent Connection
Specifies whether to create a connection to SDE that persists and can be shared by other SDE readers, writers, and transformers.
When set to Yes, the connection will remain open until FME shuts down, even if this reader is finished using it. Otherwise, the connection will be closed when the reader is shut down (unless another reader, writer, or transformer is still using the connection).
Creating a new connection is a resource-expensive operation. Depending on how FME is being used (for example, if there are multiple instances of the reader/writer being used, or if the ArcSDEQuerier is being used to query/update the same SDE), performance may improve by setting this parameter to Yes.
Nodata Handling for Managed Rasters
Managed rasters, rasters stored within the Geodatabase, represent nodata as a bit mask on each band. This parameter specifies how to handle these nodata bit masks.
- None – Nodata bit masks will be ignored
- Single Alpha Band (default) – Nodata bit masks for each band are merged into a single additional alpha band named geodb_nodata.
If merged into a single alpha band, then the alpha band will contain a value of 0 (nodata) at a given cell if and only if the corresponding cell of all the other bands is nodata.
This parameter only affects managed rasters. Unmanaged rasters, rasters stored in files outside the Geodatabase, have nodata represented as a nodata value per band and do not have nodata bitmasks.