[Switching from grass-user to grass-dev.]
On Mon, May 1, 2017 at 5:11 PM, Markus Metz
wrote:
> > > Is it different from the binning code in r.in.xyz ?
> >
> >
> > Not really. r.in.lidar was based on r.in.xyz, now they are different
> but of course the idea is to
#3344: r.stream.slope Segmentation fault: 11 error macOS 10.12.4
--+--
Reporter: msweier | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.2.1
Component:
#3344: r.stream.slope Segmentation fault: 11 error macOS 10.12.4
--+--
Reporter: msweier | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.2.1
Component:
#3344: r.stream.slope Segmentation fault: 11 error macOS 10.12.4
--+-
Reporter: msweier | Owner: grass-dev@…
Type: defect| Status: new
Priority: normal
On Mon, May 1, 2017 at 11:17 AM, Markus Neteler wrote:
>
> On Sun, Apr 30, 2017 at 10:39 PM, Markus Metz
> wrote:
> ...
> > 16+GB of RAM still seems too much to me, unless the histograms of the
cell
> > values are highly skewed. What is the
#3340: wxGUI: encoding error when saving a workspace with vector that has
accents
in legend_label
--+
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal |
#3275: wxGUI: encoding error when saving workspace
--+--
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.2.2
Component: wxGUI|
#3340: wxGUI: encoding error when saving a workspace with vector that has
accents
in legend_label
--+
Reporter: mlennert | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal |
On Sun, Apr 30, 2017 at 10:39 PM, Markus Metz
wrote:
...
> 16+GB of RAM still seems too much to me, unless the histograms of the cell
> values are highly skewed. What is the output of r.stats -c for B04_255,
> B11_255, B8A_255?
Since this comes from our automated