On Tue, Nov 20, 2018 at 7:59 PM Micha Silver wrote:
>
>
> On 11/19/18 12:41 PM, Markus Neteler wrote:
> > On Sun, Nov 18, 2018 at 10:32 PM Micha Silver wrote:
> >> I am preparing a correlation matrix for 7 raster layers. The results
using the r.covar module are different from the R layerStats
Retested on two small regions, one with some null cells and one
with no null cells, using both the GRASS r.covar module and the R
layerStats function, and this time results were almost identical.
In addition, r.covar outputs "N" the number of cells used, and I
On 11/19/18 12:41 PM, Markus Neteler wrote:
On Sun, Nov 18, 2018 at 10:32 PM Micha Silver wrote:
I am preparing a correlation matrix for 7 raster layers. The results using the
r.covar module are different from the R layerStats function. I suspect this is
due to handling of null cells. The R
Hi,
I would like to export a 3D raster done with V.VOL.RST to view it in
paraview.
With r3.out.vtk, i am using the DEM as the upper layer and another bottom
layer. I created a RGB raster map based on the DEM, same raster for 3
colors.
any ideas why this is not working?
(Tue Nov 20 22:03:53
Dear all,
In an r.mapcalc expression, I would like to trace values along a direction map
for 1 to n steps (e.g. looking 4 steps ahead along a path or stream or along a
given direction (degrees or 45degrees).
I tried using the neighborhood modifier within an eval function in r.mapcalc.
Hi GRASS list,
I'm seeking some advice about how to determine the eventual edge-cell
destination of every pixel in a DEM. I have an algorithm that works on rasters
up to 0.5 billion pixels but am now trying to do it on a region about 8x as
large and it is failing.
I've spent a week exploring
On Tue, Nov 20, 2018 at 9:50 AM Ken Mankoff wrote:
>
> Hi GRASS list,
>
> I'm seeking some advice about how to determine the eventual edge-cell
destination of every pixel in a DEM. I have an algorithm that works on
rasters up to 0.5 billion pixels but am now trying to do it on a region
about 8x
On 2018-11-19 at 08:26 +0100, Ken Mankoff wrote:
> Attached is a graphic showing the elevation input and direction
> output.
>
> If you look near the burgundy square in the elevation at the 4.0 value
> to the NW, *everything* near that cell should flow into it (all
> neighbors are >4.0).
Hi Markus,
On 2018-11-20 at 09:56 +0100, Markus Metz wrote:
> On Tue, Nov 20, 2018 at 9:50 AM Ken Mankoff wrote:
> What has worked for the 0.5 B pixel region is running r.watershed and
> then for every negative pixel, I run r.water.outlet and find the upstream
> contributors. But I can't run
