[GRASS-dev] [bug #4459] (grass) v.report: coor not reported, issues with layer=2

[Request Tracker]

this bug's URL: http://intevation.de/rt/webrt?serial_num=4459
-------------------------------------------------------------------------

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


-------------------------------------------- Managed by Request Tracker