Dear Nikos,
Can you give us a bit more context?
What is it you want to achieve? How are you using r.stats and what is it you
want to do with the output?
Personally, I am not too familiar with performance implications of NumPy vs.
plain Python, but rather use NumPy for convenience in matrix/tabl
* Nikos Alexandris [2018-08-21 12:55:49 +0200]:
* Moritz Lennert [2018-08-21 09:53:21 +0200]:
On 21/08/18 01:50, Nikos Alexandris wrote:
* Nikos Alexandris [2018-08-20 20:11:57 +0200]:
2) Look back some time, r.cross has had problems with zeroes and NULLs.
At least this one is True!, se
#3627: i.group: file= parameter for input desired
-+-
Reporter: neteler | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.6.0
Component: Imagery |Version: 7.4.0
Keywords
* Stefan Blumentrath [2018-08-23 07:23:12 +]:
Dear Nikos,
Can you give us a bit more context? What is it you want to achieve?
How are you using r.stats and what is it you want to do with the
output?
Personally, I am not too familiar with performance implications of
NumPy vs. plain Python
#2631: Future winGRASS needs python-ply package
-+-
Reporter: wenzeslaus | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.2.4
Component: Temporal|Ver
On 23/08/18 11:52, Nikos Alexandris wrote:
* Stefan Blumentrath [2018-08-23 07:23:12 +]:
Dear Nikos,
Can you give us a bit more context? What is it you want to achieve?
How are you using r.stats and what is it you want to do with the
output?
Personally, I am not too familiar with perfor
* Moritz Lennert [2018-08-23 13:02:03 +0200]:
On 23/08/18 11:52, Nikos Alexandris wrote:
* Stefan Blumentrath [2018-08-23 07:23:12 +]:
Dear Nikos,
Can you give us a bit more context? What is it you want to achieve?
How are you using r.stats and what is it you want to do with the
outpu
Hi Marcus,
I am not too familiar with C and the like so I might confuse some things here...
I noticed that using .buffer() in PyGRASS gives a lot of "using native format"
output.
So I looked it up and it seems to be using native buffering (Vect_area_buffer2):
https://trac.osgeo.org/grass/browse
On Thu, Aug 16, 2018 at 5:12 PM Markus Neteler wrote:
>
> On Mon, Aug 6, 2018 at 12:46 AM Vaclav Petras wrote:
> > I have created a page for 2017 based on the two slides from AGM 2017:
> > https://trac.osgeo.org/grass/wiki/AnnualReport/2017
> >
> > The page for 2018 is here (please, contribute):
#3564: Inconsistent results from qsort callback in g.mkfontcap
--+
Reporter: yugr | Owner: grass-dev@…
Type: defect | Status: closed
Priority: normal | Milestone: 7.4.2
Component: Default |Version: 7.4.0
Resol
On Thu, Aug 23, 2018 at 1:39 PM Stefan Blumentrath <
stefan.blumentr...@nina.no> wrote:
>
> Hi Marcus,
>
> I am not too familiar with C and the like so I might confuse some things
here...
>
> I noticed that using .buffer() in PyGRASS gives a lot of "using native
format" output.
this "using native
#3628: PyGRASS: Use GEOS buffering
-+-
Reporter: sbl | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone: 7.4.2
Component: PyGRASS |Version: svn-trunk
Keywords: buffer |CPU: All
Thanks for the explanation.
Ticket created…
From: Markus Metz
Sent: torsdag 23. august 2018 17:20
To: Stefan Blumentrath
Cc: GRASS developers list
Subject: Re: [GRASS-dev] [GRASS GIS] #3448: v.buffer native failures
On Thu, Aug 23, 2018 at 1:39 PM Stefan Blumentrath
mailto:stefan.blumentr..
#831: v.category options sum, del, and add do nothing
--+--
Reporter: isaacullah | Owner: martinl
Type: enhancement | Status: new
Priority: major| Milestone: 7.4.2
Component: Vector |Version: svn-d
#3627: i.group: file= parameter for input desired
--+-
Reporter: neteler | Owner: grass-dev@…
Type: enhancement | Status: new
Priority: normal | Milestone: 7.6.0
Component: Imagery |Version: 7.4.0
Reso
Dear all,
I just uploaded a new addon "v.rast.bufferstats" [1] that extracts different
raster statistics in multiple buffers around vector geometries.
It is looping over input geometries and thus not very performant with lots of
input geometries. But it can be convenient for e.g. characterizing
On Thu, Aug 23, 2018 at 5:40 AM Nikos Alexandris
wrote:
>
> Is there an elegant alternative?
As for your script design/coding approach:
You were concerned about nice history at one point. You can wrap it, not
just in a plain script, but in a module. Then you can hide any particulars
of the imple
#3537: Add functionalities –tmp-location and –no-clean
-+--
Reporter: radeknovotny94 | Owner: grass-dev@…
Type: enhancement | Status: closed
Priority: normal | Milestone: 7.6.0
Component: S
#3537: Add functionalities –tmp-location and –no-clean
-+--
Reporter: radeknovotny94 | Owner: grass-dev@…
Type: enhancement | Status: closed
Priority: normal | Milestone: 7.6.0
Component: S
19 matches
Mail list logo
