From lists-owner@amber.cecer.army.mil Tue Feb 4 08:19:43 1992
Received: from amber.cecer.army.mil by zorro.cecer.army.mil (4.1/SMI-4.1)
id AA28456; Tue, 4 Feb 92 08:19:43 CST
Received: from zorro.cecer.army.mil by amber.cecer.army.mil (4.1/SMI-4.1)
id AA01206; Tue, 4 Feb 92 08:19:37 CST
Received: from amber.cecer.army.mil by zorro.cecer.army.mil (4.1/SMI-4.1)
id AA28453; Tue, 4 Feb 92 08:19:37 CST
Return-Path: <daum@bnlux1.bnl.gov>
Received: from bnlux1.bnl.gov ([130.199.128.1]) by amber.cecer.army.mil (4.1/SMI-4.1)
id AA01200; Tue, 4 Feb 92 08:19:33 CST
Received: by bnlux1.bnl.gov (5.57/Ultrix3.0-C)
id AA14144; Tue, 4 Feb 92 09:19:01 -0500
Date: Tue, 4 Feb 92 09:19:01 -0500
From: daum@bnlux1.bnl.gov (mary l. daum)
Message-Id: <9202041419.AA14144@bnlux1.bnl.gov>
Reply-To: grassu-list@amber.cecer.army.mil
Precedence: Bulk
To: grassu-list@amber.cecer.army.mil
Subject: v.in.arc
Cc: daum@bnlcl6.bnl.govI hope someone can help me with a v.in.arc problem.
We used it successfully a few weeks ago on a mainframe
(VAX/Ultrix) and it worked like a charm. Now Grass is
installed on SUN workstations (it's no longer on the VAX)
and we can't get v.in.arc to work as expected.We have an ASCII file in ARC/INFO UNGENERATE format in
the arc subdirectory of the mapset we are using, and Grass
recognizes the existence of the file, so that must be OK.
But Grass is asking for a binary vector file, rather than
ASCII. ^^^^^^Am I missing something? Thanks for any hints anyone
can offer.
Mary Daum
Brookhaven National Lab
daum@bnlux1.bnl.gov
When you run the interactive version of v.in.arc, the first prompt that
is displayed is for the OUTPUT (binary) vector file name. This, obviously,
would be more intuitive if it came later in the series of prompts.
--
David Stigberg
US Army Construction Engineering Research Lab
Spatial Analysis & Systems Team
217-352-6511 x631
stigberg@zorro.cecer.army.mil