In addition to the reader directives that apply to all GeoMedia warehouses, these directives are specific to GeoMedia SQL Server Warehouses. For GeoMedia Access Warehouse-specific directives, see Reader Directives – GeoMedia Access Warehouse.
The directives listed below are prefixed by the current <ReaderKeyword> in a mapping file. By default, the <ReaderKeyword> for the SQL Warehouse Reader is FM0_SQL.
SQL_SERVER
Required/Optional: Required
Specifies the name of the server hosting the Microsoft SQL Server that stores the GeoMedia warehouse.
Range: String
Workbench Parameter: Server
USER_NAME
Required/Optional: Required
This is required only for GeoMedia SQL Server Warehouse. The username for the database must be supplied here, either through the command-line interface or the user interface settings for translation.
Workbench Parameter: User Name
WHERECLAUSE
Required/Optional: Optional
This optional keyword specifies a WHERE clause which is applied to the columns of a table to limit the resulting features.
The main difference between this WHERE clause and the one specified on DEF lines is that this WHERE clause will be applied to all the source feature tables, and the one specified on the DEF lines applies to one particular table. In the case when both the WHERE clauses are specified, then the DEF line WHERE clause takes precedence.
Workbench Parameter: Where Clause
HANDLE_MULTIPLE_SPATIAL_COLUMNS
If this directive is set to YES, feature geometry will be read into an aggregate. A directive is set on the aggregate to indicate that each part of the aggregate is independent from the others, and its own geometry.
Geometry parts of the aggregate are named and contain geometry according to their respective column in the table.
Note: When using this feature, the feature type SELECT statement may not be specified.
Required/Optional
Optional
Mapping File Syntax
<ReaderKeyword>_HANDLE_MULTIPLE_SPATIAL_COLUMNS YES
Workbench Parameter
Handle Multiple Spatial Columns
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 interact with the bounding box are returned.
If all four coordinates of the search envelope are specified as 0, the search envelope will be disabled.
Mapping File Syntax
<ReaderKeyword>_SEARCH_ENVELOPE <minX> <minY> <maxX> <maxY>
Note: If all four coordinates of the search envelope are specified as zero, the search envelope will be disabled.
Required/Optional
Optional
Workbench Parameter
Minimum X, Minimum Y, Maximum X, Maximum Y
SEARCH_ENVELOPE_COORDINATE_SYSTEM
This directive specifies the coordinate system of the search envelope if it is different than the coordinate system of the data.
The COORDINATE_SYSTEM directive, which specifies the coordinate system associated with the data to be read, must always be set if the SEARCH_ENVELOPE_COORDINATE_SYSTEM directive is set.
If this directive is set, the minimum and maximum points of the search envelope are reprojected from the SEARCH_ENVELOPE_COORDINATE_SYSTEM to the reader COORDINATE_SYSTEM prior to applying the envelope.
Required/Optional
Optional
Mapping File Syntax
<ReaderKeyword>_SEARCH_ENVELOPE_COORDINATE_SYSTEM <coordinate system>
Workbench Parameter
Search Envelope Coordinate System
CLIP_TO_ENVELOPE
This directive specifies whether or not FME should clip features to the envelope specified in the SEARCH_ENVELOPE directive.
Values
YES | NO (default)
Mapping File Syntax
<ReaderKeyword>_CLIP_TO_ENVELOPE [yes | no]
Workbench Parameter
Clip To Envelope
EXPOSED_ATTRS
This directive allows the selection of format attributes to be explicitly added to the reader feature type.
This is similar to exposing format attributes on a reader feature type once it has been generated; however, it is even more powerful because it enables schema-driven applications other than Workbench to access and leverage these attributes as if they were explicitly on the schema as user attributes.
The result of picking a list of attributes is a comma-separated list of attribute names and types that will be added to the schema features. Currently all reader feature types will receive the same set of additional schema attributes for a given instance of the reader.
Required/Optional
Optional
Mapping File Syntax
Not applicable.
While it is possible for FME Objects applications to invoke this directive, the required format is not documented.
This directive is intended for use in our GUI applications (for example, Workbench) only.
Workbench Parameter
Additional Attributes to Expose