importing ARC/INFO files

[Malcolm Williamson]

David is correct in his assumption that this file is not in the correct 
format; the .E00 extension identifies it as an Arc/Info "export" file, a 
proprietary format used to share coverages between users. What is needed 
is the "ungenerate" format. See the v.in.arc and v.out.arc pages for more 
details.
        -Malcolm
--
Malcolm D. Williamson - GIS Specialist           E-mail: malcolm at cast.uark.edu
Center for Advanced Spatial Technologies      Telephone: (501) 575-6159
Ozark Rm. 12                                        Fax: (501) 575-5218 
University of Arkansas              
Fayetteville, AR 72701

On Mon, 22 Apr 1996, David Viebrock wrote:

> 
> 
> On Fri, 19 Apr 1996, James Curry wrote:
> 
> > Hi,
> > 
> > I have a file that is supposed to be an arc/info file. I'd like to 
> > import it into GRASS. I have tried using v.in.arc but on each attempt
> > I have received the message:   ERROR: Reading LINES file
> > 
> > Below is the firs 20 lines of the file that I am trying to import.
> > Can someone tell me what is causing the error?
> > 
> > Thanks.
> > -Jim
> > 
> > -----
> > EXP  0 /DATA3/KOFFMAN/PENDERGAST/SITEMAPS/FH_MAPU.E00                      
     
> > ARC  2
> >          1         1         0         0         0         0         2
> >  4.4081297E+05 3.6828878E+06 4.4076409E+05 3.6828938E+06
> >          2         2         0         0         0         0         2
> >  4.4081328E+05 3.6828893E+06 4.4076581E+05 3.6828950E+06
> >          3         3         0         0         0         0         2
> >  4.4101038E+05 3.6827960E+06 4.4096928E+05 3.6828353E+06
> >          4         4         0         0         0         0         2
> >  4.4092441E+05 3.6829453E+06 4.4093116E+05 3.6830153E+06
> >          5         5         0         0         0         0       410
> >  4.4096928E+05 3.6828353E+06 4.4096906E+05 3.6828355E+06
> >  4.4096884E+05 3.6828358E+06 4.4096863E+05 3.6828360E+06
> >  4.4096844E+05 3.6828363E+06 4.4096822E+05 3.6828363E+06
> >  4.4096800E+05 3.6828365E+06 4.4096778E+05 3.6828368E+06
> >  4.4096756E+05 3.6828370E+06 4.4096734E+05 3.6828373E+06
> >  4.4096713E+05 3.6828375E+06 4.4096691E+05 3.6828378E+06
> >  4.4096672E+05 3.6828378E+06 4.4096650E+05 3.6828380E+06
> >  4.4096628E+05 3.6828383E+06 4.4096606E+05 3.6828385E+06
> >  4.4096588E+05 3.6828388E+06 4.4096566E+05 3.6828390E+06
> >  4.4096544E+05 3.6828390E+06 4.4096522E+05 3.6828393E+06
> > 
> 
> The appropriate import command to use would depend partly on what type of
> data (polygon, line, or site).  You don't specify what the output command
> was used to export this data from arc/info but that command would then
> determine the appropriate grass command to use.  I don't think this is a
> data format that the v.in.arc command was intended to use (either polygon
> or line).
> 
> Try asking your data source what they used to create this file and if it
> is something importable by grass.  Typicall arc/info data export commands
> would be "export" for other arc/info systems, "ungenerate" for v.in.arc 
> in grass, "arcdlg" for dlg format data, or "arcdxf" for cad format data.
> It would be a good idea to request data export files in a format you know
> you can read into grass such as dlg or "ungenerate" format for v.in.arc.
> So...  Check back with your source and figure it from there.
> 
> -Dave Viebrock
> viebrock at gis.cwu.edu  
>