v.in.arc(1)		      Grass User's Manual		   v.in.arc(1)



NNAAMMEE
       vv..iinn..aarrcc   -  Imports  vector  data  in ARC/INFO ungenerate format into
       GRASS.
       _(_G_R_A_S_S _V_e_c_t_o_r _D_a_t_a _I_m_p_o_r_t _P_r_o_g_r_a_m_)

SSYYNNOOPPSSIISS
       vv..iinn..aarrcc
       vv..iinn..aarrcc hheellpp
       vv..iinn..aarrcc [--nn] ttyyppee==_n_a_m_e lliinneess__iinn==_n_a_m_e  [ppooiinnttss__iinn==_n_a_m_e]	[tteexxtt__iinn==_n_a_m_e]
       vveeccttoorr__oouutt==_n_a_m_e [iiddccooll==_v_a_l_u_e] [ccaattccooll==_v_a_l_u_e] [aattttccooll==_v_a_l_u_e]

DDEESSCCRRIIPPTTIIOONN
       The user may wish to use GRASS programs on data files that were created
       by other GISs.  To do this, the user must first convert data  files  in
       these  systems'	formats  to  GRASS's  file format.  Bringing data from
       other systems into GRASS is termed file	_i_m_p_o_r_t.   Sending  GRASS  data
       files out into other systems' formats is termed file _e_x_p_o_r_t.


       A variety of GRASS programs exist to import and export data to and from
       GRASS.  The _v_._i_n_._a_r_c program will convert  vector  data	in  ARC/INFO's
       "Generate"  format to GRASS's vector file format, and bring it into the
       user's current GRASS mapset.  The files to be imported  to  GRASS  must
       first  have  been  exported from ARC/INFO using the ARC/INFO _U_n_g_e_n_e_r_a_t_e
       command, and may represent either linear features ("line coverage")  or
       areal   features  ("polygon  coverage").   The  _A_R_C_/_I_N_F_O  _U_s_e_r_'_s  _G_u_i_d_e
       describes how files containing linear and  polygonal  features  can  be
       exported  from ARC/INFO, in a section detailing the use of the _U_n_g_e_n_e_r_-
       _a_t_e command.


       NNoottee 11::	The ARC coverage must be set to single precision  before  run-
       ning  _U_n_g_e_n_e_r_a_t_e.  If it is not, first copy it to another coverage that
       is set to single precision, then run _U_n_g_e_n_e_r_a_t_e.


       NNoottee 22::	To use for text attributes, numeric fields  with  values  >999
       may  contain  no  commas or TABs.  Also, the first record must have all
       fields filled.

OOPPTTIIOONNSS
       Program parameters and the flag have the following meanings.



   FFllaaggss::
       --nn     Neatline.  Vectors representing  a  box  (neatline)  around  the
	      input  vector data will be inserted into the output GRASS vector
	      file.




   PPaarraammeetteerrss::
       ttyyppee==_n_a_m_e
	      Coverage type.  Either polygon, or line.
	      Options:	polygon, line

       lliinneess__iinn==_n_a_m_e
	      ARC/INFO ungenerate lines file;  ungenerate  format  input  file
	      containing line or polygon coordinates.

       ppooiinnttss__iinn==_n_a_m_e
	      ARC/INFO	ungenerate  label-points file; ungenerate format input
	      file containing label-point coordinates; only applies to	'poly-
	      gon' type data.

       tteexxtt__iinn==_n_a_m_e
	      ARC/INFO	ungenerate  label-text	file;  ungenerate format input
	      file containing  category  numbers  and  (optionally)  attribute
	      text.

       vveeccttoorr__oouutt==_n_a_m_e
	      Resultant GRASS vector output file.

       iiddccooll==_v_a_l_u_e
	      ID  Number column in label-text file.  Number of label-text col-
	      umn containing line-ID numbers.

       ccaattccooll==_v_a_l_u_e
	      GRASS category column in label-text file.  Number of  label-text
	      column containing category values.

       aattttccooll==_v_a_l_u_e
	      GRASS attribute column in label-text file.  Number of label-text
	      column containing attribute text.



       This program can be run either non-interactively or interactively.  The
       program will run non-interactively if the user specifies the (optional)
       flag setting and needed parameter values on the command line, using the
       form:


       vv..iinn..aarrcc  [--nn]  ttyyppee==_n_a_m_e lliinneess__iinn==_n_a_m_e [ppooiinnttss__iinn==_n_a_m_e] [tteexxtt__iinn==_n_a_m_e]
       vveeccttoorr__oouutt==_n_a_m_e [iiddccooll==_v_a_l_u_e] [ccaattccooll==_v_a_l_u_e] [aattttccooll==_v_a_l_u_e]





       Alternately, the user can type:


       vv..iinn..aarrcc



       on the command line without program arguments;  in this case, the  pro-
       gram  will prompt the user for the flag setting and parameter values in
       the manner shown below.




       In ARC/INFO, three files are used to store polygon data:


       1) a _l_i_n_e_s _f_i_l_e, which contains coordinates of all the area edge lines;
       2) a _l_a_b_e_l_-_p_o_i_n_t _f_i_l_e, which contains coordinates of label-points (each
       of which has associated with it a unique label-point ID	number).   One
       label-point  is associated with each polygon defined in the _l_i_n_e_s _f_i_l_e;
       3) a _l_a_b_e_l_-_t_e_x_t _f_i_l_e, which associates each label-point ID number  with
       a category number and category ("attribute") text.

       Linear  feature	data  are  stored in two files: 1) a _l_i_n_e_s _f_i_l_e, which
       contains geographic coordinates defining lines,	each  with  a  line-ID
       number;	and 2) a _l_a_b_e_l_-_t_e_x_t _f_i_l_e, which associates each line-ID number
       with a category number and attribute text.




       These data files are described in further detail below, under the  DATA
       FILE FORMATS section.

IINNTTEERRAACCTTIIVVEE MMOODDEE
       The  program  will  prompt  the user for the flag setting and parameter
       values if the user does not specify these on the command line.	First,
       the  user  will	be  asked to assign a name to the vector file to store
       program output:
	    VECTOR (DIGIT) FILENAME
	    Enter 'list' for a list of existing binary vector files
	    Hit RETURN to cancel request
	    >
	Next, the user is asked to specify the COVERAGE (feature) type	to  be
       imported into GRASS.  Valid coverage types are ppoollyyggoonn and lliinnee.
	    COVERAGE TYPE
	    Enter "polygon" or "line"
	    Hit RETURN to cancel request
	    >
	IMPORTING A POLYGON COVERAGE


       If  the user chooses POLYGON coverage, he is asked if he wishes a neat-
       line placed around his data.  (The existence of neatlines in the output
       file can facilitate subsequent patching of data files.)
	    NEATLINE
	    Do you want a neatline ?
	    Enter "yes" or "no"
	    >
	If the user types yyeess, vectors that box the data will be inserted into
       the GRASS vector output file (_v_e_c_t_o_r___o_u_t); otherwise, no neatline  will
       be inserted into the output file.


       Next,  the user is prompted for the name of an existing lines-file con-
       taining the geographic coordinates of the arcs forming polygon  perime-
       ters.   The  lines-file	is  created with the ARC/INFO _U_n_g_e_n_e_r_a_t_e _L_I_N_E_S
       option, and is in the same format at the _p_r_e_f_i_x_._p_o_l file created by the
       _v_._o_u_t_._a_r_c
	program.  The user sees the following prompt:
	    LINES FILENAME
	    Enter name of the file created with the LINES
	    option of the ARC/INFO Ungenerate command.
	    Hit RETURN to cancel request
	    >
	 The  next  prompt for coverage type "polygon" asks for the name of an
       existing label-points file.  The label-points file is created with  the
       _U_n_g_e_n_e_r_a_t_e  _P_O_I_N_T_S  option, and is in the same format as the _p_r_e_f_i_x_._l_a_b
       file created by the _v_._o_u_t_._a_r_c
	program.  The user sees the following prompt:
	    LABEL-POINTS FILENAME
	    Enter name of file created with the POINTS
	    option of the ARC/INFO Ungenerate command.
	    Hit RETURN if there is no such file
	    >
	Finally, the program asks the user for the name of an existing	label-
       text file.  This file associates each label-point ID number with a text
       string.	It is in the same format as the _p_r_e_f_i_x_._t_x_t file created by the
       _v_._o_u_t_._a_r_c
	program.
	    LABEL-TEXT FILENAME
	    Enter the name of a file that associates
	    label-point ID numbers with text label strings
	    Hit RETURN if there is no such file
	    >
	 _v_._i_n_._a_r_c  then scans the label-text file to find the numbers of lines
       and columns, the column headers (if any), and the first three lines  of
       actual data in the file.  It displays this information to standard out-
       put to help the user determine which columns will hold the ID, Category
       value, and Attribute text data in the new vector output file.  A sample
       of the program's output is shown below:
	  The LABEL-TEXT file has been scanned. There are 132
	  lines in the file and 8 columns in the file

	  Column headers of the LABEL-TEXT file:
	    rec# AREA PERIMETER SOILS# SOILS-ID  SOIL-CODE  DRAIN_CODE	TXTUR-
       CODE

	  Here are the first three lines :
	       1   -2.30228E+07  19399.848     1      0      0	    0	   0
	       2     81079.875	  1678.826     2      1     15	    3	   3
	       3    955952.500	 10229.637     3      2     19	    8	   8
	 The  column of category values must contain only integer values.  The
       attribute text column can contain a floating point number, an  integer,
       or a word (text string).


       Finally,  the  user  is	prompted to enter line ID, category value, and
       attribute text column numbers.
	    Enter the number of the column that should be used
	    for line IDs (probably the column with -ID) :

	       Enter the number of the column that is to be used
	       for GRASS category values:

	       Enter the number of the column that should be used
	       for GRASS attribute text:
	Once these column numbers have been entered, _v_._i_n_._a_r_c will begin  con-
       verting	the  ARC/INFO  "Generate"  format files into GRASS vector file
       format.


       IMPORTING A LINE COVERAGE


       The user will also be prompted for input when importing ARC/INFO  files
       containing  linear features ("line coverage") data.  Like polygon data,
       linear features are constructed by the series of  arcs  (aka,  vectors)
       defining  their	perimeters.   If  the  user selects LINE coverage, the
       prompts seen by the user will be different in two respects  from  those
       for POLYGON coverage.  First, the user will not be asked whether or not
       a neatline is desired;  and second, no label-points file name  will  be
       requested.   In other respects, the treatment of LINE coverage is iden-
       tical to that for POLYGON coverage.


       The user is prompted for the name of the lines-file containing the geo-
       graphic coordinates of these arcs.  The lines-file must first have been
       created with the ARC/INFO _U_n_g_e_n_e_r_a_t_e _L_I_N_E_S option, and is in  the  same
       format as the _p_r_e_f_i_x_._l_i_n file created by the GRASS _v_._o_u_t_._a_r_c
	program.



DDAATTAA FFIILLEE FFOORRMMAATTSS
       Following are examples of the data files discussed above.


       LINES FILE, also known as _p_r_e_f_i_x_._l_i_n or _p_r_e_f_i_x_._p_o_l file.


       This type of file can be created in ARC/INFO by using the _l_i_n_e_s subcom-
       mand of the _U_n_g_e_n_e_r_a_t_e command.	 Each line (aka, arc) is defined by  a
       line-ID number, followed by a list of at least two easting and northing
       coordinate pairs, followed by a line with the word "END".  The file  is
       terminated with the word "END".


       The  line-ID  number  is  important only for line coverage data.  For a
       line coverage, the line-ID number is the number	that  associates  each
       line with its attribute data.
       3
       711916.000000  4651803.000000
       711351.875000  4651786.000000
       END
       3
       709562.500000  4651731.000000
       709617.250000  4651624.000000
       709617.250000  4651567.000000
       709585.000000  4651503.000000
       709601.125000  4651470.000000
       709696.875000  4651503.000000
       709720.500000  4651574.000000
       709823.750000  4651575.000000
       709893.125000  4651741.000000
       END
       3
       710296.875000  4651491.000000
       710295.125000  4651470.000000
       710223.000000  4651454.000000
       710154.500000  4651463.000000
       END
       END



       LABEL-POINTS FILE, also known as _p_r_e_f_i_x_._l_a_b file.


       This type of file can be created in ARC/INFO using the _P_o_i_n_t_s option of
       the _U_n_g_e_n_e_r_a_t_e command.	The first number on each line is a label-point
       ID number, and the following two numbers are (respectively) the easting
       and northing coordinate pair representing the  geographic  location  of
       the label-point.
       1    711539.875000  4651743.000000
       2    711429.000000  4650632.000000
       3    711027.625000  4651736.000000
       4    711022.625000  4651519.000000
       5    710482.750000  4651494.000000
       6    710474.500000  4651667.000000
       7    709269.750000  4651018.000000
       8    709726.500000  4651604.000000
       9    708926.375000  4651195.000000
       10   708567.500000  4651644.000000
       11   708272.750000  4651407.000000
       END
	LABEL-TEXT FILE, also known as _p_r_e_f_i_x_._t_x_t file.


       The ARC/INFO _D_i_s_p_l_a_y command can be used to create this type of file.
       1    -2.30228E+07   19399.848 1	  0    0    0
       2    81079.875 1678.826	2    1	  15   3
       3    955952.500	   10229.637 3	  2    19   8
       4    41530.875 926.887		4 3    17   3
       5    87900.188 1900.909	5    4	  13   3
       6    166125.125	   3512.950  6	  5    15   3
       7    29460.563 824.968	7    6	  17   3
       8    1022769.875    9105.707  8	  7    20   9
       9    51385.500 1075.638	9    8	  17   3
       10   376834.875	   4470.027  10   9    9    2
       11   65802.688 1575.088	11   10   16   3


NNOOTTEESS
       ARC/INFO  data  can  be imported even if a label-points and/or a label-
       text file are missing;  however, the lines and/or areas	imported  will
       not be labeled.


       _v_._i_n_._a_r_c  can  handle  label-text  files  both  with and without header
       lines.


       Import files are read from any directory, v.in.arc can handle  relative
       or absolute file names with path.

SSEEEE AALLSSOO
	_v_._i_n_._s_h_a_p_e_, _v_._i_n_._d_x_f_, _v_._o_u_t_._a_r_c_, _v_._s_u_p_p_o_r_t

AAUUTTHHOORR
       Dave Johnson

       DBA Systems, Inc.

       10560 Arrowhead Drive

       Fairfax, Virginia 22030

       _L_a_s_t _c_h_a_n_g_e_d_: _$_D_a_t_e_: _2_0_0_2_/_0_1_/_2_5 _0_5_:_4_5_:_3_5 _$



GRASS 5.0							   v.in.arc(1)
