[GRASS-dev] Re: [GRASS GIS] #1088: r.fillnulls: support other interpolation methods

2012-02-15 Thread GRASS GIS
#1088: r.fillnulls: support other interpolation methods -+-- Reporter: kyngchaos| Owner: grass-dev@… Type: enhancement | Status: new Priority: normal |

[GRASS-dev] errors in GRASS 7 svn compiling

2012-02-15 Thread Michael Barton
I just compiled GRASS 7 svn (r50820). I had the following errors: Errors in: /Users/Shared/grass_dev/grass70_dev/temporal/tv.what.rast /Users/Shared/grass_dev/grass70_dev/temporal/tv.observe.rast /Users/Shared/grass_dev/grass70_dev/gui/wxpython The first two seem to be from listings in the

Re: [GRASS-dev] GRASS and Paraview

2012-02-15 Thread Michael Barton
Soren, If I get bold enough to try this, do I need to have source trees of both GRASS and VTK? And if so, do I need to have VTK compiled? I'm using a binary of Paraview but don't have VTK independent of that (AFAIK). Also, do I need to put this anywhere in particular or will make install do it

[GRASS-dev] success with NetCDF

2012-02-15 Thread Michael Barton
I was able to directly import our test NetCDF file into GRASS using r.in.gdal. The trick is to properly specify the file and data subset name. Here is the command version, though I did it through the GUI too. r.in.gdal -o -e

Re: [GRASS-dev] GRASS and Paraview

2012-02-15 Thread Sören Gebbert
Hi Michael, 2012/2/15 Michael Barton michael.bar...@asu.edu: Soren, If I get bold enough to try this, do I need to have source trees of both GRASS and VTK? And if so, do I need to have VTK compiled? I'm using a binary of Paraview but don't have VTK independent of that (AFAIK). I did not

Re: [GRASS-dev] GRASS Web site: compilation errors for G7

2012-02-15 Thread Hamish
Markus Neteler wrote: * man: Indeed, also in my local compilation I don't have a man/ directory, to be removed from the tar command? Glynn: The manual pagers were moved from $GISBASE/man to $GISBASE/docs/man in r49908. Ok, main Makefile updated. Hi, sorry for the trouble, but I've just

[GRASS-dev] [GRASS GIS] #1577: r.stream.extract/r.stream.order - calculated mainchannel vs. real mainchannel

2012-02-15 Thread GRASS GIS
#1577: r.stream.extract/r.stream.order - calculated mainchannel vs. real mainchannel -+-- Reporter: hellik | Owner: grass-dev@… Type: enhancement | Status: new

Re: [GRASS-dev] [GRASS GIS] #1577: r.stream.extract/r.stream.order - calculated mainchannel vs. real mainchannel

2012-02-15 Thread Jarek Jasiewicz
On 02/15/2012 03:33 PM, GRASS GIS wrote: #1577: r.stream.extract/r.stream.order - calculated mainchannel vs. real mainchannel -+-- Reporter: hellik | Owner: grass-dev@… Type: enhancement |

[GRASS-dev] Re: [GRASS GIS] #1577: r.stream.extract/r.stream.order - calculated mainchannel vs. real mainchannel

2012-02-15 Thread Helmut Kudrnovsky
what does it means? Any reference? Main channel established in real network or algorithms of modeling main channel? the mentionned real mainchannel is the part of real Austrian river network (i.e. listed in the annual Austrian hydrographical handbook as the river 'Isel') an example screenshot of

Re: [GRASS-dev] how to deal with a python keyword as a module option name?

2012-02-15 Thread Glynn Clements
Hamish wrote: r.resamp.bspline uses 'lambda' as a command line parameter name, but when you try to use it with grass.run_command() you get an error as lambda is a python reserved keyword. How to work around that? Prepend an underscore to the name, i.e.:

[GRASS-dev] Re: [GRASS GIS] #1577: r.stream.extract/r.stream.order - calculated mainchannel vs. real mainchannel

2012-02-15 Thread Helmut Kudrnovsky
the mentionned real mainchannel is the part of real Austrian river network (i.e. listed in the annual Austrian hydrographical handbook as the river 'Isel') or may have also a look in the pdf mentioned in http://wisa.lebensministerium.at/article/archive/29373 Helmut - best regards Helmut

Re: [GRASS-dev] Re: [GRASS GIS] #1577: r.stream.extract/r.stream.order - calculated mainchannel vs. real mainchannel

2012-02-15 Thread Jarek Jasiewicz
On 02/15/2012 04:46 PM, Helmut Kudrnovsky wrote: what does it means? Any reference? Main channel established in real network or algorithms of modeling main channel? the mentionned real mainchannel is the part of real Austrian river network (i.e. listed in the annual Austrian hydrographical

Re: [GRASS-dev] Re: [GRASS GIS] #1577: r.stream.extract/r.stream.order - calculated mainchannel vs. real mainchannel

2012-02-15 Thread Markus Metz
On Wed, Feb 15, 2012 at 10:46 PM, Helmut Kudrnovsky hel...@web.de wrote: what does it means? Any reference? Main channel established in real network or algorithms of modeling main channel? the mentionned real mainchannel is the part of real Austrian river network (i.e. listed in the annual

Re: [GRASS-dev] GRASS Web site: compilation errors for G7

2012-02-15 Thread Markus Neteler
On Wed, Feb 15, 2012 at 8:42 PM, Hamish hamis...@yahoo.com wrote: Markus Neteler wrote: * man: Indeed, also in my local compilation I don't have a man/ directory, to be removed from the tar command? Glynn: The manual pagers were moved from $GISBASE/man to $GISBASE/docs/man in r49908. Ok,

Re: [GRASS-dev] GRASS Web site: compilation errors for G7

2012-02-15 Thread Glynn Clements
Hamish wrote: sorry for the trouble, but I've just discovered that the man pages need to go back into $GISBASE because of the way that `manpath` works. it searches $PATH and for each path dir, if ../man/ exists it is added to the manpath search list. Adding a symlink back there works, but

[GRASS-dev] Re: [GRASS GIS] #1576: r.in.poly broken by window split

2012-02-15 Thread GRASS GIS
#1576: r.in.poly broken by window split +--- Reporter: hamish | Owner: grass-dev@… Type: defect | Status: new

[GRASS-dev] [GRASS GIS] #1578: grass user map is 404

2012-02-15 Thread GRASS GIS
#1578: grass user map is 404 -+-- Reporter: hamish | Owner: grass-dev@… Type: defect | Status: new Priority: major

[GRASS-dev] Re: [GRASS GIS] #1534: vector_db_select fails with kwargs

2012-02-15 Thread GRASS GIS
#1534: vector_db_select fails with kwargs -+-- Reporter: artegion | Owner: grass-dev@… Type: defect | Status: new Priority: critical | Milestone: