Yann wrote:
I am importing a large amount of ascii files as 3D vectors,
some of them have null values (currently set to an arbitrary
high constant value)
Is there a filter for v.in.ascii to set null values,
and/or in v.surf.* to avoid using those points with
specific values?
I typically
Does this mean that v.in.ascii recognizes 9.99 as a grass vector null value?
If I use 9.99 in v.surf.* will it be discarded from the interpolation?
On 16 May 2013 11:44, Hamish hamis...@yahoo.com wrote:
Yann wrote:
I am importing a large amount of ascii files as 3D vectors,
some of
Yann:
Does this mean that v.in.ascii recognizes 9.99 as a grass
vector null value?
If I use 9.99 in v.surf.* will it be discarded from the
interpolation?
Nope, the 'grep -v' means that entire row of data is excluded
from the datastream and never sent to v.in.ascii in the first
Thanks Hamish,
thinking in vector mode is different than in raster mode...
Yann
On 16 May 2013 12:45, Hamish hamis...@yahoo.com wrote:
Yann:
Does this mean that v.in.ascii recognizes 9.99 as a grass
vector null value?
If I use 9.99 in v.surf.* will it be discarded from the
On Thu, May 16, 2013 at 9:15 AM, Hamish hamis...@yahoo.com wrote:
Yann:
Does this mean that v.in.ascii recognizes 9.99 as a grass
vector null value?
If I use 9.99 in v.surf.* will it be discarded from the
interpolation?
Nope, the 'grep -v' means that entire row of data is excluded
Hi,
I am importing a large amount of ascii files as 3D vectors, some of
them have null values (currently set to an arbitrary high constant
value)
Is there a filter for v.in.ascii to set null values,
and/or
in v.surf.* to avoid using those points with specific values?
Yann
--
Yann Chemin
