E00 (Esri ArcInfo Coverage/Esri ArcInfo Export) Reader Parameters

Switches E00 reader between "raw" and "normal" modes. Usually, the various bits and pieces of ArcInfo coverages (E00, binary, or PC binary) are combined to make wholly formed features, complete with attributes and resolved topology, but there are very rare special cases where it is useful to consider the pieces of the features as separate entities. This is mostly designed for performing ArcInfo-to-ArcInfo translations, where some simple manipulation of the feature's coordinates is being performed along the way.

Space the characters along the original curve, and generates a separate character for each (non-whitespace) character of the text. (This is the default.)

FME evenly spaces 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.

The start and end points of the text line are used to compute the average rotation of the characters, and the first point in the line becomes the text's position. This is FME's traditional behavior, drawing a straight line from the first point of the curve to the last point, and placing the text along that line.

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 Extract Bounds is checked, FME will create a single feature representing the coverage extent information.

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 Extract Tics is checked, FME will create a feature for each TIC point.

Traditionally the ArcInfo reader reads the NAT table and outputs the NODE attributes as a plain set of attributes. If this box is checked, 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.

This parameter controls which character encoding is used to interpret text attributes from the file. Using this parameter along with the encoding value ensures that the original data is preserved from the reader to the writer.

By default, the character encoding will be automatically detected from the system (fme-source-encoding).

If you select any other character encoding, it will take precedence over the automatically detected character encoding.

FME supports most encodings.

Use this parameter to expose Format Attributes in FME Workbench when you create a workspace:

• In a dynamic scenario, it means these attributes can be passed to the output dataset at runtime.
• In a non-dynamic scenario, this parameter allows you to expose additional attributes on multiple feature types. Click the browse button to view the available format attributes (which are different for each format) for the reader.

A search envelope (also known as a bounding box) is a rectangular area that defines a geographic area. In FME, the easiest way to define a search envelope is to use search envelope parameters.

Defining a search envelope is the most efficient method of selecting an area of interest because FME will read only the data that is necessary – it does not have to read an entire dataset. Search Envelope parameters apply to both vector and raster datasets and can be particularly efficient if the source format has a spatial index.

Most FME readers have parameters to define the search envelope of data that is being read:

The parameters include the x and y coordinates of the bounding box as well as a parameter that defines the coordinate system.

How to Define the Bounding Box

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 intersect with the bounding box are returned. Note that the bounding box intersection is not a full geometry intersection (based on spatial relationships) that would be returned by a transformer like the SpatialFilter.

Search Envelope Coordinate System

Specifies the coordinate system of the search envelope if it is different than the coordinate system of the data. The coordinate system associated with the data to be read must always be set if this parameter is set.

If this parameter is set, the minimum and maximum points of the search envelope are reprojected from the Search Envelope Coordinate System to the reader’s coordinate system prior to applying the envelope.

The underlying function for Use Search Envelope is an intersection; however, when Clip to Search Envelope is checked, a clipping operation is also performed.

• When checked (set to Yes), this option instructs FME to clip features to the exact envelope boundary. FME removes any portions of imported features being read that are outside the search envelope.
• When left unchecked (set to No), features that overlap the boundary will be included in their full (unclipped) form.

If the reader is placing the text characters along their curve (i.e., if Text Curve is not set to Fit or Follow), it usually inspects the text content to try detecting any multi-byte representations of “international” characters. If the reader finds a pair of bytes that seem to define a single character, it will use those 2 bytes in a single feature representing that character of text.

This behavior could lead to incorrect representation of some character strings, if they happen to be composed of single-byte characters that look like multi-byte characters. You can disable automatic detection of multi-byte characters by setting this parameter to Yes.