The MOEP writer processes the DATASET and DEF directives as described in the Reader Directives section.
It does not use the IDs directive.
The following table shows the supported global attributes for writing, and their default values, if available:
|
Attribute Name |
Description |
|
MOEP_FILENAME |
Name of physical file within MOEP dataset. Default: Feature type name with .bin appended |
|
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. Default: 32 |
|
MOEP_FILE_TYPE |
An integer in the range 0..9 denoting the type of data this file contains. Default: 0 |
|
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. Default: Feature type name |
|
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. Default: None |
|
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). Default: None |
|
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). Default: None |