The directives processed by the SDF reader are listed below. The suffixes shown are prefixed by the current <ReaderKeyword> in a mapping file. By default, the <ReaderKeyword> for the SDF reader is SDF.
DATASET
Required/Optional: Required
The value for this keyword is the folder containing the SDF files to be read, or a single SDF file. A typical mapping file fragment specifying an input SDF dataset looks like:
SDF_DATASET /usr/data/sdf/92i080
IDs
Required/Optional
Optional
This specification is used to limit the available and defined SDF files read. The syntax of the IDs keyword is:
<ReaderKeyword>_IDs <baseName1> \
<baseName2> \
<baseNameN>
The basenames must match those used in DEF lines.
The example below selects only the roads SDF file for input during a translation:
SDF_IDs roads
SPATIAL_EXTENT
Required/Optional
Optional
This specifies a bounding box where all features retrieved by the read function must in some part be within the bounding box area. This keyword is formatted as follows:
<ReaderKeyword>_SPATIAL_EXTENT <minX> <minY> <maxX> <maxY>
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
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