[GRASSLIST:10160] Re: v.to.db option=query: issue with 2 layers and multiple categories

[Maciek Sieczka]

On Mon, 6 Feb 2006 09:09:58 +0100
Radim Blazek <radim.blazek at gmail.com> wrote:

> But you are doing still the same error. You have to use
> qcolumn=avg(elevation)

Then I don't understand what you mean. I'm not referring to case:

1. cat 1,2 at layer1 to cat 10 at layer2

but to

2. cat 1,2 at layer1 to cat 10,11 at layer2

I thought you meant that in the case 2 it wouldn't be necessary to use
qcolumn=avg() because the number of rows in both input and output are
equal in that case. Your words:

I wrote:
> > > > However, there are _also_ two categories for the same geometry
> > > > in layer 2 (10,11). I mean - I understand I couldn't upload 2
> > > > values into one "row". But since in this particular case in
> > > > both layer 1 and 2 there are two "rows", isn't it somehow
> > > > different? Just wondering.

Radim wrote:
> > > If it is not uploaded to both rows  in layer 2 (10,11) then it is
> > > a bug.

Sorry, maybe I didn't understand. Do you mean I should use something
like qcolumn=avg() even if number of cats (rows) for a given geometry in
output layer2 and input layer1 are equal?

Maciek

--------------------
W polskim Internecie s? setki milion?w stron. My przekazujemy Tobie tylko najlepsze z nich!
http://katalog.panoramainternetu.pl/