grass to MapInfo and vice-versa

Xin Zhuang zhuang at
Tue Jan 24 09:35:52 EST 1995

	From grass-lists-owner at Tue Jan 24 04:25:31 1995
	Received: from by with SMTP id AA23008
	  (5.67b8/IDA-1.5 for <zhuang at>); Tue, 24 Jan 1995 04:25:29 -0500
	Received: (from daemon at localhost) by (8.6.9/8.6.9) id CAA11021 for grassu-people; Tue, 24 Jan 1995 02:30:27 -0600
	Received: from ( []) by (8.6.9/8.6.9) with ESMTP id CAA11018 for <grassu-list at>; Tue, 24 Jan 1995 02:30:25 -0600
	Received: from (motte at []) by (8.6.9/8.6.9) with SMTP id CAA19073 for <grassu-list at>; Tue, 24 Jan 1995 02:29:39 -0600
	Received: by id AA17390
	  (5.67b/IDA-1.5 for grassu-list at; Tue, 24 Jan 1995 09:29:46 +0100
	From: motte <motte at>
	Message-Id: <199501240829.AA17390 at>
	Subject: Re: grass to MapInfo and vice-versa
	Sender: grass-lists-owner at
	Reply-To: grassu-list at
	Precedence: Bulk
	To: grassu-list at
	Date: Tue, 24 Jan 1995 09:29:46 +0100 (MET)
	In-Reply-To: <950123124126_100074.213_EHK55-1 at CompuServe.COM> from "National Centre" at Jan 23, 95 07:41:27 am
	X-Mailer: ELM [version 2.4 PL21]
	Content-Type: text
	Content-Length: 884       
	Status: R

	> Hello,
	> 	Has anybody had any experience of exchanging vecter data between MapInfo
	> and Grass - is there a good way of retaining attribute data?
	> Cheers, Al.

	Afaik there is no code around that does the trick. I spent a few hours 
	trying to make a conversion program, but it's not that easy given 
	MapInfo's vector data structure (any volunteers?). The best way so far is 
	to use DXF layers, but this means you'll have to export each attribute in
	a separate layer. 

	Philip Verhagen

	P.S. Next time you put a message on the list, it might be a good idea to 
	add your full name, affiliation and e-mail adress...


				S t i c h t i n g  R A A P

			Regionaal Archeologisch Archiverings Projekt

	adress: 	Plantage Muidergracht 14
		        1018 TV Amsterdam
	phone:          (31) 20 525 5835
	fax:		(31) 20 525 5834
	e-mail:		motte at

I wrote but won't get back to you until
late this week. Please email me directly.

v.out.mapinfo can be done. However, MapInfo makes its projection
line not that easy to be accesses. There's a projection file
come with MapInfo. However, you probably notice that
they're different when included in MIF (MapInfo Interchange Format)
files. I guess it needs to sit down for a while and study them
before writing v.out.mapinfo. The easiest way is probably 
to create a lookup table for all UTM in the US.


More information about the grass-user mailing list