here are some samples that might be helpful. I dont have a
straight up answer to your question, but if i look through these export
files in greater detail I may be able to help come up with a pattern or
key words that would aid in automating this process. Right off
the bat I dont see anything that tells you
directly what it is, or what topology is built for. The topology
in coverages/e00's builds off each other. meaning you can have various
"info" files associated with each data feature type. I pasted
e00's of a simple point, line and polygon coverage or E00 file.
Its lenghty, but they features are broken by the line of "="
signs. If you can script something out i'm sure it would be
useful. i ran into this problem a while back.<br>
<br>
===================================================================<br>
Here's an example of a simple point data set in e00 format. The
key word "LAB" after the EXP line seems to indicate its a point
coverage or "label" as the term is synomous in ESRI coverage terms. <br>
EXP 0
T:\GARBAGE\THE_PT.E00
<br>
LAB 2<br>
1 0 3.6663384E+00 3.0019684E+00<br>
3.6663384E+00 3.0019684E+00 3.6663384E+00 3.0019684E+00<br>
-1 0 0.0000000E+00 0.0000000E+00<br>
TOL 2<br>
1 2 0.0000000E+00<br>
2 2 0.0000000E+00<br>
3 2 0.0000000E+00<br>
4 2 0.0000000E+00<br>
5 2 0.0000000E+00<br>
6 2 0.0000000E+00<br>
7 2 0.0000000E+00<br>
8 2 0.0000000E+00<br>
9 2 0.0000000E+00<br>
10 2 0.0000000E+00<br>
-1
0
0
0
0
0 0<br>
SIN 2<br>
EOX<br>
LOG 2<br>
200511141212 0 0 0user ARCEDIT T:\GARBAGE\THE_PT<br>
~<br>
200511141214 0 0 0user build the_pt point<br>
~<br>
EOL<br>
IFO 2<br>
THE_PT.BND
XX 4 4
16 1<br>
XMIN
4-1 14-1 12 3 60-1 -1
-1-1
1-<br>
YMIN
4-1 54-1 12 3 60-1 -1
-1-1
2-<br>
XMAX
4-1 94-1 12 3 60-1 -1
-1-1
3-<br>
YMAX
4-1 134-1 12 3 60-1 -1
-1-1
4-<br>
3.6663384E+00 3.0019684E+00 3.6663384E+00 3.0019684E+00<br>
THE_PT.PAT
XX 4 4
16 1<br>
AREA
4-1 14-1 12 3 60-1 -1
-1-1
1-<br>
PERIMETER
4-1 54-1 12 3 60-1 -1
-1-1
2-<br>
THE_PT#
4-1 94-1 5-1 50-1 -1
-1-1
3-<br>
THE_PT-ID 4-1
134-1 5-1 50-1 -1
-1-1
4-<br>
0.0000000E+00
0.0000000E+00
1 1<br>
THE_PT.TIC
XX 3 3
12 4<br>
IDTIC
4-1 14-1 5-1 50-1 -1
-1-1
1-<br>
XTIC
4-1 54-1 12 3 60-1 -1
-1-1
2-<br>
YTIC
4-1 94-1 12 3 60-1 -1
-1-1
3-<br>
1 4.5521653E-01 4.9458661E+00<br>
2 6.5329719E+00 4.7490153E+00<br>
3 2.9527557E-01 4.1830707E-01<br>
4 7.1604323E+00 2.9527557E-01<br>
EOI<br>
EOS<br>
==============================================================<br>
here is a simple line coverage. The "ARC" after EXP line seems to
indicate its a line, but the same thing is present in a polygon
model. a distinction is the ".aat" file which is the arc
attribute table. this says there is line topology built for the
dataset. ARC keyword in conjunction with a .AAT file would indicate a
line coverage/e00.<br>
EXP 0
T:\GARBAGE\THE_LINE.E00
<br>
ARC 2<br>
1
1
1
2
0
0 3<br>
2.6697834E+00 3.3218503E+00 4.0354328E+00 2.4360235E+00<br>
4.3553147E+00 2.2883856E+00<br>
-1
0
0
0
0
0 0<br>
TOL 2<br>
1 2 2.0000000E-03<br>
2 2 0.0000000E+00<br>
3 2 0.0000000E+00<br>
4 2 0.0000000E+00<br>
5 2 0.0000000E+00<br>
6 2 1.6855314E-02<br>
7 2 1.6855314E-03<br>
8 2 1.6855314E-03<br>
9 2 1.6855314E-03<br>
10 2 1.6855314E-03<br>
-1
0
0
0
0
0 0<br>
SIN 2<br>
EOX<br>
LOG 2<br>
200511141213 0 0 0user ARCEDIT T:\GARBAGE\THE_LINE<br>
~<br>
200511141214 0 0 0user build the_line line<br>
~<br>
EOL<br>
IFO 2<br>
THE_LINE.AAT
XX 7 7
28 1<br>
FNODE#
4-1 14-1 5-1 50-1 -1
-1-1
1-<br>
TNODE#
4-1 54-1 5-1 50-1 -1
-1-1
2-<br>
LPOLY#
4-1 94-1 5-1 50-1 -1
-1-1
3-<br>
RPOLY#
4-1 134-1 5-1 50-1 -1
-1-1
4-<br>
LENGTH
4-1 174-1 12 3 60-1 -1
-1-1
5-EXP 0
======================================================<br>
This is a simple polygon coverage in e00 format. This too has the
"ARC" after the EXP line, but further down in the E00 you can see there
is a .PAL file. I believe this stands for Polygon Attribute
Label. It also has a LAB component because in the ESRI polygon
coverage model, all polygons have label points associated with them. <br>
EXP 0
T:\GARBAGE\THE_POLY.E00
<br>
ARC 2<br>
1
2
1
1
2
1 5<br>
4.9458661E+00 4.3452330E+00 4.9458661E+00 2.9404526E+00<br>
6.4960628E+00 2.9650588E+00 6.5575781E+00 4.3676176E+00<br>
4.9458661E+00 4.3452330E+00<br>
-1
0
0
0
0
0 0<br>
CNT 2<br>
0 5.7361488E+00 3.6591427E+00<br>
1 5.7361488E+00 3.6591427E+00<br>
1<br>
-1
0
0
0
0
0 0<br>
LAB 2<br>
1 2 5.7361197E+00 3.6561463E+00<br>
5.7361197E+00 3.6561463E+00 5.7361197E+00 3.6561463E+00<br>
-1 0 0.0000000E+00 0.0000000E+00<br>
PAL 2<br>
2 4.9458661E+00 2.9404526E+00 6.5575781E+00 4.3676176E+00<br>
0
0
0
1
1 2<br>
1 4.9458661E+00 2.9404526E+00 6.5575781E+00 4.3676176E+00<br>
-1
1 1<br>
-1
0
0
0
0
0 0<br>
TOL 2<br>
1 1 2.0000001E-03<br>
2 2 0.0000000E+00<br>
3 2 0.0000000E+00<br>
4 2 0.0000000E+00<br>
5 2 0.0000000E+00<br>
6 2 1.6117120E-02<br>
7 2 1.6117120E-03<br>
8 2 1.6117120E-03<br>
9 2 1.6117120E-03<br>
10 2 1.6117120E-03<br>
-1
0
0
0
0
0 0<br>
SIN 2<br>
EOX<br>
LOG 2<br>
200511141214 0 0 0user ARCEDIT T:\GARBAGE\THE_POLY<br>
~<br>
200511141214 0 0 0user ARCEDIT T:\GARBAGE\THE_POLY<br>
~<br>
200511141214 0 0 0user build the_poly<br>
~<br>
EOL<br>
IFO 2<br>
THE_POLY.BND
XX 4 4
16 1<br>
XMIN
4-1 14-1 12 3 60-1 -1
-1-1
1-<br>
YMIN
4-1 54-1 12 3 60-1 -1
-1-1
2-<br>
XMAX
4-1 94-1 12 3 60-1 -1
-1-1
3-<br>
YMAX
4-1 134-1 12 3 60-1 -1
-1-1
4-<br>
4.9458661E+00 2.9404526E+00 6.5575781E+00 4.3676176E+00<br>
THE_POLY.PAT
XX 4 4
16 2<br>
AREA
4-1 14-1 12 3 60-1 -1
-1-1
1-<br>
PERIMETER
4-1 54-1 12 3 60-1 -1
-1-1
2-<br>
THE_POLY#
4-1 94-1 5-1 50-1 -1
-1-1
3-<br>
THE_POLY-ID 4-1
134-1 5-1 50-1 -1
-1-1
4-<br>
-2.2184148E+00
5.9709468E+00
1 0<br>
2.2184148E+00
5.9709468E+00
2 1<br>
THE_POLY.TIC
XX 3 3
12 4<br>
IDTIC
4-1 14-1 5-1 50-1 -1
-1-1
1-<br>
XTIC
4-1 54-1 12 3 60-1 -1
-1-1
2-<br>
YTIC
4-1 94-1 12 3 60-1 -1
-1-1
3-<br>
1 4.5521653E-01 4.9458661E+00<br>
2 6.5329719E+00 4.7490153E+00<br>
3 2.9527557E-01 4.1830707E-01<br>
4 7.1604323E+00 2.9527557E-01<br>
EOI<br>
EOS<br>
===================================================<br>
<br>
<br>
<br><div><span class="gmail_quote">On 11/14/05, <b class="gmail_sendername">Kirk R. Wythers</b> <<a href="mailto:kwythers@umn.edu" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">kwythers@umn.edu
</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I am using the v.in.e00 script to import a large number of .e00<br>files. One nuisance I face is that I do not know what type each file<br>happens to be. Some files I try type=area only to get the<br><br>Importing areas...
<br>ERROR: Layer 'ARC' not available<br>An error occurred. Stop.<br><br>message. In those situations I try type=point, and everything works<br>fine. Does anyone know of a clever way to test for what the file type<br>is before hand? If this is possible I could script this whole process.
<br><br>Thanks,<br><br>Kirk<br><br></blockquote></div><br>