Difference between revisions of "MapInfo Tips"
Line 11: | Line 11: | ||
TUFLOW utilises the MapInfo Interchange Format files for MapInfo GIS inputs. The MapInfo interchange format consists of a pair of files with the extensions .MIF and .MID. Both of these files are text files (and can be viewed in a text editor). Whilst knowledge of the file formats is not necessary for TUFLOW modelling, advanced users can take advantage of the nature of the file formats to manipulate these datasets.<br> | TUFLOW utilises the MapInfo Interchange Format files for MapInfo GIS inputs. The MapInfo interchange format consists of a pair of files with the extensions .MIF and .MID. Both of these files are text files (and can be viewed in a text editor). Whilst knowledge of the file formats is not necessary for TUFLOW modelling, advanced users can take advantage of the nature of the file formats to manipulate these datasets.<br> | ||
− | A full | + | A brief description is given below, for the full specification of the MIF/MID file formats please see [http://www.gissky.com/Download/Download/DataFormat/Mapinfo_Mif.pdf here.] |
<u>'''MIF File'''</u><br> | <u>'''MIF File'''</u><br> | ||
− | The | + | The .MIF file contains information on the projection, data attributes and types as well as the geographic information contained in the table. An example .MIF file is given below. Lines 1 to 3 are header information, line 4 defines the projection of the table. Line 5 specifies the number of associated data attributes. A separate line follows for each attribute column (in this case 1), this defines the type and length of this field (in this case we have an attribute named "Comment" which is a character field of length 250. The 7th line ("Data") signals the start of the GIS data. |
+ | |||
+ | Following this are any number of "Point", "Line", "Polyline" and "Region" objects (there are other types of objects such as "Ellipses") but these four are the most common. In the example below the only object is a Polyline ("PLine") with two vertices, the coordinates of these are listed on lines 10 and 11. An object style is associated with each object "Pen (1,2,0)". | ||
+ | |||
+ | <pre> | ||
+ | Version 600 | ||
+ | Charset "WindowsLatin1" | ||
+ | Delimiter "," | ||
+ | CoordSys Earth Projection 8, 116, "m", 147, 0, 0.9996, 500000, 10000000 Bounds (-7745844.29605, 2035.05684549) (8745844.29605, 19997964.9432) | ||
+ | Columns 1 | ||
+ | Comment Char(250) | ||
+ | Data | ||
+ | |||
+ | Pline 2 | ||
+ | 333788.63 5815865.7 | ||
+ | 338831.12 5815865.7 | ||
+ | Pen (1,2,0) | ||
+ | </pre> | ||
=Basics= | =Basics= |
Revision as of 15:15, 22 August 2011
Introduction
This page contains a
MapInfo File Formats
There are a number of files that make up a MapInfo Table. The minimum files for a GIS map object with data are:
- .DAT
- .ID
- .MAP
- .TAB
There are a number of additional files types that may be present, these include: .IND, .TDA, .TIN and .TMA.
TUFLOW utilises the MapInfo Interchange Format files for MapInfo GIS inputs. The MapInfo interchange format consists of a pair of files with the extensions .MIF and .MID. Both of these files are text files (and can be viewed in a text editor). Whilst knowledge of the file formats is not necessary for TUFLOW modelling, advanced users can take advantage of the nature of the file formats to manipulate these datasets.
A brief description is given below, for the full specification of the MIF/MID file formats please see here.
MIF File
The .MIF file contains information on the projection, data attributes and types as well as the geographic information contained in the table. An example .MIF file is given below. Lines 1 to 3 are header information, line 4 defines the projection of the table. Line 5 specifies the number of associated data attributes. A separate line follows for each attribute column (in this case 1), this defines the type and length of this field (in this case we have an attribute named "Comment" which is a character field of length 250. The 7th line ("Data") signals the start of the GIS data.
Following this are any number of "Point", "Line", "Polyline" and "Region" objects (there are other types of objects such as "Ellipses") but these four are the most common. In the example below the only object is a Polyline ("PLine") with two vertices, the coordinates of these are listed on lines 10 and 11. An object style is associated with each object "Pen (1,2,0)".
Version 600 Charset "WindowsLatin1" Delimiter "," CoordSys Earth Projection 8, 116, "m", 147, 0, 0.9996, 500000, 10000000 Bounds (-7745844.29605, 2035.05684549) (8745844.29605, 19997964.9432) Columns 1 Comment Char(250) Data Pline 2 333788.63 5815865.7 338831.12 5815865.7 Pen (1,2,0)
Basics
In this section are some basic MapInfo functions that are regularly used in creating TUFLOW models in MapInfo.