From rhoskins@home.com Wed Apr 21 19:30:56 1999
Received: from mxu4.u.washington.edu (mxu4.u.washington.edu [140.142.33.8])
	by lists.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA38544
	for <waphgis@lists.u.washington.edu>; Wed, 21 Apr 1999 19:30:56 -0700
Received: from ha1.rdc1.wa.home.com (siteadm@ha1.rdc1.wa.home.com [24.0.2.66])
	by mxu4.u.washington.edu (8.9.3+UW99.02/8.9.3+UW99.01) with ESMTP id TAA08669
	for <WAPHGIS@u.washington.edu>; Wed, 21 Apr 1999 19:30:55 -0700
Received: from c501552a ([24.5.121.123]) by ha1.rdc1.wa.home.com
          (Netscape Mail Server v2.02) with SMTP id AAA2491
          for <WAPHGIS@u.washington.edu>; Wed, 21 Apr 1999 19:29:21 -0700
Message-ID: <02de01be8c67$e2cda280$7b790518@olmpi1.wa.home.com>
From: "Richard E. Hoskins" <rhoskins@home.com>
To: <WAPHGIS@u.washington.edu>
Subject: WAPHGIS: comversion from e00to Mapinfo
Date: Wed, 21 Apr 1999 19:28:59 -0700
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_02DB_01BE8C2D.34BA63C0"
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211

This is a multi-part message in MIME format.

------=_NextPart_000_02DB_01BE8C2D.34BA63C0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I reported that I took  e00 (ESRI export format) files from various free =
data GIS sites (12 of them) from around the county and converted them to =
various formats using Caliper's Maptitude. (www.caliper.com)  Complete =
success.=20

I repeated the same experiment using MapInfo Pro (www.mapinfo.com).   I =
had the same results. I had a little glitch, but it was pointed out to =
me politely that I had not read the directions quite carefully enough. =
It all works now. (it is far simpler than getting a style change in MS =
word document.)=20

I now have all this free data in the format of two different GIS vendors =
other than ESRI (ArcInfo & ArcView).

The point I make here is that in fact, although the standard these days =
is ESRI GIS formats (and that is by no means not a bad idea) for those =
who choose something else, this is OK because our favorite software can =
likely do the  conversion and we can use the tools to get the job done =
with the tool we need and choose rather than being forced to choose =
something that has less or something different from what we need.=20

Richard E. Hoskins


------=_NextPart_000_02DB_01BE8C2D.34BA63C0
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2014.210" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I reported that I took&nbsp; e00 (ESRI =
export=20
format) files from various free data GIS sites (12 of them) from around =
the=20
county and converted them to various formats using Caliper's Maptitude. =
(<A=20
href=3D"http://www.caliper.com">www.caliper.com</A>)&nbsp; Complete =
success.=20
</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I repeated the same experiment using =
MapInfo Pro=20
(<A href=3D"http://www.mapinfo.com">www.mapinfo.com</A>). &nbsp; I had =
the same=20
results. I had a little glitch, but it was pointed out to me politely =
that I had=20
not read the directions quite carefully enough.&nbsp;It all works now. =
(it is=20
far simpler than getting a style change in MS word document.) =
</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>I now have all this free data in the =
format of two=20
different GIS vendors other than&nbsp;ESRI (ArcInfo &amp; =
ArcView).</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>The point I make here is that in fact, =
although the=20
standard these days is ESRI GIS formats (and that is by no =
means&nbsp;not a bad=20
idea) for those who choose something else, this is OK because our=20
favorite&nbsp;software can likely do the&nbsp; conversion and we can use =
the=20
tools to get the job done with the tool we need and choose rather than =
being=20
forced to choose something that has less or something different from =
what we=20
need. </FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT face=3DArial size=3D2>Richard E. =
Hoskins<BR></FONT></DIV></BODY></HTML>

------=_NextPart_000_02DB_01BE8C2D.34BA63C0--

.