|
|
| GeoCommunity Mailing List |
| |
| Mailing List Archives |
| Subject: | RE: GISList: Re: [Manifold\ Projection challenge... |
| Date: |
01/11/2002 05:03:46 PM |
| From: |
Robert Heitzman |
|
|
>AV3.2 has no problem with .e00 files. Use the program Import71 which comes
>with the install.
>
I've seem to have had IMPORT71 fail several times. I thought it had to do
with IMPORT71 choking on the output from the newer ESRI products. Maybe it
was some other reason.
I always struggle with the user interface. The "Export" field is the input
and the save to box needs a path name without a terminating / as remember.
I sure wish the output of IMPORT71 was Shapefiles instead of ArcInfo
coverages. I guess that was intentional on ESRI's part.
===============
I just tried an experiment on some National Wetlands Inventory .E00 files.
I converted them via IMPORT71 and imported them into 3.2. I only got
polygons, no lines or points were imported. Seems that 3.2 "discovers" the
ArcInfo folders, since I couldn't drill down into the coverage folders, but
upon import only the polygons were present. The polygons that did load did
not look like the polygons loaded by Manifold and ArcExplorer 2. They did
have attribute data attached at least, even if the shapes were incorrect.
I imported the same .E00 into manifold and got the Arc/Cnt/Label/Poly
components. The polygons did not cover the drawing 100% (gaps) and no
useful attribute data was present on any of the components, nor were any
data tables formed (except for one during my test of three seperate .E00
files), which was missing any ID data to link in back to the drawings.
I also tried using ArcExlorer 2 and had the most luck. It could find both
the lines and polygons and it even mapped the attribute data correctly! The
polygons had the same gap problem as Manifold so I would guess that the gaps
are in the source data. Too bad there isn't anyway to get data out of
ArcExplorer.
Of the three 3.2 did the worst job importing .E00 files via IMPORT71.
ArcExplorer did the best but bogarts the data. Manifold created good lines
and points (and maybe polygons if the source data was better) but w/o
attributes.
All in all I'm not very impressed with .E00. Seems most programs, including
ESRI, can read .E00 sucessfully all the time. Maybe - if the
make/model/version/day of the week of the exporting program is the same as
the importing program.
If I see sites that post public domain data in .E00 I always send them a
flame. If they are public agencies I write my congressperson. .E00 is not
a useful public interchange format IMHO.
I don't really expect Manifold to put much effort into .E00 support, seems
like a worthless cause.
It would be really nice if ESRI would update IMPORT71 to work with all
releases of .E00.(I just suspect it doesn't, it may.) And it would be
really, really nice if they would export shapefiles as an option.
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp.
To unsubscribe, write to gislist-unsubscribe@geocomm.com
________________________________________________________________________
Setup a GeoCommunity Account and have access to FAST DataDownloads
and Premium Career Posting at a discounted rate!
https://www.geocomm.com/cgi-bin/accounts/login
On-line Archives available at
http://spatialnews.geocomm.com/community/lists/
|
|
Sponsored by:
For information
regarding
advertising rates
Click Here!
|
