m.in.e00(1)	       Grass User's Manual	      m.in.e00(1)



NNAAMMEE
       _m_._i_n_._e_0_0 - Read an ESRI e00 file

       _(_G_R_A_S_S _V_e_c_t_o_r_/_R_a_s_t_e_r_/_S_i_t_e_s _D_a_t_a _I_m_p_o_r_t _P_r_o_g_r_a_m_)

SSYYNNOOPPSSIISS
       mm..iinn..ee0000

       mm..iinn..ee0000  [--iiddttss] iinnppuutt==_n_a_m_e [mmaappsseett==_n_a_m_e] [aaccttiioonn==_w_h_a_t _t_o
       _d_o] [vveerrbboossee==_d_e_b_u_g _l_e_v_e_l] [llooggffiillee==_n_a_m_e]

DDEESSCCRRIIPPTTIIOONN
       The m.in.e00 program is designed to import  ESRI  Arc/Info
       e00  ascii  archives.   The input file may be a compressed
       e00 file : m.in.e00 will automatically recognize the  for-
       mat.

       The module not only can analyse the content of an Arc/Info
       file, but try to create the  objects  described	(geometry
       and attributes).

       m.in.e00  will be run non-interactively if the user speci-
       fies program arguments on  the  command	line,  using  the
       form:

       mm..iinn..ee0000  [--iiddttss] iinnppuutt==_n_a_m_e [mmaappsseett==_n_a_m_e] [aaccttiioonn==_w_h_a_t _t_o
       _d_o] [vveerrbboossee==_d_e_b_u_g _l_e_v_e_l] [llooggffiillee==_n_a_m_e]

       Alternately, the user can simply type:

       mm..iinn..ee0000

       on the command line without  program  arguments.  In  this
       case, the user will be prompted for parameter values using
       the standard GRASS user interface described in the  manual
       entry for parser.

FFEEAATTUURREESS
       m.in.e00   attemps  to  retrieve  all  information  in  an
       Arc/Info export file (.e00): points,  line,  polygon,  and
       grid  coverage.	The  attribute	of  each  "vector" object
       (points, line, and polygon) is  the  Arc/Info  coverage-ID
       (and not the coverage-#). Both single and double precision
       are supported.

       GRASS files created have the name extracted from the first
       line  of  the e00 file, i.e. the name of the coverage. The
       file is read from the current directory	unless	specified
       differently.

       The  following rules are used : A line vector file is cre-
       ated when there is a non-empty ARC  section,  and  neither
       PAL   (Polygon	Attribute  Label)  section,  neither  PAT
       (Point/Polygon Attribute Table)	table  in  INFO  section.
       Otherwise  a polygon vector file is created, excepted when
       the ARC section is empty or doesn't exist, in which case a
       site file is created.

       Dig_cats  files	are  created  if  the  PAT  or	AAT  (Arc
       Attribute Table) tables	have  more  attributes	than  the
       standard  one.  If  there  is  one  extra  attribute,  the
       dig_cats file has  the  name  of  the  vector  (dig)  file
       created.  If  there  is more than one extra attribute, the
       dig_cats    files    have    names     of     the     form
       cover_name.attribute_name. If you want to use one of them,
       you must rename it so it matches the name  of  the  vector
       file.  Doing  this, the vector modules will use it for the
       raster file created.


       To "activate" a category label file  for  the  vector  map
       "cover_name", change to:


	   cd $LOCATION/dig_cats/
	   ls cover_name.*
	   cp cover_name.attribute_name cover_name
	   cd $HOME
	   v.support cover_name

       If  you	want  to use another table entry, you have to run
       above	     procedure		accordingly	     with
       cover_name.other_attribute_name.


       When  importing	raster file ("GRID"), cats files are cre-
       ated the same way in $LOCATION/cats.  Note that	an  empty
       cat  file  is  automaticaly  put  in this directory when a
       raster file  is	created,  so  m.in.e00	allways  use  the
       cover_name.attribute_name  form for raster category files.

OOPPTTIIOONNSS
       _m_._i_n_._e_0_0 requires the user to enter the following informa-
       tion:

   FFllaaggss::
       --ii  Use	the  "feature-ID" of the arc info objects to link
	   geometry and attribute's tables. The default is to use
	   the	"feature-#" field (which is an internal link, but
	   you should not rely on it for linking Arc/Info objects
	   to an external database.

       --dd  Use	a  database  instead of as many dig_cats files as
	   you have attributes in the INFO tables (not yet opera-
	   tional).

       --tt  Put	all attributes in one category file, separated by
	   tabs (not yet operational).

       --ss  Automatically run "v.support" on newly created  vector
	   file.


   PPaarraammeetteerrss::
       mmaappsseett==_n_a_m_e
	   For	creating a new mapset for the data imported. This
	   may be useful, since we  cannot  create  a  projection
	   info  file and a default window in an existing mapset.
	   When a file is imported in  the  current  mapset,  you
	   should take care that they are in the same projection.
	   Unfortunately, you may run in trouble after that  when
	   using g.region (Cf BUGS).

       aaccttiioonn==_w_h_a_t _t_o _d_o
	   Five  options: analyse, raster, lines, vector and all.
	   By default, all is used and everything (grid,  points,
	   lines,  polygons)  is  imported.  Analyze  produces no
	   files, but only a log output (level 5) on stderr,  and
	   is useful to see whether the e00 file is clean or not.
	   Raster imports only grid section.  Lines imports  only
	   the	geometry  (no  label are attached to the lines or
	   polygons) of  a  point/line/polygon	coverage.  Vector
	   imports   a	point/line/polygon  coverage  with  their
	   attributes.

       vveerrbboossee==_d_e_b_u_g _l_e_v_e_l
	   Number between 0 (no trace of what's happening) and	9
	   (very verbose log).

       llooggffiillee==_n_a_m_e
	   Name  of  file  where  log  info  will  be written. By
	   default log info are directed to stderr.


BBUUGGSS AANNDD CCAAVVEEAATT
       If the E00 file contains areas, it is recommended  to  set
       the  map  scale	(in v.digit) to some big value (1:1), and
       run v.support again. Otherwise map threshold is	too  big,
       and v.support may fail even on clean data.


       You must know what to do with all the dig_cats file gener-
       ated when importing a vector coverage.

       The program may crash when unexpexted data (mainly in INFO
       section) are found, or when the input file is corrupted.

       There  is  no support for projection. Using verbose=1 lets
       you see the parameters of the e00 file, but you must  cre-
       ate the DEFAULT_WIND and the PROJ file yourself.

       New  mapset are always created with proj=0 zone=99. If the
       default proj and zone are not the same, g.region complains
       and d.vect or d.rast refuse to display your data. The only
       thing to do is to import in the current mapset.

RREEFFEERREENNCCEESS
       E00 format

SSEEEE AALLSSOO
       g.mapsets,  g.region,  g.setproj,   r.in.arc,   v.support,
       v.to.rast, v.in.shape

AAUUTTHHOORR
       Michel J. Wurtz, DIG/cemagref

       mw@teledetection.fr

       _L_a_s_t _c_h_a_n_g_e_d_: _$_D_a_t_e_: _2_0_0_2_/_0_5_/_1_0 _0_8_:_0_6_:_0_7 _$



GRASS 5.0					      m.in.e00(1)
