(This functionality is available with the Input / Output module)
Allows the export of objects (points, lines, polygons and text) to MapInfo. For each of these object types, there are 2 files created for each Code/Group: the MapInfo Interchange Format (*.MIF) and the MapInfo Interchange Data (*.MID). Note that arcs and splines are exported as MapInfo polylines.
To obtain this option, select the "Export/MapInfo MIF/MID" command from the Data Conversions task to display the relevant dialog box.
Export MapInfo MIF/MID dialog box
| Item | Used to |
| Save in: | Select the folder in which the files are to be created. |
| Export By: | Select the method to be used for exporting. This option controls the naming of the files. Points, lines, polygons and text objects will be added to the files based on either their code or group. |
| Attribute Mapping: | Select the attribute mapping file (.mlu) that defines the point, line, polygon and text attributes to be exported. A default .mlu file (Mapinfo.mlu) is distributed with the system and located in the LISCAD user folder language sub folder. You may add others to suit particular export needs. They may be edited in a text editor such as Notepad to remove unwanted attributes or to change the name of the attributes created in the export (as defined on the right hand side of the equals signs). |
| Maximum Segment Distances | Splines are exported as MapInfo polylines. Hence the Maximum Segment Distance is entered to control the distance between points generated in the polylines. |
| Arc/Chord Offset | Arcs are exported as MapInfo polylines. Hence this value is entered to control how closely the polylines approximate arcs. |
| Projection Category: | Select the projection category. The available categories are populated from the Mapinfo.prj file which resides in the LISCAD User Folder. |
| Projection Member: | Select the projection member. The available members depend on the category selected and are also populated from the Mapinfo.prj file which resides in the LISCAD User Folder. |
| Lookup | Select the lookup files to be used for matching: - LISCAD line styles to MapInfo line styles; - LISCAD symbols to MapInfo symbols. Refer to the Lookup File Settings dialog box. |
| Save | Create the MIF and MID files. These files will be created in the specified
output folder and have
names aaa(bbb).xxx, where aaa is the Code or Group name (depending upon the "Export By" selection), bbb is the LISCAD entity,
either point, line, polygon or text and xxx is either MIF or MID. If the file name to be created already exists in the destination folder a dialog will appear asking if you want to overwrite the existing files. |
| Cancel | Close the dialog box without creating the files. |
Notes:
Display and Block sensitive:
Only objects which are currently displayed will be exported. Refer to the Display/Groups and Display/Features command.
If there is a block currently active, then only those objects which are defined by that block will be exported.
Attribute Mapping:
The MIF file has two areas – the file header and the data.
The MIF header describes how to create a MapInfo table of the data, listing the columns of that table.
It also contains a COORDSYS clause. This specifies what form the coordinates of the data are in. The data in the COORDSYS clause is mapped to what the chosen projection is, via the Mapinfo.prj file.
The column names are also output in the header of the MIF file. What column names get output, for a particular LISCAD entity is defined in the Attribute Mapping file selected. A column name should not contain a space. An example MLU file would be:
# LISCAD Standard Attribute Mapping file for MapInfo MIF/MID
[Point]
Identifier = ID
Code = CODE
Group = GROUP
Description = DESCRIP
SymbolName = SYMB_NAME
SymbolDim1 = SYM_DIM_1
SymbolDim2 = SYM_DIM_2
SymbolDirn = SYM_DIRN
Elev = ELEV
[Line]
Number = NUMBER
LineType = TYPE
Code = CODE
Group = GROUP
Description = DESCRIP
LineColourNumber = COLOUR_NUM
LineStyleName = STYLE_NUM
Length = LENGTH
[Polygon]
Number = NUMBER
Code = CODE
Group = GROUP
Description = DESCRIP
FillColourNumber = FILLCOL_NUM
LineType = L_TYPE
LineColourNumber = L_COL_NUM
LineStyleNum = L_STYLE_NUM
Area = AREA
Perimeter = PERIMETER
[Text]
Code = CODE
Group = GROUP
Hence, a Point type MIF file would contain the headings, based upon the preceding file…
ID,CODE,GROUP,DESCRIP,SYMB_NAME,SYM_DIM_1,SYM_DIM_2,SYM_DIRN,ELEV
The MIF data section contains the entity data.
The data section of the MIF file can have any number of graphical primitives, one for each graphic object.
MapInfo matches up entries in the MIF and MID files, associating the first object in the MIF file with the first row in the MID file,
the second object in the MIF with the second row in the MID, etc.
LISCAD Point objects will be output as a MIF point object.
LISCAD Line objects will be output as a:
• MIF line object if it is a two point line
• MIF polyline object if it is a multi point line or a spline, using the maximum segment distances defined in the dialog where appropriate
• MIF arc object if it is an arc
• MIF ellipse object if it is a circle
LISCAD Spirals, Offsets and Radiations will not be output.
LISCAD Polygon objects will be output as a MIF region object.
LISCAD Text objects will be output as a MIF text object.
Each MIF object can have a visual Style attached to it.
For linear objects, a PEN style can be associated, which corresponds closely to a LISCAD line style.
The Line Style Lookup File specified via the Dialog is used to map the LISCAD line style to a MapInfo Pen pattern.
For point objects, a SYMBOL style can be associated, which corresponds closely to a LISCAD symbol.
The Symbol Lookup File specified via the Dialog is used to map the LISCAD symbol to a MapInfo Style Shape.
The MID file contains the data, one record per row, as defined by the columns defined in the corresponding MIF file.
The data is delimited with a ',' character.
File Naming:
Example: file name conventions are as follows when 'Code' has been selected from the 'Export By' list:
Points
Code(point).mif
Code(point).mid
Lines
Code(line).mif
Code(line).mid
Polygons
Code(poly).mif
Code(poly).mid
Text
Code(poly).mif
Code(poly).mid