E00 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 is applicable only if you are working with foreign (non-English) character sets.

For example, if your source data contains foreign characters, using this parameter along with the encoding value ensures that the original data is preserved from the reader to the writer.

If the value is not set, the character encoding will be automatically detected from the source file. If the value is set, it will take precedence over the automatically detected character encoding.

FME supports most encodings.

Use this parameter to expose Format Attributes in 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 where you have multiple feature types, it is convenient to expose additional attributes using this one parameter. For example, if you have ten feature types and want to expose the same attribute in each one, it is easier to define it once than it is to set each feature type individually in the workspace.

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.

If all four coordinates of the search envelope are specified as 0, the search envelope will be disabled.

Select this parameter to remove any portions of imported features being read that are outside the Search Envelope.

The illustration below shows the results of the Search Envelope when Clip to Search Envelope is set to No on the left side and Yes on the right side.

• No: Any features that cross the search envelope boundary will be read, including the portion that lies outside of the boundary.
• Yes: Any features that cross the search envelope boundary will be clipped at the boundary, and only the portion that lies inside the boundary will be read. The underlying function for the Clip to Search Envelope function is an intersection; however, when Clip to Search Envelope is set to Yes, a clipping operation is also performed in addition to the intersection.

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.