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)
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.