The suffixes listed are prefixed by the current <ReaderKeyword> in a mapping file. By default, the <ReaderKeyword> for the E00 reader is E00 or ARCINFO.
DATASET
Required/Optional: Required
The E00 reader processes the directive <ReaderKeyword>_DATASET, where <ReaderKeyword> is the keyword assigned to the E00 reader. By default, the reader keyword is E00 for E00 files, or ARCINFO when working with binary ArcInfo coverages.
The <ReaderKeyword>_DATASET directive specifies the data set to be read by the E00 reader. When reading E00 files, this is the name of the E00 file, including the .e00 suffix. If the E00 reader encounters the end of the E00 file <filename>.e00 while it is expecting more data to process, it will attempt to use the file <filename>.e01 as a continuation of the input. No specific mention of <filename>.e01 is required.
When reading binary ArcInfo coverages directly, the value of <Readerkeyword>_DATASET is the path of the folder containing the files that make up the coverage.
Note: It is not the folder containing the individual coverage folders, but rather one of the coverage folders itself.
No additional configuration is required to tell the reader to process a binary coverage instead of an E00 file. If the supplied argument is a folder, the reader will assume the data set is a binary coverage.
When reading binary ArcInfo tables directly, the value of <Readerkeyword>_DATASET is the path to the “info” folder which contains info tables.
Workbench Parameter
Source Esri ArcInfo Export (E00) File(s)
TEXT_CURVE
Required/Optional
Optional
There is an additional directive that tells the E00 reader how to deal with text elements which follow a splined curve in ArcInfo. In the past, the FME has simply drawn a straight line from the first point of the curve to the last point, and placed the text along that line. The default behavior now is to space the characters along the original curve, and generate a separate character for each (non-whitespace) character of the text. The directive <ReaderKeyword>_TEXT_CURVE allows one to change the FME’s interpretation of curved text features. The default value for the directive is FOLLOW; a value of IGNORE will revert the FME to its traditional behavior; and a value of FIT will tell FME to evenly space out the characters of the text along the curve, so that the left edge of the first character is on the first point of the curve, and the right edge of the last character is on the last point.
Value: FIT | FOLLOW | IGNORE
Default Value: FOLLOW
Workbench Parameter
Text Curves
SINGLE_BYTE_TEXT
Required/Optional: Optional
If the E00 reader is placing the text characters along their curve (i.e., if the <ReaderKeyword>_TEXT_CURVE was not given a value of FIT or FOLLOW), it normally inspects the text content to try to detect whether any are multi-byte representations of “international” characters. If it finds a pair of bytes that it thinks define a single character, it will use those two bytes in a single feature representing that character of text. This behavior might lead to incorrect representation of some character strings, if they happen to be composed of single-byte characters that look like multi-byte characters. This automatic detection of multi-byte characters may be disabled by providing the SINGLE_BYTE_TEXT directive a value of YES.
Value: YES | NO
Default Value: NO
Workbench Parameter: Force Single-Byte Text
INCLUDE_BND
Required/Optional
Optional
ArcInfo coverages typically include an info file named BND, which defines the extents of the coverage. FME will normally ignore the contents of this file. If the <ReaderKeyword>_INCLUDE_BND keyword is specified with a value of YES, FME will create a single feature representing the coverage extent information.
The extent is defined on the resulting feature with the attributes XMIN, YMIN, XMAX, and YMAX. In FME, the feature will have a polygon geometry corresponding to these attributes’ values; in FME Objects, the BND feature will have no geometry.
Value: YES | NO
Default Value: NO
Example:
E00_INCLUDE_BND Yes
INCLUDE_TIC
Required/Optional
Optional
ArcInfo coverages typically include an info file named TIC, which defines the tic points for the coverage. FME will normally ignore the contents of this file. If the <ReaderKeyword>_INCLUDE_TIC is specified with a value of YES, FME will create a feature for each TIC point.
The features resulting from reading the TIC file will have the IDTIC, XTIC, and YTIC attributes as defined in the TIC file, and will have a point geometry corresponding to (XTIC,YTIC).
Value: YES | NO
Default Value: NO
Example:
E00_INCLUDE_TIC Yes
HYPHENS_ARE_VALID
Required/Optional: Optional
When set to “Yes” the reader will not convert hyphens in attribute names to underscores. The one exception to this rule is that if the attribute name ends in “-ID” – in this case, it will be converted to _ID no matter what the directive is set to.
So, for example, if the attribute name is “HYPH-ENS-ID”, then when the directive is set to “Yes”, it will be read as “HYPH-ENS_ID” and if the directive is set to “No”, it will be read as “HYPH_ENS_ID”.
If this directive is missing, then it will have an implied value of “No”. This is to ensure backwards compatibility, so workspaces created with a previous version of FME (one that does not yet support this directive) continue to work as they always have.
Value: YES | NO
Default Value: Yes
Example:
E00_HYPHENS_ARE_VALID Yes
GENERATE_NODE_FEATURES
Required/Optional: Optional
Traditionally the ArcInfo reader reads the NAT table and outputs the NODE attributes as a plain set of attributes. If the value is YES, the endpoints of the ARC features are turned into NODE features, which are then joined with the NAT table attributes to provide fully formed point features.
Value: YES | NO
Default Value: NO
Example:
E00_GENERATE_NODE_FEATURES NO
Workbench Parameter: Not applicable (parameter box setting only)
There are no other directives processed by the E00 reader, meaning there are no DEF lines for reading E00 features. The features obtained from the specified data set take the form described in the remainder of this chapter.
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