Hi,
I was wondering if anyone is using Load/Save expressions in r.mapcalc GUI.
I just added there the copy button which is standard for all modules. When
I need, I store multiple r.mapcalc commands in a text file and then I just
copy and paste. Loading and saving expressions using the buttons seem
Hi Paul,
On Tue, Mar 25, 2014 at 4:14 PM, Paul Shapley wrote:
> Hi,
>
> I use the 'v.extrude' module often but cannot understand why the resulting
> 3D geometries criss-cross on the tops and sometimes the sides of the
> extrusions.
Are the data really like that (could you extract just a single
b
On Fri, Mar 28, 2014 at 1:03 PM, Thomas Adams wrote:
> All;
>
> I'm trying to create a water depth map using the following:
>
> (1) DEM
> (2) vector polygon indicating the lateral extent of inundation
> (3) stream channel centerline
>
> I figure I can intersect the polygon with the DEM raster to g
On Sat, 29 Mar 2014, Rich Shepard wrote:
Will now try -7.0.
Same problem: wxGTK needed in addition to wxPython. Built error-free and
installed.
Rich
--
Richard B. Shepard, Ph.D. | Have knowledge, will travel.
Applied Ecosystem Services, Inc. |
www.appl-ecosys.com Voice
Rich,
glad you solved it.
Let's put a note to the Wiki page about 'Compile and Installation'...
Best
Markus
___
grass-user mailing list
grass-user@lists.osgeo.org
http://lists.osgeo.org/mailman/listinfo/grass-user
On Sat, 29 Mar 2014, Markus Neteler wrote:
Could it be included in
http://repository.slacky.eu/slackware-14.1/libraries/wxGTK/2.8.12/
Markus, et al.:
Thanks for the pointer to the problem: I _thought_ I read somewhere that
wxGTK was included in wxPython and that both could not be installed
On Fri, 28 Mar 2014, Anna Petrášová wrote:
could you just try importing wxpython in python console outside of grass
session:
import wxversion
import wx
to make sure it's working? (Sorry if you already did that)
Anna,
Sure:
In [1]: import wxversion
In [2]: import wx
In [3]:
No erro
On Fri, Mar 28, 2014 at 6:49 PM, Rich Shepard wrote:
> On Fri, 28 Mar 2014, Vaclav Petras wrote:
>
>> wxversion is a usually a separate package. The reason is that it access
>> all the other versions.
...
> failing to build, probably because there's no wxversion here.
>
>> Which system are you usi
