On Thu, Feb 23, 2012 at 6:50 PM, Glynn Clements
gl...@gclements.plus.com wrote:
Markus Neteler wrote:
The existing implementation has been reverted last year, but how to
do that now? I have to find out at which DOY in a pixel a certain value
has been reached. Input are all single daily GDD
#1588: v.out.dxf of 3d-polyline is not complete
-+--
Reporter: khermann | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone:
Markus Neteler wrote:
Also, you might consider changing the c_thresh() method to be more
generally useful; I can't imagine that the current implementation
would be of use for anything other than the exact case for which it
was originally written; e.g. it won't help with your second
On Fri, Feb 24, 2012 at 11:54 AM, Glynn Clements
gl...@gclements.plus.com wrote:
...
Thanks for the suggestions, will study them.
So e.g. 10,000 maps with 1000 columns would require an extra 200MB;
10,000 maps with 10,000 columns would require an extra 2GB.
We have 19,000 x 22,000 pixels
#1589: r.clump: inadequate color ramp
-+--
Reporter: pcav | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone:
#1589: r.clump: inadequate color ramp
-+--
Reporter: pcav | Owner: grass-dev@…
Type: defect | Status: new
In the wxGUI, save display to graphic file is not working in
wingrass and should not work in linux, because SaveToFile uses
wx.BufferedPaintDC() which is in this case illegal because it can only
be used inside of an EVT_PAINT event handler [0], and SaveToFile is
not an EVT_PAINT event handler,
Hi all,
After some time I've decided to start testing latest devel versions of
GRASS on Ubuntu again. I have just today successfully compiled this week's
SVN snapshot on Ubuntu 11.04 64-bit with the following configuration
options: CFLAGS=-g -Wall ./configure --with-cxx --with-freetype=yes
Actually, now that I am thinking about it, this may be related to an
ongoing NVIZ problem that I have had since moving to Ubuntu 11.03.
Essentially, what happens is that NVIZ only *sort of* works in that I can
get it to load up and display a map, but as soon as i touch any of the
controls with the
I've just learned that typing g.region [return] from the terminal does not
launch the g.region GUI. Typing it from the wxPython command console does
launch the GUI. Other commands typed from the terminal (followed by return with
no arguments) launch their GUIs.
This is happening in GRASS 7 and
#1590: new vector map crashing GUI in 6.4.3 svn
-+--
Reporter: cmbarton | Owner: grass-dev@…
Type: defect | Status: new
Priority: normal | Milestone:
Michael wrote:
I've just learned that typing g.region [return] from the terminal
does not launch the g.region GUI.
worksforme, what happens for you? do you get an error message?
how about g.region --ui ?
what does g.gisenv get=GRASS_GUI say?
what about echo $? directly after running g.region
On Feb 24, 2012, at 4:21 PM, Hamish wrote:
Michael wrote:
I've just learned that typing g.region [return] from the terminal
does not launch the g.region GUI.
worksforme, what happens for you? do you get an error message?
Nothing. No error message. Nothing happens
how about g.region
#1591: misc. spelling errors in documentation
--+-
Reporter: hamish| Owner: grass-dev@…
Type: defect| Status: new
Priority: minor |
14 matches
Mail list logo
