The suffixes listed are prefixed by the current <ReaderKeyword> in a mapping file. By default, the <ReaderKeyword> for the IDRISI reader is IDRISI.
DATASET
Required/Optional: Required
The value for this directive is the folder containing the IDRISI files to be read, or a single IDRISI file. A typical mapping file fragment specifying an input IDRISI dataset looks like:
IDRISI_DATASET /usr/data/idrisi/input
Workbench Parameter: Source IDRISI Vector Format File(s)
DEF
Required/Optional
Required
Each IDRISI file must be defined before it can be read. The definition specifies the base name of the file, and the names and the types of all attributes. The syntax of an IDRISI DEF line is:
<ReaderKeyword>_DEF <baseName> \
[<attrName> <attrType>]+
The following table shows the attribute types supported.
|
Field Type |
Description |
|
char(<width>) |
Character fields store fixed-length strings. The width parameter controls the maximum number of characters that can be stored by the field. No padding is required for strings shorter than this width. For the IDRISI database, the width is limited to a maximum of 255. |
|
date |
Date fields store date as character strings with the format YYYYMMDD. |
|
double |
Float fields store 64-bit floating point values. There is no ability to specify the precision and width of the field. |
|
integer |
Integer fields store 32-bit signed integers. |
|
logical |
Logical fields store TRUE/FALSE data. Data read or written from and to such fields must always have a value of either true or false. |
IDs
Required/Optional
Optional
This optional specification limits the available and defined IDRISI files read. If no IDs are specified, then all defined and available IDRISI files are read.
The syntax of the IDs directive is:
<ReaderKeyword>_IDs <baseName> \
<baseName1> … \
<baseNameN>
The basenames must match those used in DEF lines.
The example below selects only the roads IDRISI file for input during a translation:
IDRISI_IDs roads
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