[GRASS-dev] small interface inconsistency in r.to.vect in GRASS 7
Michael Barton
Michael.Barton at asu.edu
Tue Dec 2 08:56:16 PST 2014
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 Change
Head, Graduate Faculty in Complex Adaptive Systems Science
Arizona State University
Tempe, AZ 85287-2402
USA
voice: 480-965-6262 (SHESC), 480-965-8130/727-9746 (CSDC)
fax: 480-965-7671(SHESC), 480-727-0709 (CSDC)
www: http://csdc.asu.edu, http://shesc.asu.edu
http://www.public.asu.edu/~cmbarton
On Dec 2, 2014, at 6:48 AM, Martin Landa <landa.martin at gmail.com> wrote:
> Hi,
>
> 2014-11-29 18:20 GMT+01:00 Michael Barton <Michael.Barton at 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 vector
> features. Martin
>
> --
> Martin Landa
> http://geo.fsv.cvut.cz/gwiki/Landa
> http://gismentors.eu/mentors/landa
More information about the grass-dev
mailing list