Reader Directives

The suffixes listed are prefixed by the current <ReaderKeyword> in a mapping file. Unless otherwise specified, the <ReaderKeyword> for the ArcGIS Layer reader is the same as the <ReaderType>.

DATASET

A single Esri layer/feature class from which data is to be read. The value for an Esri layer is simply the layer file. The value for a feature class is the Esri path to the file/database containing the feature class plus the name of the feature class. The Esri path is displayed in the Location toolbar within Esri ArcCatalog.

The FME dataset selector has been enhanced for the ArcGIS Layer reader to use Esri’s layer/feature class picker. Using this selector will greatly simplify the process of selecting a dataset.

Required/Optional: Required

Esri Layer Example:

ARCGIS_LAYER_DATASET “C:\data\runways.lyr”

Feature Class within a Personal Geodatabase Example:

ARCGIS_LAYER_DATASET “C:\data\airport.mdb\runways”

Feature Class within an Enterprise Geodatabase Example:

ARCGIS_LAYER_DATASET “Database Connections\esri92.sde\JOE.runways”

FME Feature Class within a MIF/MID file Example (requires ArcGIS to be extended by FME):

ARCGIS_LAYER_DATASET “C:\data\mif\usa.mif\usa Line”

Workspace Parameter: Esri ArcGIS Layer

DEF

Describes feature classes. Normally these lines are automatically generated within a mapping file/workspace using FME.

Required/Optional: Optional

Example:

ARCGIS_LAYER_DEF Parcels                  \
    geodb_type           geodb_polygon     \
    OBJECTID_1           integer                \
    PROPERTY_I           double                 \
    LANDUSE_CO           char(3)              \
    ZONING               char(6)                   \
    PARCEL_ID            integer                  \
    Res                  smallint                      \
    ZONING_S             char(4)                 \
    Shape_Length         double                 \
    Shape_Area           double                

 

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