MapInfo File Formats - Revision history

Emilie Nielsen at 01:44, 8 January 2026

2026-01-08T01:44:25Z

← Older revision		Revision as of 11:44, 8 January 2026
Line 47:		Line 47:
	15,945,"V",115.341		15,945,"V",115.341
	</pre>		</pre>


			{{Tips Navigation
			\|uplink=[[MapInfo_Tips\| Back to MapInfo Tips]]
			}}

Emilie Nielsen at 01:58, 5 April 2024

2024-04-05T01:58:38Z

← Older revision		Revision as of 11:58, 5 April 2024
Line 8:		Line 8:

	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 brief description is given below, for the full specification of the MIF/MID file formats please see [http://read.pudn.com/downloads23/doc/fileformat/74584/mapinfoformat.pdf here.]<br>
	<u>'''MIF File'''</u><br>		<u>'''MIF File'''</u><br>
	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.		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.

Steph.dufour at 05:28, 28 November 2014

2014-11-28T05:28:11Z

← Older revision		Revision as of 15:28, 28 November 2014
Line 8:		Line 8:

	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 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.]<br>		A brief description is given below, for the full specification of the MIF/MID file formats please see [http://read.pudn.com/downloads23/doc/fileformat/74584/mapinfoformat.pdf here.]<br>
	<u>'''MIF File'''</u><br>		<u>'''MIF File'''</u><br>
	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.		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.

tuflow>Par: Protected "MapInfo File Formats": High traffic page ([edit=sysop] (indefinite) [move=sysop] (indefinite))

2011-10-06T21:49:13Z

Protected "MapInfo File Formats": High traffic page ([edit=sysop] (indefinite) [move=sysop] (indefinite))

← Older revision		Revision as of 07:49, 7 October 2011
(No difference)

tuflow>Par: Created page with '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 ty...'

2011-08-22T05:24:26Z

Created page with '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 ty...'

New page

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 [http://www.gissky.com/Download/Download/DataFormat/Mapinfo_Mif.pdf 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)".
 
'''Example .MIF file:''' 
<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>

'''MID File''' 
The .MID file contains the attribute data associated with the GIS objects. These are stored in a comma separated variable (csv) format with no columns titles (as this is stored in the .MIF file). 
In the example above, the .MID file contains only one line (as there was only one object in the .MIF file). The data attributed with this is a "Comment" with a length of up to 250 characters. The .MID file below is associated with the .MIF file example above. 
'''Example .MID file:''' 
<pre>
"This line defines the X-axis of the TUFLOW model"
</pre>

A more complex .MID file is presented below, this is from a 2d_zpt layer, where the fields are "N", "M" "Type" and elevation. This example contains five GIS objects. 

<pre>
15,943,"H",115.491
15,944,"H",115.379
15,944,"V",115.412
15,945,"H",115.357
15,945,"V",115.341
</pre>

MapInfo File Formats - Revision history

Emilie Nielsen at 01:44, 8 January 2026

Emilie Nielsen at 01:58, 5 April 2024

Steph.dufour at 05:28, 28 November 2014

tuflow>Par: Protected "MapInfo File Formats": High traffic page ([edit=sysop] (indefinite) [move=sysop] (indefinite))

tuflow>Par: Created page with '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 ty...'

tuflow>Par: Created page with '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 ty...'