Details Ticket 4459


Comment | Reply | Take | Open


Serial Number 4459
Subject v.report: coor not reported, issues with layer=2
Area grass6
Queue grass
Requestors tutey@o2.pl
Owner none
Status resolved
Last User Contact Tue Feb 20 22:25:01 2007 (2 yr ago)
Current Priority 30
Final Priority 70
Due No date assigned
Last Action Tue Feb 20 22:25:01 2007 (2 yr ago)
Created Mon May 15 23:00:20 2006 (2 yr ago)

Transaction History Ticket 4459


Mon, May 15 2006 23:00:20    Request created by guest  
Subject: v.report: coor not reported, issues with layer=2

Platform: GNU/Linux/x86
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: 2006-05-07

I've got a points vector file with 2 layers.

   See the layer=1 colums:

$ v.info -c points layer=1
Displaying column types/names for database connection of layer 1:
INTEGER|oldcat
DOUBLE PRECISION|CAT
CHARACTER|NAZWA
CHARACTER|KOMENT
DOUBLE PRECISION|NUMBER
DOUBLE PRECISION|NEXT
DOUBLE PRECISION|odwr

   And the layer=2 colums:

$ v.info -c points layer=2
Displaying column types/names for database connection of layer 2:
INTEGER|cat
INTEGER|lcat
DOUBLE PRECISION|along
DOUBLE PRECISION|x
DOUBLE PRECISION|y
DOUBLE PRECISION|z

Now, when I request coordinates of points in layer 1, v.report doesn't print
them, only the datatable content:

$ v.report map=points layer=1 option=coor units=meters
Displaying column types/names for database connection of layer 1:
oldcat|CAT|NAZWA|KOMENT|NUMBER|NEXT|odwr|x|y
1|1.000000|||2.000000|3.000000|0.000000|

<snip>

And, when I request coordinates of points in layer 2, v.report says it reports
layer 1 (sic!), and only a _corrupted_ datatable content of layer 2 is printed
instead of coordinates:

$ v.report map=points layer=2 option=coor units=meters
Displaying column types/names for database connection of layer 1:
oldcat|CAT|NAZWA|KOMENT|NUMBER|NEXT|odwr|x|y
1|1|0.000000|600488.642402|5677976.919601|98.650734|1|600488.642401556|5677976.91960139|0
<snip>

Maciek
Tue, May 16 2006 08:27:21    Mail sent by msieczka  
Hi,

I'm forwarding this report manally as it didn't make it to the dev list when
the ticket was created.



Subject: v.report: coor not reported, issues with layer=2

Platform: GNU/Linux/x86
grass obtained from: CVS
grass binary for platform: Compiled from Sources
GRASS Version: 2006-05-07

I've got a points vector file with 2 layers.

   See the layer=1 colums:

$ v.info -c points layer=1
Displaying column types/names for database connection of layer 1:
INTEGER|oldcat
DOUBLE PRECISION|CAT
CHARACTER|NAZWA
CHARACTER|KOMENT
DOUBLE PRECISION|NUMBER
DOUBLE PRECISION|NEXT
DOUBLE PRECISION|odwr

   And the layer=2 colums:

$ v.info -c points layer=2
Displaying column types/names for database connection of layer 2:
INTEGER|cat
INTEGER|lcat
DOUBLE PRECISION|along
DOUBLE PRECISION|x
DOUBLE PRECISION|y
DOUBLE PRECISION|z

Now, when I request coordinates of points in layer 1, v.report doesn't print
them, only the datatable content:

$ v.report map=points layer=1 option=coor units=meters
Displaying column types/names for database connection of layer 1:
oldcat|CAT|NAZWA|KOMENT|NUMBER|NEXT|odwr|x|y
1|1.000000|||2.000000|3.000000|0.000000|

<snip>

And, when I request coordinates of points in layer 2, v.report says it reports
layer 1 (sic!), and only a _corrupted_ datatable content of layer 2 is printed
instead of coordinates:

$ v.report map=points layer=2 option=coor units=meters
Displaying column types/names for database connection of layer 1:
oldcat|CAT|NAZWA|KOMENT|NUMBER|NEXT|odwr|x|y
1|1|0.000000|600488.642402|5677976.919601|98.650734|1|600488.642401556|5677976.91960139|0
<snip>

Maciek
Tue, May 23 2006 00:15:09    Mail sent by mneteler  
Hi,

v.report is just a script - should be easy to adapt and fix!

Markus
Wed, Jul 26 2006 18:34:41    User changed to tutey@o2.pl by msieczka  
Tue, Feb 20 2007 22:25:01    Status changed to resolved by msieczka  
Tue, Feb 20 2007 22:25:01    Mail sent by msieczka  
Fixed in CVS by Markus.

Maciek
Comment | Reply | Take | Open

You are currently authenticated as guest.
[Show Configuration] [Login as another user]

Users Guide - Mail Commands - Homepage of RequestTracker 1.0.7 - list any request