Metria AutoKa Transfer File (FF) Reader Parameters

When selected, causes self-intersecting polygons to be broken up into non-intersecting polygons.

Specifies whether lines used to build polygon geometries should also be read and presented as separate lines.

Specify the name of the file to be used as a parameter file. This parameter file is created by the FF reader and is used to store many metadata values for future use with other formats.

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 this is the bounding box intersection only, and not a full geometry intersection that would be returned by a transformer like the SpatialFilter.)

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

Clip to Search Envelope

When selected, this parameter removes any portions of imported features being read that are outside the Search Envelope.

The example below illustrates the results of the Search Envelope when Clip to Search Envelope is not selected (set to No) and when it is selected (set to Yes).

• 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 selected, a clipping operation is also performed in addition to the intersection.

Specifies whether texts attached to point geometries should be extracted to standalone texts with their own point geometry.

• Yes: Text-features are made for those points that have a list called ff_text_point{}.
• No: You can choose to create text later by using a ListExploder transformer with the ff_text_point list.

If set to No, clusters are not built. You can rebuild clusters later using the Aggregator and the ff_up_cluster attribute.

In TransferFiles (FF-files), clusters may have a mix of features with different geometry types, but by default such clusters are not built.

To build clusters with different geometries, specify Yes.

Note: This will generate objects that are not commonly supported by other formats, so if you set this option to Yes, you may have to split the clusters before sending them to the writer.

In FF, a 3D line or area (polygon) is not required to have heights on all vertices.

A vertex with unknown height will have a height value of NaN (Not a Number).

Very few formats allow vertices to have unknown heights, so this parameter allows you to replace all NaN height values with a default height value.

Note: This option does not turn 2D features into 3D features; only NaN values on 3D features are replaced.

The dep-attribute (dep = detail type) is stored on all FF features as a string of 10 characters. Any dep-value shorter than 10 characters will have spaces padded on the left side to make the string 10 characters long. As a standard behavior, FME does not try to trim any values read from an FF file.

If this parameter is set to Yes, FME will trim those spaces from the left side of the dep-value.