[GRASS5] [bug #2820] (grass) v.build: discuss mysterious "support files"

GRASS GIS GRASS GIS developer
1

this bug's URL: http://intevation.de/rt/webrt?serial_num=2820
-------------------------------------------------------------------------

In the v.build documentation, discuss these mysterious "support
files". Perhaps they are the files that live in .../dbf/... . Perhaps
they are the files called cidx coor dbln head hist sidx topo ... no it
couldn't be them.

Say just when one would need to use v.build. I mean who would want to
go thru life without "support". And the more support, and the more
often, the better.

Show how one can determine if one doesn't have support, but should,
and if one has support, but it isn't needed, etc.

Also,
Parameters:
   error Name of vector where errors are written
Say what will happen if we don't give this. Do our errors go up in
smoke...etc? Will we still be informed of them? Say so.

don't say "write topology to stdout"
say "build topology, but only write it to stdout, not the files"
or "don't build topology, instead only write any topology already
found to stdout..."

--- Headers Follow ---

From jidanni@jidanni.org Thu Dec 9 00:15:56 2004

Return-Path: <jidanni@jidanni.org>
Delivered-To: grass-bugs@lists.intevation.de
Received: from mail.intevation.de (aktaia [212.95.126.10])
  by lists.intevation.de (Postfix) with ESMTP id B5FCA102C35
  for <grass-bugs@lists.intevation.de>; Thu, 9 Dec 2004 00:15:56 +0100 (CET)
Received: from localhost (localhost [127.0.0.1])
  by mail.intevation.de (Postfix) with ESMTP id 8866736CD8
  for <grass-bugs@lists.intevation.de>; Thu, 9 Dec 2004 00:15:56 +0100 (CET)
Received: from frodo.hserus.net (frodo.hserus.net [204.74.68.40])
  by mail.intevation.de (Postfix) with ESMTP id 2A2ED36CE0
  for <grass-bugs@intevation.de>; Thu, 9 Dec 2004 00:15:55 +0100 (CET)
Received: from [219.69.72.86] (port=32784 helo=jidanni1)
  by frodo.hserus.net with esmtpsa
  (Cipher TLSv1:RC4-SHA:128) (Exim 4.43 #0)
  id 1CcB2H-0003gK-Kh by authid <jidanni> with plain
  for <grass-bugs@intevation.de>; Thu, 09 Dec 2004 04:45:54 +0530
To: grass-bugs@intevation.de
Subject: v.build: discuss mysterious "support files"
From: Dan Jacobson <jidanni@jidanni.org>
Date: Thu, 09 Dec 2004 04:28:22 +0800
Message-ID: <871xe0zg9l.fsf@jidanni.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Spam-Status: No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
X-Spam-Level:

-------------------------------------------- Managed by Request Tracker

2

On Thu, Dec 09, 2004 at 12:15:56AM +0100, Request Tracker wrote:

this bug's URL: http://intevation.de/rt/webrt?serial_num=2820
-------------------------------------------------------------------------

In the v.build documentation, discuss these mysterious "support
files". Perhaps they are the files that live in .../dbf/... . Perhaps
they are the files called cidx coor dbln head hist sidx topo ... no it
couldn't be them.

Say just when one would need to use v.build. I mean who would want to
go thru life without "support". And the more support, and the more
often, the better.

Question: Why not reading more than the first line?

Citation:
http://grass.itc.it/grass57/manuals/html57_user/v.build.html

"DESCRIPTION
These support files supply topology and category information
that are needed by other GRASS programs
"

Show how one can determine if one doesn't have support, but should,
and if one has support, but it isn't needed, etc.

I have added now:
"GRASS is generating these support files automatically,
only in rare cases the user has to (re)build them.
"

No, I won't explain "rare cases" in the documentation.
A rare case occurs if e.g. Radim asks the user to run v.build to
rebuild the topology for existing 5.7 maps in case of a format
change. Happened a very few times in the past.

Also,
Parameters:
   error Name of vector where errors are written
Say what will happen if we don't give this. Do our errors go up in
smoke...etc? Will we still be informed of them? Say so.

Yes, Sir.

Changed the message to:
- err_opt->description = "Name of vector where errors are written";
+ err_opt->description = "Name of vector map where erroneous vectors are written to";

and added
+In case of errors, the user can optionally generate an error
+vector map containing the erroneous vectors for later inspection.

to the documentation.

don't say "write topology to stdout"
say "build topology, but only write it to stdout, not the files"

Why? This is not the case.

or "don't build topology, instead only write any topology already
found to stdout..."

Even not the case.

Markus