Precisely MapInfo TAB (MAPINFO/MITAB) Writer Parameters

Provides a hint of the target version of the output file.

This affects compatibility options for date fields. Specifically, versions 300 and 450 will treat date/time fields as strings instead.

Note that this option does not affect the overall version number written to the file. That is determined by the specific attribute types, geometry types, or coordinate systems. For example, if the coordinate system is “Krovak S-JTSK”, then the version is promoted to at least 900.

Values Supported: 300, 450, 900, 950, 1000, 1050, 1100, 1150

Tells the MapInfo writer to create an optimal spatial index when writing. This will allow for faster spatial queries on the resulting file when using MapInfo Pro or other software that takes advantage of built-in spatial indexing. The use of this directive will, however, slow down the writing of the file.

To direct the writer to calculate the region centroid and store the x and y values in the corresponding mif_centroid_x and mif_centroid_y format attributes. The writer only attempts to calculate the centroid values if the format attributes were not previously set. If neither the format attributes nor this directive are set, a default centroid value is still calculated by underlying libraries.

Indicates whether to write a linear feature with two vertices as a polyline (two or more vertices).

Indicates whether the arcs are vectorized before writing. If Yes, all arcs are converted to polylines. This option may be useful where sweep angles have precision finer than 0.1 degree.

This parameter is applicable if you are working with extended (not basic ASCII) character sets. If your source data contains non-ASCII characters, using this parameter along with the encoding value ensures that the original data is preserved from the reader to the writer.

The character encoding will be automatically detected from the source file (fme-source-encoding). If you select any other character encoding, it will take precedence over the automatically detected character encoding.

FME supports most encodings.

The coordinate system statement that should be used in the output files. Usually, FME examines the coordinate system information present on the features written to the files, and outputs the coordinate system based on this information. However, in certain circumstances it is necessary to override this and force a particular coordinate system to be output. This is typically done to force the units of a non-Earth projection to something other than the default, which is meters.

Allows explicit setting of the bounds of the output features. Because MIF has limited precision for storing coordinates, defining a tight bound on the range of the data can preserve more accuracy.