Writer Directives

The directives processed by the IDEX Writer are listed below. The suffixes shown are prefixed by the current <WriterKeyword> in a mapping file. By default, the <WriterKeyword> for the IDEX writer is IDEX.

DATASET

Required/Optional: Required

The value of this directive is the IDEX file to be written. A typical mapping file fragment specifying an input IDEX file looks like:

IDEX_DATASET c:\idex\map.idx

Workbench Parameter: Destination Leica IDEX File

DEF

Required/Optional

Required

The syntax of an IDEX DEF line is:

<ReaderKeyword>_DEF <featureType> \
	idex_type idex_point|idex_line|idex_polygon \
			[<attrName> <attrType>]+

The <featureType> is used as the idex_database_code_id if this attribute is used but not correlated to. The <attrName> is an attribute, whereas <attrType> is the type of the attribute. Currently supported attribute types are listed in the following table.

Attribute Type	Description
char	Fixed-length character string attribute.
float	Real number attribute.
integer	Integer value attribute.

Example:

IDEX_DEF CANADA \
    idex_type   idex_point \
    Province  char \
	Population  integer \
	GenderRatio  float

DATANAMES

Required/Optional

Required

The syntax of an IDEX DATANAMES line is:

<ReaderKeyword>_DATANAMES <idex_type> \
	[<dataName> (YES|NO)]+

The data name specified in this section determines which data names are formatted in the IDEX output. The tables shown in the following sections identify the data names that the FME supports for each <idex_type>. Notice that the word after idex in the DATANAMES is the IDEX section to which the attribute belongs. For example:

IDEX_DATANAMES idex_point \
    idex_database_east YES \
    idex_database_north YES \
	idex_database_code_id YES 

Points

idex_type: idex_point

The following data names are supported for points.

Data Name	Description	Value
idex_database_user_id	Specifies the user-defined ID number for this point.	YES|NO
idex_database_job_number	Specifies the user-defined job number for this point.	YES|NO
idex_database_coord_system	This is the IDEX coordinate system for the point.	YES|NO
idex_database_coord_class	This is the IDEX coordinate class for the point.	YES|NO
idex_database_east	This is the X-coordinate of the point.	YES|NO
idex_database_north	This is the Y-coordinate of the point.	YES|NO
idex_database_elevation	This is the Z-coordinate of the point.	YES|NO
idex_database_longitude	This is the longitude of the point.	YES|NO
idex_database_latitude	This is the latitude of the point.	YES|NO
idex_database_code_id	Specifies what type of object this point is.	YES|NO
idex_database_description	Specifies the point object’s description.	YES|NO
idex_database_color	Specifies the colour of the point.	YES|NO
idex_database_layer_number	This is the layer number of this point.	YES|NO
idex_database_symbol1_number	This is the first symbol associated with this point.	YES|NO
idex_database_symbol2_number	This is the second symbol associated with this point.	YES|NO
idex_database_symbol_ direction	This is the symbol rotation for this point.	YES|NO
idex_database_flag	This is the database flag to be set for the point.	YES|NO
idex_codes_name	This is the description of the code in the codes section.	YES|NO
idex_codes_layer_number	This is the layer number in the CODES section.	YES|NO
idex_theme_attrib_code	This is the code in the ATTRIBUTES section.	YES|NO

Lines

idex_type: idex_line

The following data names are supported for lines.

Data Name	Description	Value
idex_database_user_id	Specifies the user-defined ID number for this line.	YES|NO
idex_database_job_number	Specifies the user-defined job number for this line.	YES|NO
idex_database_code_id	Specifies what type of object this line is.	YES|NO
idex_database_description	Specifies the line object’s description.	YES|NO
idex_database_color	Specifies the color of the line.	YES|NO
idex_database_layer_number	This is the layer number of this point.	YES|NO
idex_database_line_style	Specifies the style of this line.	YES|NO
idex_database_flag1	This is the first database flag to be set for the line.	YES|NO
idex_database_flag2	This is the second database flag to be set for the line.	YES|NO
idex_codes_name	This is the description of the code in the CODES section.	YES|NO
idex_codes_layer_number	This is the layer number in the CODES section.	YES|NO
idex_theme_attrib_code	This is the code in the ATTRIBUTES section.	YES|NO

Polygons

idex_type: idex_polygon

The following data names are supported for polygons.

Data Name	Description	Value
idex_database_user_id	Specifies the user-defined ID number for this polygon.	YES|NO
idex_database_job_number	Specifies the user-defined job number for this polygon.	YES|NO
idex_database_code_id	Specifies what type of object this line is.	YES|NO
idex_database_ description	Specifies the line object’s description.	YES|NO
idex_database_color	Specifies the color of the line.	YES|NO
idex_database_layer_ number	This is the layer number of this point.	YES|NO
idex_database_line_style	Specifies the style of this line.	YES|NO
idex_database_symbol_ number	This is the symbol associated with the polygon.	YES|NO
idex_database_symbol_direction	This is the rotation the symbol associated with this polygon	YES|NO
idex_database_flag	This is the database flag to be set for the polygon.	YES|NO
idex_database_hatch_color	Specifies the color of the hatches.	YES|NO
idex_database_fill_type	This is the fill type to be set for the polygon.	YES|NO
idex_codes_name	This is the description of the code in the CODES section.	YES|NO
idex_codes_layer_number	This is the layer number in the CODES section.	YES|NO
idex_theme_attrib_code	This is the code in the ATTRIBUTES section.	YES|NO

POINT_ID_FRONT

Required/Optional: Optional

Points are created by the writer as it writes lines and polygons. Since these points have no user-defined ID, the writer will generate them. To avoid name collisions, the point_id_front allows you to set the prefix to the internal point number which is stored as the user ID.