[GRASS-dev] Re: GRASS 7: d.vect: layer=-1 default conflicts with
where option
Markus Neteler
neteler at osgeo.org
Sun Sep 4 04:29:19 EDT 2011
On Sun, Sep 4, 2011 at 10:13 AM, Markus Neteler <neteler at osgeo.org> wrote:
> Hi,
>
> I found that d.vect fails on commandline
>
> d.vect mylakes where="FTYPE IS NULL" type=area col=red
> ERROR: Option <layer> must be > 0
>
> d.vect mylakes where="FTYPE IS NULL" type=area col=red layer=1
> d.vect complete.
>
> The reason is
> layer Layer number or name ('-1' for all layers)
The same applies to v.dissolve (and maybe others) on command line:
layer Layer number or name. If -1, all layers are extracted.
A single vector map can be connected to multiple database
tables. This number determines which table to use. Layer name for
direct OGR access.
default: -1
v.dissolve mysoils_general output=mysoils_general_families column=GSL_NAME
ERROR: Database connection not defined for layer <-1>
ERROR: Column <GSL_NAME> not found
Stating layer=1 manually on command line would be very annoying of course...
Markus
More information about the grass-dev
mailing list