List of Supported Formats

Search the Online Transformer Gallery

Reader Directives

The suffixes shown below are prefixed by the current <ReaderKeyword> in a mapping file. By default, the <ReaderKeyword> for the MOEP reader is MOEP.

DATASET

Required/Optional: Required

The value for this directive is the folder name of the input MEOP files, or a single MOEP file to be read. A typical mapping file fragment specifying an input MOEP dataset looks like:

MOEP_DATASET /usr/data/moep/92i080

or

MOEP_DATASET /usr/data/moep/92i080/92i080a.bin

Workbench Parameter: Source B.C. MOEP File(s)

DEF

Required/Optional

Optional

The definition specifies the ID to use to refer to the file, along with the physical file name and its extension. In addition to the file name, other global attributes from the table below can be specified in the definition. When additional attributes are specified for an MOEP file being read, the reader will generate warnings if the specified values do not match those specified in the file’s header. The writer uses the global attributes to fill in the header of the MOEP file being written.

The syntax of an MOEP DEF line is:

<ReaderKeyword>_DEF <fileID> \
	MOEP_FILENAME <physFileName> \
	[<attrName> <attrVal>]*

The following table shows the supported global attributes:

Attribute Name

Description

MOEP_FILENAME

Name of physical file within MOEP data set.

MOEP_RESOLUTION

The size of integer used to represent each X and Y coordinate value within the MOEP file. This can be either 16 or 32, indicating 16-bit or 32-bit integers, respectively.

Z coordinates are always 16 bits, regardless of this attribute’s value.

MOEP_FILE_TYPE

An integer in the range 0..9 denoting the type of data this file contains.

MOEP_NAME

An ASCII string 0 to 11 characters in length, providing a logical name for the file. This is stored in the file’s header; it typically contains a mapsheet ID.

MOEP_FORCE_TYPE5

This optional attribute must be set to either yes or no. The default is no. If it is yes, a type 5 attribute record is written with each feature, even if it is empty.

MOEP_DATE

The date of submission of the MOEP file. The format for this date is YYMMDD, where YY is the last two digits of the year, MM is the month (01-12), and DD is the day within the month (01-31).

MOEP_OFFSET_MINIMUM

The MOEP writer module uses this value to determine the origin from which 16-bit (X,Y) coordinates are measured. As features are written to the MOEP file, their minimum bounding rectangle is maintained; once the MBR is larger than MOEP_OFFSET_MINIMUM in both the X and Y directions, its centre point is chosen as the origin for all coordinates written to the file. This attribute has no effect on 32-bit coordinates, which are always measured from (0,0).

The following mapping file fragment defines two MOEP files, one containing DEM data with 16-bit coordinates, and one containing contours, with 32-bit coordinates:

MOEP_DEF dem_data MOEP_FILENAME 92b053d.arc \
	MOEP_FILE_TYPE 1 \
	MOEP_RESOLUTION 16 \
	MOEP_NAME 92b053d \
	MOEP_DATE 960913\
	MOEP_OFFSET_MINIMUM 1000
MOEP_DEF contour_data MOEP_FILENAME 92b053t \
	MOEP_FILE_TYPE 2 \
	MOEP_RESOLUTION 32 \
	MOEP_NAME 92b053t \
	MOEP_DATE 960913

IDs

Required/Optional

Optional

This optional specification is used to limit the available and defined MOEP files read. If no IDs are specified, then all defined and available MOEP files are read. The syntax of the IDs keyword is:

<ReaderKeyword>_IDs	<fileID1> \
	<fileID1> …  \
	<fileIDn>

The fileIDs must match those used in DEF lines.

The example below selects only the dem_data MOEP file for input during a translation:

MOEP_IDs dem_data

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