Thu, Aug 25 2005
14:40:31
|
|
Request created by guest
|
|
Subject: v.db.select - don't force all the input columns to the output datable
Platform: GNU/Linux/i386
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: cvs 23.08.05
Please let me choose whether I want all the input columns to be present in the
output datatable or only those selected by me.
Below I'm trying to omit importing the x and y columns to output datatable (I
want to use them only for coordinates). But this is recognized as an "error".
v.db.select -c map=wejscie column=cat,rast_val,x,y | v.in.ascii output=grd_faults_pt_nocat_addcat_as
c
columns='CAT integer, WYS double' x=3 y=4 cat=1
Maximum input row length: 44
Maximum number of columns: 4
Minimum number of columns: 4
column: 1 type: integer
column: 2 type: double
column: 3 type: double
column: 4 type: double
ERROR: Number of columns defined (2) does not match number of columns (4)
in input.
Maciek |
|
Thu, Aug 25 2005
16:29:50
|
|
Area changed to grass6.1 by msieczka
|
|
Fri, Aug 26 2005
12:14:05
|
|
Mail sent by neteler@itc.it
|
|
Return-Path |
<neteler@itc.it>
|
Delivered-To |
grass-bugs@lists.intevation.de
|
Date |
Fri, 26 Aug 2005 12:14:01 +0200
|
From |
Markus Neteler <neteler@itc.it>
|
To |
Request Tracker <grass-bugs@intevation.de>
|
Cc |
grass5@grass.itc.it
|
Subject |
Re: [GRASS5] [bug #3573] (grass) v.db.select - don't force all the input columns to the output datable
|
Message-ID |
<20050826101401.GH16084@thuille.itc.it>
|
Mail-Followup-To |
Request Tracker <grass-bugs@intevation.de>, grass5@grass.itc.it
|
References |
<20050825124031.E2879102BC0@lists.intevation.de>
|
Mime-Version |
1.0
|
Content-Type |
text/plain; charset=us-ascii
|
Content-Disposition |
inline
|
In-Reply-To |
<20050825124031.E2879102BC0@lists.intevation.de>
|
User-Agent |
Mutt/1.4.1i
|
X-PGP-Key |
http://www.gdf-hannover.de/neteler/markus_gpgkey.asc
|
X-Spam-Status |
No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
|
X-Spam-Level |
|
On Thu, Aug 25, 2005 at 02:40:31PM +0200, Request Tracker wrote:
> this bug's URL: http://intevation.de/rt/webrt?serial_num=3573
> -------------------------------------------------------------------------
>
> Subject: v.db.select - don't force all the input columns to the output datable
>
> Platform: GNU/Linux/i386
> grass obtained from: CVS
> grass binary for platform: Compiled from Sources
> GRASS Version: cvs 23.08.05
>
> Please let me choose whether I want all the input columns to be present in
the output datatable or only those selected by me.
>
> Below I'm trying to omit importing the x and y columns to output datatable
(I want to use them only for coordinates). But this is recognized as an "error".
>
> v.db.select -c map=wejscie column=cat,rast_val,x,y | v.in.ascii output=grd_faults_pt_nocat_addcat_
asc
columns='CAT integer, WYS double' x=3 y=4 cat=1
>
> Maximum input row length: 44
> Maximum number of columns: 4
> Minimum number of columns: 4
> column: 1 type: integer
> column: 2 type: double
> column: 3 type: double
> column: 4 type: double
> ERROR: Number of columns defined (2) does not match number of columns (4)
> in input.
>
> Maciek
>
> -------------------------------------------- Managed by Request Tracker
>
Maciek,
you could put a
| cut -d'<delimiter>' -f<field>[,<field>] in between.
Markus
|
|
Sat, Aug 27 2005
22:07:08
|
|
Subject changed to v.in.ascii: don't force all the input columns to the output datable by msieczka
|
|
Sat, Aug 27 2005
22:07:52
|
|
Mail sent by werchowyna@epf.pl
|
|
Return-Path |
<werchowyna@epf.pl>
|
Delivered-To |
grass-bugs@lists.intevation.de
|
Message-ID |
<01da01c5ab42$d9999740$a0e41d3e@eustahiush>
|
From |
"Maciek Sieczka" <werchowyna@epf.pl>
|
To |
"Markus Neteler via RT" <grass-bugs@intevation.de>
|
Cc |
"Markus Neteler" <neteler@itc.it>
|
References |
<20050826101405.344F4101FA3@lists.intevation.de>
|
Subject |
Re: [bug #3573] (grass) v.db.select - don't force all the input columns to the output datable
|
Date |
Sat, 27 Aug 2005 21:56:31 +0200
|
MIME-Version |
1.0
|
Content-Type |
text/plain; format=flowed; charset="iso-8859-2"; reply-type=original
|
Content-Transfer-Encoding |
7bit
|
X-Priority |
3
|
X-MSMail-Priority |
Normal
|
X-Mailer |
Microsoft Outlook Express 6.00.2900.2180
|
X-MimeOLE |
Produced By Microsoft MimeOLE V6.00.2900.2180
|
X-Antivirus |
avast! (VPS 0528-4, 2005-07-14), Outbound message
|
X-Antivirus-Status |
Clean
|
X-Spam-Status |
No, hits=-4.9 tagged_above=-999.0 required=3.0 tests=BAYES_00
|
X-Spam-Level |
|
From: "Markus Neteler via RT"
> you could put a
>
> | cut -d'<delimiter>' -f<field>[,<field>] in between.
Thanks Markus, I'll try it next time. But I wouldn't be me if I didn't
complain - could this workaround be put *temporarily* in the manual until
v.in.ascii is fixed to support selecting columns?
(this bug report should refer to v.in.ascii not v.db.select, my mistake, I'm
changing it)
|
|
Wed, Aug 31 2005
20:57:36
|
|
Area changed to grass6 by mneteler
|
|
Thu, Sep 1 2005
02:03:30
|
|
Mail sent by dcalvelo
|
|
Another option (that might be mentioned in *some* man page; which one?) is to
use db.copy with the select= option.
So, where to mention this? The wiki, in a tips section?
Daniel. |
|
Thu, Sep 1 2005
02:33:22
|
|
Status changed to resolved by dcalvelo
|
|
Thu, Sep 1 2005
02:34:00
|
|
Status changed to open by dcalvelo
|
|
Thu, Sep 1 2005
02:35:56
|
|
Comments added by dcalvelo
|
|
I've added a paragraph in the docs explaining the 'cut' trick.
Can we change the area to "wish6"?
Daniel. |
|
Mon, Sep 5 2005
05:20:59
|
|
Area changed to wish6 by dcalvelo
|
|
Wed, Jul 26 2006
14:45:14
|
|
User changed to tutey@o2.pl by msieczka
|
|