On 06/26/2013 07:00 PM, Pierre Roudier wrote:
Hi Benjamin,
As far as soils data, we would probably often mask with depths min or
max, use a plan to cut the profile collection to return points (give
the carbon value at 13.5cm depth for this collection of profiles).
Yes, however, please keep
Hi Benjamin,
As far as soils data, we would probably often mask with depths min or
max, use a plan to cut the profile collection to return points (give
the carbon value at 13.5cm depth for this collection of profiles).
Alternatively, we would try to interpolate a profile collection to
harmonise
Hi Ben,
All that I meant by mask is, in this case, an r3 map that defines a subset
of space that subsequent operations are constrained to. I guess I was just
expressing worry about creating runaway data demands.The region settings
act as a three dimensional bounding cube, does not seem adequate
On 06/25/2013 10:00 AM, Tim Bailey wrote:
Hi Ben,
All that I meant by mask is, in this case, an r3 map that defines a
subset of space that subsequent operations are constrained to. I guess I
was just expressing worry about creating runaway data demands.The region
settings act as a three
Hi Tim,
i am the second mentor in your SoC project, and will try to help you with
the 3D raster approach in GRASS.
The 3D raster implementation in GRASS is using a tiled based storage
approach.[1]
The tiles can be stored in compressed form (zlib in GRASS7) or uncompressed
form on the hard disk.
On 06/25/2013 10:21 AM, Sören Gebbert wrote:
Hi Tim,
i am the second mentor in your SoC project, and will try to help you
with the 3D raster approach in GRASS.
The 3D raster implementation in GRASS is using a tiled based storage
approach.[1]
The tiles can be stored in compressed form (zlib in
