Re: [GRASS-dev] [GRASS GIS] #3685: pygrass GridModule: ERROR: Unable to open element file

2018-10-19 Thread GRASS GIS
#3685: pygrass GridModule: ERROR: Unable to open element file --+- Reporter: mlennert | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.6.0 Component: PyGRASS |

Re: [GRASS-dev] quickest way to test whether a raster contains any non-null values in the current computational region ?

2018-10-19 Thread Markus Metz
On Fri, Oct 19, 2018 at 4:04 PM Moritz Lennert wrote: > > On 19/10/18 15:48, Michel Wortmann wrote: > > Hi Moritz, > > How about this: > > > > info = grass.parse_command('r.univar', map='raster_xyz', flags='g') > > print(int(info['n']), int(info['null_cells'])) > > Thanks ! > > Yes, this is one

Re: [GRASS-dev] Python scripts in GRASS GIS: conditional loading of external libraries?

2018-10-19 Thread Ondřej Pešek
Hi, pá 19. 10. 2018 v 17:18 odesílatel Martin Landa napsal: > pá 19. 10. 2018 v 16:45 odesílatel Markus Neteler > napsal: > > we are currently writing a Python script which needs to import some > > heavy external libraries. > > if I understand well, a lazy import could help > > """ > def main:

[GRASS-dev] Fwd: [Proj] finding proj descriptions

2018-10-19 Thread Markus Neteler
Anyone here willing to support? Would be great! - Forwarded message - From: Howard Butler Date: Fr., 19. Okt. 2018, 20:48 Subject: Re: [Proj] finding proj descriptions To: On 10/17/18 11:17 AM, Andre Joost wrote: > Am 17.10.18 um 17:12 schrieb MacQueen, Don: > Most changes in

Re: [GRASS-dev] Python scripts in GRASS GIS: conditional loading of external libraries?

2018-10-19 Thread Vaclav Petras
On Fri, Oct 19, 2018 at 12:23 PM Nikos Alexandris wrote: > > * Markus Neteler [2018-10-19 16:45:29 +0200]: > ... > >Now: could the import of the external library (it takes in the range > >of > 2min) be conditionalized to only be read at the second "run"? > > > >I was searching in the g.parser

Re: [GRASS-dev] Python scripts in GRASS GIS: conditional loading of external libraries?

2018-10-19 Thread Nikos Alexandris
* Markus Neteler [2018-10-19 16:45:29 +0200]: Hi, we are currently writing a Python script which needs to import some heavy external libraries. AFAIK the script is read twice, once by the Python interpreter, then when having reached the grass.parser() line again in order to re-read properly

Re: [GRASS-dev] quickest way to test whether a raster contains any non-null values in the current computational region ?

2018-10-19 Thread Eric Patton
On Fri, Oct 19, 2018 at 11:04 AM, Moritz Lennert wrote: > On 19/10/18 15:48, Michel Wortmann wrote: >> Hi Moritz, >> How about this: >> >> info = grass.parse_command('r.univar', map='raster_xyz', flags='g') >> print(int(info['n']), int(info['null_cells'])) > > Thanks ! > > Yes, this is one

Re: [GRASS-dev] OSGeo4W-winGRASS - for anyone working?

2018-10-19 Thread Veronica Andreo
Thanks a million, @Martin!!! :) El vie., 19 oct. 2018 a las 17:11, Helmut Kudrnovsky () escribió: > >good news: newly upload 64bit grass package (grass-7.4.1-3) is fixed > > confirmed, grass-7.4.1-3 64bit is up again! thanks! > > > > - > best regards > Helmut > -- > Sent from:

Re: [GRASS-dev] Python scripts in GRASS GIS: conditional loading of external libraries?

2018-10-19 Thread Martin Landa
Hi, pá 19. 10. 2018 v 16:45 odesílatel Markus Neteler napsal: > we are currently writing a Python script which needs to import some > heavy external libraries. if I understand well, a lazy import could help """ def main: from mylib import xyz ... return 0 if __name__ ==

Re: [GRASS-dev] OSGeo4W-winGRASS - for anyone working?

2018-10-19 Thread Helmut Kudrnovsky
>good news: newly upload 64bit grass package (grass-7.4.1-3) is fixed confirmed, grass-7.4.1-3 64bit is up again! thanks! - best regards Helmut -- Sent from: http://osgeo-org.1560.x6.nabble.com/Grass-Dev-f3991897.html ___ grass-dev mailing list

Re: [GRASS-dev] [GRASS GIS] #3230: lib/raster/gdal.c – missing libgdal.20.dylib in the GDAL library names list

2018-10-19 Thread GRASS GIS
#3230: lib/raster/gdal.c – missing libgdal.20.dylib in the GDAL library names list --+- Reporter: vince| Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.4.2

Re: [GRASS-dev] quickest way to test whether a raster contains any non-null values in the current computational region ?

2018-10-19 Thread Markus Neteler
On Fri, Oct 19, 2018 at 4:04 PM Moritz Lennert wrote: > On 19/10/18 15:48, Michel Wortmann wrote: > > Hi Moritz, > > How about this: > > > > info = grass.parse_command('r.univar', map='raster_xyz', flags='g') > > print(int(info['n']), int(info['null_cells'])) > > Thanks ! > > Yes, this is one

[GRASS-dev] Python scripts in GRASS GIS: conditional loading of external libraries?

2018-10-19 Thread Markus Neteler
Hi, we are currently writing a Python script which needs to import some heavy external libraries. AFAIK the script is read twice, once by the Python interpreter, then when having reached the grass.parser() line again in order to re-read properly the #% options ... etc. statements. Now: could the

Re: [GRASS-dev] quickest way to test whether a raster contains any non-null values in the current computational region ?

2018-10-19 Thread Moritz Lennert
On 19/10/18 15:48, Michel Wortmann wrote: Hi Moritz, How about this: info = grass.parse_command('r.univar', map='raster_xyz', flags='g') print(int(info['n']), int(info['null_cells'])) Thanks ! Yes, this is one option. I was wondering if there was any faster option than actually having to

Re: [GRASS-dev] [GRASS GIS] #3685: pygrass GridModule: ERROR: Unable to open element file

2018-10-19 Thread GRASS GIS
#3685: pygrass GridModule: ERROR: Unable to open element file --+- Reporter: mlennert | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.6.0 Component: PyGRASS |

Re: [GRASS-dev] quickest way to test whether a raster contains any non-null values in the current computational region ?

2018-10-19 Thread Michel Wortmann
Hi Moritz, How about this: info = grass.parse_command('r.univar', map='raster_xyz', flags='g') print(int(info['n']), int(info['null_cells'])) Michel > On 19 Oct 2018, at 15:36, Moritz Lennert wrote: > > Hi all, > > What would be the quickest way to test whether a raster contains any

[GRASS-dev] quickest way to test whether a raster contains any non-null values in the current computational region ?

2018-10-19 Thread Moritz Lennert
Hi all, What would be the quickest way to test whether a raster contains any non-null values in the current computational region ? And the correlary: what would be the quickest way to test whether a raster contains any null values in the current computational region ? This will be applied

Re: [GRASS-dev] [GRASS GIS] #3685: pygrass GridModule: ERROR: Unable to open element file

2018-10-19 Thread GRASS GIS
#3685: pygrass GridModule: ERROR: Unable to open element file --+- Reporter: mlennert | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.6.0 Component: PyGRASS |

[GRASS-dev] help needed with #3685

2018-10-19 Thread Moritz Lennert
Hi everyone, As this is quite urgent in the context of my work, I would love some help on this issue. Does anyone have any hint as to where I should start looking about this ? Moritz Forwarded Message Subject: [GRASS-dev] [GRASS GIS] #3685: pygrass GridModule: ERROR:

Re: [GRASS-dev] OSGeo4W-winGRASS - for anyone working?

2018-10-19 Thread Martin Landa
Hi, pá 19. 10. 2018 v 10:31 odesílatel Martin Landa napsal: > I hopefully found it. GRASS is still linked to proj4 (proj.dll) and > and not proj5 (proj_5_2.dll). Rebuild triggered. Fingers crossed. Ma good news: newly upload 64bit grass package (grass-7.4.1-3) is fixed (GRASS GUI starts, raster

[GRASS-dev] [GRASS GIS] #3685: pygrass GridModule: ERROR: Unable to open element file

2018-10-19 Thread GRASS GIS
#3685: pygrass GridModule: ERROR: Unable to open element file -+- Reporter: mlennert | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 7.6.0 Component: PyGRASS |Version:

Re: [GRASS-dev] OSGeo4W-winGRASS - for anyone working?

2018-10-19 Thread Nikos Alexandris
* Martin Landa [2018-10-19 10:31:01 +0200]: Hi, pá 19. 10. 2018 v 10:14 odesílatel Martin Landa napsal: bad news, with new build the problem remains. Ma I hopefully found it. GRASS is still linked to proj4 (proj.dll) and and not proj5 (proj_5_2.dll). Rebuild triggered. Fingers crossed. Ma

Re: [GRASS-dev] OSGeo4W-winGRASS - for anyone working?

2018-10-19 Thread Martin Landa
Hi, pá 19. 10. 2018 v 10:14 odesílatel Martin Landa napsal: > bad news, with new build the problem remains. Ma I hopefully found it. GRASS is still linked to proj4 (proj.dll) and and not proj5 (proj_5_2.dll). Rebuild triggered. Fingers crossed. Ma -- Martin Landa

Re: [GRASS-dev] OSGeo4W-winGRASS - for anyone working?

2018-10-19 Thread Martin Landa
Hi, čt 18. 10. 2018 v 22:15 odesílatel Martin Landa napsal: > issue confirmed. grass-7.4.1 package rebuild triggred. I hope it will > help. Will see tomorrow morning. Ma bad news, with new build the problem remains. Ma -- Martin Landa http://geo.fsv.cvut.cz/gwiki/Landa