Rejected by Custodian

LE_MAILBOX le_mailbox at qmgate.anl.gov
Mon Dec 18 07:00:00 EST 1995


Mail*Link(r) SMTP               RE>prefix.txt & ARC/INFO ??

Max,

I'm not entirely sure that I'm going to properly address your
question, but I often associate point attribute data in ARC with
attributes taken from GRASS following this procedure.  It may be done
with any number of data types that a RDBMS such as INFO accepts
(character, integer, real, etc.).  In this case, the example is for a
character string 40 characters wide:

1.  generate the ARC coverage following the procedures to which you
alluded in your mail.

2.  create a "flat" file of your character attributes that will be
imported into INFO.  This file will contain only the labels, and must
be in exactly the same order as their respective points that were
imported using "generate" in ARC.  

3.  in INFO, define a new INFO item that is for the attributes only.
This item will contain the flat file info & then be linked to the new
ARC coverage:

        a.  start info
        b.  DEFINE <INFO.FILE>
                ITEM NAME:  <YOUR_CHOICE>
                INPUT LENGTH:  40    <UP TO YOU, REALLY>
                OUTPUT LENGTH:  41   (I'm not sure why, but I've been
told to keep the output length 1 longer than the input length)
                ITEM TYPE:   C
        c.  hit return to get out of define

4.  Now, populate this new INFO item with the add from command.  At
the INFO prompt:

        ADD FROM ../<flat_file_created_in_step_2>

5.  Exit from INFO (q stop)  and in ARC, JOINITEM the coverage with
the newly created INFO file:

        joinitem <cover>.pat <infofile> <cover>.pat $recno $recno link

6.  Now you should be ready to go.

If you have any questions, or this routine fails to work, please let
me know & we can work on it a bit further. 

Good luck,

Scott


------------------ RFC822 Header Follows ------------------
Received: by qmgate_backup.anl.gov with SMTP;18 Dec 1995 13:52:55 -0600
Received: (from daemon at localhost) by diego.cecer.army.mil (8.7/8.7) id
JAA10396 for grassu-people; Mon, 18 Dec 1995 09:32:43 -0600 (CST)
Received: from max.cecer.army.mil (max.cecer.army.mil [129.229.20.254]) by
diego.cecer.army.mil (8.7/8.7) with SMTP id JAA10392 for
<grassu-list at diego.cecer.army.mil>; Mon, 18 Dec 1995 09:32:41 -0600 (CST)
Received: from diablo-canyon.tucson.ars.ag.gov
(diablo-canyon.tucson.ars.ag.gov [198.22.133.2]) by max.cecer.army.mil
(8.6.9/8.6.9) with ESMTP id JAA29715 for <grassu-list at max.cecer.army.mil>;
Mon, 18 Dec 1995 09:11:40 -0600
Received: from kanab-creek.tucson.ars.ag.gov (kanab-creek.tucson.ars.ag.gov
[198.22.133.42]) by diablo-canyon.tucson.ars.ag.gov (8.6.10/8.6.9) with ESMTP
id IAA14699; Mon, 18 Dec 1995 08:32:09 -0700
From: Scott Miller <miller at tucson.ars.ag.gov>
Received: (miller at localhost) by kanab-creek.tucson.ars.ag.gov (8.6.10/8.6.9)
id IAA21656; Mon, 18 Dec 1995 08:31:13 -0700
Date: Mon, 18 Dec 1995 08:31:13 -0700
Message-Id: <199512181531.IAA21656 at kanab-creek.tucson.ars.ag.gov>
Sender: grass-lists-owner at moon.cecer.army.mil
Reply-To: grassu-list at moon.cecer.army.mil
Precedence: Bulk
Sender: grass-lists-owner at moon.cecer.army.mil.
Reply-To: grassu-list at moon.cecer.army.mil.
Precedence: Bulk
To: 100450.1143 at compuserve.com
Subject: Re: prefix.txt & ARC/INFO ??
In-Reply-To: Mail from 'Max Grad <100450.1143 at compuserve.com>'
      dated: 18 Dec 1995 11:38:01 GMT
Cc: grassu-list at max.cecer.army.mil








More information about the grass-user mailing list