> I think how it currently works, doesn't make sense for the reverse case,
> please create a ticket. The column should be created in the new vector.
>
Done: https://trac.osgeo.org/grass/ticket/2774
Thanks!
Pedro
___
grass-user mailing list
G. Allegri wrote:
> > This isn't about the if() function. The bitand() function (to which
> > the error message refers) corresponds to the bitwise-and operator "&".
> >
> > The if() function accepts either integer or floating-point values for
> > its arguments.
>
> That's what disappointed my
Moritz Lennert wrote:
> >> Doing a logical operation with a DCELL raster within an if(x,a) statement
> >> produces an error: "Incorrect argument types to function bitand()".
> >
> > First, you're confusing bitwise operators and logical operators. & and
> > | are bitwise operators, while && and
On Wed, Oct 21, 2015 at 4:15 AM, Pedro Venâncio
wrote:
> Hi Anna,
>
>
>
> Will this be backported to 7.0.x?
>>
>> I believe I backported it, 7.0.2 RC1 release is just going on now, there
>> will be an announcement soon.
>>
>>
> Thanks, I will check!
>
>
>
>
>>>
>>>
Hi Anna,
Will this be backported to 7.0.x?
>
> I believe I backported it, 7.0.2 RC1 release is just going on now, there
> will be an announcement soon.
>
>
Thanks, I will check!
>>
>> Then I wanted to transform the z-coordinate to
>>>
an attribute column using
v.to.3d -r
Dylan
A small sidenote on your issue. I also use GNU parallel for operations
that have to run on very large scales. Never had problems with it when
running it on different mapsets, i.e. I create a temporary mapset in my
scripts that are wrapped by the command. Storing the data back to a