Re: [GRASS-dev] [GRASS GIS] #2134: Create a general exit-safe interface to C libraries

#2134: Create a general exit-safe interface to C libraries --+- Reporter: wenzeslaus| Owner: grass-dev@… Type: enhancement | Status: new

Re: [GRASS-dev] [GRASS GIS] #2134: Create a general exit-safe interface to C libraries

#2134: Create a general exit-safe interface to C libraries --+- Reporter: wenzeslaus| Owner: grass-dev@… Type: enhancement | Status: new

Re: [GRASS-dev] [GRASS GIS] #2134: Create a general exit-safe interface to C libraries

#2134: Create a general exit-safe interface to C libraries --+- Reporter: wenzeslaus| Owner: grass-dev@… Type: enhancement | Status: new

[GRASS-dev] G7: r.what limited to 400 maps?

Hi, would be be possible to enable r.what to support more than 400 maps? I fail on multiannual daily time series data extraction. My brute-force attempt to change #define NFILES 400 to #define NFILES 4000 leads to GRASS 7.0.svn (latlong):~ > r.what map=`g.mlist rast pat="frac.*" sep=,` coord=12

[GRASS-dev] installing GRASS 7 on Ubuntu issue

Hi Hamish, The instructions you sent, and added to the WIKI, worked great for installing GRASS 7 on 2 Ubuntu boxes. But on the 3rd, it won't install the GUI. We've made sure that wxpython (2.8.12.1) and wxwidgets are installed, but when GRASS installs, it simply skips the GUI. I assume that it

Re: [GRASS-dev] where are the options listed for g.parser?

Thanks much Markus. This is a start. This is aimed at C programming, however, and only some of the keys and values transfer over to scripts. Following your link, I found additional info at: http://grass.osgeo.org/programming7/gis_8h_source.html#l00473 But again, this is aimed at creating interf

[GRASS-dev] [GRASS GIS] #2134: Create a general exit-safe interface to C libraries

#2134: Create a general exit-safe interface to C libraries --+- Reporter: wenzeslaus| Owner: grass-dev@… Type: enhancement | Status: new

Re: [GRASS-dev] where are the options listed for g.parser?

On Mon, Nov 18, 2013 at 10:15 AM, Maris Nartiss wrote: > Hello Michael, > recently there was a request about GUI prompting with hints to documentation: > http://lists.osgeo.org/pipermail/grass-dev/2013-November/066267.html > Right next to the gisprompt is also a pointer to standard options: > http

Re: [GRASS-dev] Implementation of the High Pass Filter Additive Fusion technique (i.fusion.hpf)

Nick Ves wrote: > The HPF algorithm about the histrogram matching states "Stretch the > new multispectral image to match the mean and standard deviation of > the original (input) multispectral image" > > In that context why it is wrong to do : > > Ouput <- output/sddev(output)*sddev(input) > >

Re: [GRASS-dev] where are the options listed for g.parser?

Michael Barton wrote: > The g.parser manual only gives a very limited set of examples for the > options available to g.parser for creating a script GUI. I agree. > Are these listed somewhere yet or are they still secret arcane knowledge? As a "noob", I had to go through other existing scripts t

Re: [GRASS-dev] where are the options listed for g.parser?

Hello Michael, recently there was a request about GUI prompting with hints to documentation: http://lists.osgeo.org/pipermail/grass-dev/2013-November/066267.html Right next to the gisprompt is also a pointer to standard options: http://grass.osgeo.org/programming7/parser__standard__options_8c.html