| Long name | MapInfo Data Interchange Format |
| Short name | MIF |
| File extension(s) | .mid, .mif |
MapInfo layers in the form of .mif/.mid files are supported by the GDB library for both read and write with RST support, with some limitations listed below.
All graphical object types are imported with all their attributes, however, ARCs and ELLIPSEs are emulated with line segments 3 degrees long (up to 120 segments in one complete ellipse). Rounded Rectangles are also treated as simple rectangles. PLINEs and REGIONs are converted to one single GDB Shape with a RingStart attribute specifying the index where the sub-regions start in the array of vertices of the shape.
Projections are remapped to best match while reading and writing. However, it is possible that some specific projections have no equivalent. In such cases, the projection will be set to "METER" on import (with the coordinates converted to meters as well) or to "COORDSYS NonEarth" on export. On export, if the datum or ellipsoid of the projection cannot be converted, a warning is displayed and a METER projection is assumed.
In write mode, vertices and all attribute types (except CountedInts) are written out. A RST can also be provided as long as it is in Ground Units, and GDB will export the representation information. When you import a file, the best results will be obtained with RSTs that have been generated by this same translator.
Export of MapInfo files is supported. These files are exported with a type of "MIF".
The translator will give better results if an RST (in Ground Units) with the following attributes is available. Note that these are optional and that the export operation will work but without representation information (colors, line widths, etc) if they are not provided:
© PCI Geomatics Enterprises, Inc.®, 2024. All rights reserved.