how/where do you set the variable? it needs to be set before
GRASS begins.
I have set the GRASS_ADDON_PATH variable in my ~/.bashrc, like this
export GRASS_ADDON_PATH=/home/ricardo/gisProjectos/grassAddons
in the gnome menu entry prefs do you have start in terminal ticked?
Yep, it
Hello list
I compiled grass-6.4.0RC5 (downloaded a tarball from the main site).
I'd like to learn about scripting grass with python.
Following the first sample script at the GRASS Python scripting
library (http://download.osgeo.org/grass/grass6_progman/pythonlib.html)
I created a test file
Hi,
2009/6/30 Ricardo Filipe Soares Garcia da ricardo.garcia.si...@gmail.com:
Following the first sample script at the GRASS Python scripting
library (http://download.osgeo.org/grass/grass6_progman/pythonlib.html)
I created a test file called teste.py, and placed it on the Desktop.
When I try
Thanks for your help
Now I'll get on with the program!
Hopefully I'll be able to build a script that can find the nearest
hospital to an accident site on a vector network working ;)
Cheers
On Tue, Jun 30, 2009 at 2:51 PM, Martin Landalanda.mar...@gmail.com wrote:
Hi,
2009/6/30 Ricardo
On 30/06/09 12:58, Ricardo Filipe Soares Garcia da wrote:
Hello list
I compiled grass-6.4.0RC5 (downloaded a tarball from the main site).
I'd like to learn about scripting grass with python.
Following the first sample script at the GRASS Python scripting
library
On Jun 30, 2009, at 7:10 AM, grass-user-requ...@lists.osgeo.org wrote:
Date: Tue, 30 Jun 2009 15:58:01 +0200
From: Moritz Lennert mlenn...@club.worldonline.be
Subject: Re: [GRASS-user] grass 6.4 rc5 and python scripting
To: Ricardo Filipe Soares Garcia da ricardo.garcia.si...@gmail.com
Cc
Glynn Clements wrote:
In order for g.parser to work, the file teste.py needs to be in your
PATH.
This is actually a bug in G_parser() and G_gui(). menuform.py is being
passed the base filename rather than the complete path. There isn't
any other reason why the script needs to be in the
Michael Barton wrote:
3. Set the GRASS_ADDON_PATH variable in the .grassrc6 file
(or its equivalent in GRASS 7). For example, I could add...
GRASS_ADDON_PATH: /Users/Michael/Desktop;/Users/Michael/Documents
...and any script on my desktop or in my documents folder
would be accessible to
It really does work. It's pretty nice. I don't know how .grassrc6
handles separators--GRASS specific or OS specific.
Michael
__
C. Michael Barton, Professor of Anthropology
Director of Graduate Studies, School of Human Evolution Social Change
Director, Center for
Hello all
Thanks for your good advice. I decided to go with the option of
EXPORTing the grass addon path and put my scripts there, which works
ok, well... kind of.
It happens that when I launch GRASS from the terminal, the
GRASS_ADDON_PATH gets correctly added to the PATH and I can load my
test
Ricardo Filipe Soares Garcia da wrote:
Thanks for your good advice. I decided to go with the
option of EXPORTing the grass addon path and put my scripts
there, which works ok, well... kind of.
It happens that when I launch GRASS from the terminal, the
GRASS_ADDON_PATH gets correctly added
11 matches
Mail list logo
