> Is this the only way? MI is very weak in its reprojection cabablities.
On the contrary, MapInfo is quite strong in this area. You have to understand: MapInfo was designed so that a table's projection would be *transparent* to the ordinary user. Tables have intrinsic projections, so that MapInfo's on-the-fly projection engine can display layers in different projections together. This puts a responsibility on the person who develops the data: Identify the correct projection in the first place. "Reprojecting" a table in the sense that you specify means "going back and fixing the data developer's mistake in not specifying the table's projection correctly." Your best bet is to re-import the table from the original source and specify the correct projection then. If you bought this data from someone and it was already in MapInfo format, demand they fix the table and ship you a corrected version. As a fallback, follow the suggestions of other users: Export, fix, and re-import. If you export to MID/MIF, edit the MIF file in Notepad, inserting the correct Coordsys clause (for the UTM projection) That said, MapInfo doesn't behave correctly when saving a table from an Earth projection to a Nonearth projection, or vice-versa. This action should merely substitute one intrinsic projection for another (leaving internal coordinate values and bounds unaffected), or be IMPOSSIBLE. Hope this helps Spencer _______________________________________________________________________ List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, send e-mail to [EMAIL PROTECTED] and put "unsubscribe MapInfo-L" in the message body.
