On Tue, Dec 2, 2014 at 12:01 AM, Michael Barton michael.bar...@asu.edu
wrote:
On Dec 1, 2014, at 9:31 PM, Anna Petrášová kratocha...@gmail.com wrote:
On Mon, Dec 1, 2014 at 6:21 PM, Michael Barton michael.bar...@asu.edu
wrote:
In r.to.vect, this argument ONLY refers to the output
Hi,
2014-11-29 18:20 GMT+01:00 Michael Barton michael.bar...@asu.edu:
I just ran into this last night.
The description for the type argument for r.to.vect calls it Input
feature type, but actually it should be Output feature type.
why do you think so? The option is used to filter out input
__
C. Michael Barton
Director, Center for Social Dynamics Complexity
Professor of Anthropology, School of Human Evolution Social Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University
Tempe, AZ 85287-2402
USA
voice: 480-965-6262
For r.to.vect, there are no input vector features. The only input is a raster.
It is the output that produces vector features.
Michael
__
C. Michael Barton
Director, Center for Social Dynamics Complexity
Professor of Anthropology, School of Human Evolution Social
2014-12-02 17:56 GMT+01:00 Michael Barton michael.bar...@asu.edu:
For r.to.vect, there are no input vector features. The only input is a raster.
It is the output that produces vector features.
sorry, I mistake the modules, fixed in r63332. Martin
--
Martin Landa
Hi,
2014-12-02 5:31 GMT+01:00 Anna Petrášová kratocha...@gmail.com:
Probably revert http://trac.osgeo.org/grass/changeset/59324? Or create
separate options G_OPT_V_TYPE_INPUT, G_OPT_V_TYPE_OUTPUT?
there are probably not so many modules which would need
G_OPT_V_TYPE_OUTPUT, right? Martin
I think there are quite a few modules that output vector files where the type
might vary.
Michael
__
C. Michael Barton
Director, Center for Social Dynamics Complexity
Professor of Anthropology, School of Human Evolution Social Change
Head, Graduate Faculty in
On Sat, Nov 29, 2014 at 6:20 PM, Michael Barton michael.bar...@asu.edu wrote:
I just ran into this last night.
The description for the “type” argument for r.to.vect calls it “Input
feature type”, but actually it should be “Output feature type”.
I'm not sure. The raster input defines also the
In r.to.vect, this argument ONLY refers to the output vector feature. There are
not any different feature types for the 2D raster maps that are input to this
module. I assume that while the nature of the raster map affects the vector
feature type to some extent, this argument can force it to
On Mon, Dec 1, 2014 at 6:21 PM, Michael Barton michael.bar...@asu.edu
wrote:
In r.to.vect, this argument ONLY refers to the output vector feature.
There are not any different feature types for the 2D raster maps that are
input to this module. I assume that while the nature of the raster map
On Dec 1, 2014, at 9:31 PM, Anna Petrášová
kratocha...@gmail.commailto:kratocha...@gmail.com wrote:
On Mon, Dec 1, 2014 at 6:21 PM, Michael Barton
michael.bar...@asu.edumailto:michael.bar...@asu.edu wrote:
In r.to.vect, this argument ONLY refers to the output vector feature. There are
not
I just ran into this last night.
The description for the “type” argument for r.to.vect calls it “Input feature
type”, but actually it should be “Output feature type”.
Michael
C. Michael Barton
Director, Center for Social Dynamics Complexity
Professor of Anthropology,
12 matches
Mail list logo
