Thu, Dec 9 2004
00:15:56
|
|
Request created by jidanni@jidanni.org
|
|
Return-Path |
<jidanni@jidanni.org>
|
Delivered-To |
grass-bugs@lists.intevation.de
|
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 |
|
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..."
|
|
Thu, Dec 9 2004
17:37:15
|
|
Mail sent by neteler@itc.it
|
|
Return-Path |
<neteler@itc.it>
|
Delivered-To |
grass-bugs@lists.intevation.de
|
Date |
Thu, 9 Dec 2004 17:37:11 +0100
|
From |
Markus Neteler <neteler@itc.it>
|
To |
Request Tracker <grass-bugs@intevation.de>
|
Cc |
grass5@grass.itc.it
|
Subject |
Re: [GRASS5] [bug #2820] (grass) v.build: discuss mysterious "support files"
|
Message-ID |
<20041209163710.GQ4854@thuille.itc.it>
|
Mail-Followup-To |
Request Tracker <grass-bugs@intevation.de>, grass5@grass.itc.it
|
References |
<20041208231556.DB9BD102C54@lists.intevation.de>
|
Mime-Version |
1.0
|
Content-Type |
text/plain; charset=us-ascii
|
Content-Disposition |
inline
|
In-Reply-To |
<20041208231556.DB9BD102C54@lists.intevation.de>
|
User-Agent |
Mutt/1.4.1i
|
X-Spam-Status |
No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
|
X-Spam-Level |
|
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
|
|
Thu, Dec 9 2004
17:37:22
|
|
Status changed to resolved by mneteler
|
|
Fri, Dec 10 2004
23:11:17
|
|
Mail sent by jidanni@jidanni.org
|
|
Return-Path |
<jidanni@jidanni.org>
|
Delivered-To |
grass-bugs@lists.intevation.de
|
To |
Markus Neteler via RT <grass-bugs@intevation.de>
|
Subject |
Re: [bug #2820] (grass) v.build: discuss mysterious "support files"
|
References |
<20041209163715.BEBA2102C74@lists.intevation.de>
|
From |
Dan Jacobson <jidanni@jidanni.org>
|
Date |
Fri, 10 Dec 2004 09:11:47 +0800
|
Message-ID |
<874qivlzxo.fsf@jidanni.org>
|
MIME-Version |
1.0
|
Content-Type |
text/plain; charset=us-ascii
|
X-Spam-Status |
No, hits=-4.2 tagged_above=-999.0 required=3.0 tests=BAYES_00, DATE_IN_PAST_12_24
|
X-Spam-Level |
|
H> I have added now: "GRASS is generating these support files
H> automatically, only in rare cases the user has to (re)build them.
OK, then can remove any SEE ALSOs to it that might be on
$ fgrep -l v.build\< */desc*|s
v.build.polylines/description.html
v.clean/description.html
v.hull/description.html
v.in.ascii/description.html
v.patch/description.html
And did you mention just exactly what files the mysterious "support
files" are? Probably only grown ups should know.
H> and added
H> +In case of errors, the user can optionally generate an error
H> +vector map containing the erroneous vectors for later inspection.
Mention: "In any case, a count of the errors will still be printed to
/dev/stdout." (if indeed that is what happens).
>> don't say "write topology to stdout"
>> say "build topology, but only write it to stdout, not the files"
H> Why? This is not the case.
>> or "don't build topology, instead only write any topology already
>> found to stdout..."
H> Even not the case.
well, crystallize building vs. not building, writing etc. reporting
etc. in the document. Otherwise it's like one of those sneaky contracts.
|
|
Fri, Dec 10 2004
23:11:17
|
|
Status changed to open by _rt_system
|
|
Mon, Dec 12 2005
12:18:55
|
|
Area changed to grass6 by msieczka
|
|
Wed, Aug 16 2006
18:03:59
|
|
Status changed to resolved by msieczka
|
|
Wed, Aug 16 2006
18:03:59
|
|
Mail sent by msieczka
|
|
Closing this bug. v.build explains enough now. Details are in
http://grass.itc.it/grass63/manuals/html63_user/vectorintro.html (a link has
been just added).
Maciek
|
|