Hi all,
I wanted to start writing small python scripts for grass. Unfortunatelly I
fail to set the environment variables right. I'm struggeling since hours to
get them right. I found topics about environment variable in linux and
windows, but nothing for mac:
'db.execute input=-' for stdin only works in grass7. for 6.4+6.5 it is
simpler, just omit the input option all together.
Hi,
What do you mean with omit the input?
Like this?
grass.write_command('db.execute', stdin = sql_coi_percent)
--
View this message in context:
tried the make command:
make MODULE_TOPDIR=/Applications/GRASS-6.4.app/Contents/MacOS/
As a result I get the an error:
make: *** Makefile: Is a directory. Stop.
Does someone know what this could mean and what I'm doing wrong?
Tusend tack,
schorschli
--
View this message in context:
http://n2
Thanks for answering.
Are you sure about this directory?
MODULE_TOPDIR should point to the GRASS installation directory which
contains bin/, lib/ and other GRASS stuff.
Yes, the directory is the one containing the grass-folders (bin/, lib/ and
others).
I could solve this problem. It was not
only a single problematic path (e.g 18 102 7) is working
fine.
Does anyone of you know, what could cause this strange behaviour? How does
the order of the nodes influence the algorithm?
Greetings Schorschli
--
View this message in context:
http://n2.nabble.com/v-net-path-algorithm-problem
Hi,
Thanks for your suggestions.
Perhaps some nodes are missing? I have success in the past by applying
http://grass.osgeo.org/grass64/manuals/html64_user/v.net.html
I tried v.net -- report and indeed some nodes where missing. I added those
with v.net --nodes. Running v.net.path can still
Hi Sophie,
v.out.ascii format=standard might help.
Here is the manual:
http://grass.itc.it/grass64/manuals/html64_user/v.out.ascii.html
Afterwards you can write a simple script to extract the coordinates from the
ascii-output.
schorschli
--
View this message in context:
http://osgeo-org
William Kyngesburye wrote:
If you're using my GRASS build...,
Yes I'm using your GRASS build
William Kyngesburye wrote:
Does the wxpython GUI run in GRASS? (I'm guessing no)
The GRASS wxpython GUI is running.
William Kyngesburye wrote:
Are you doing something with the
I updated to version GRASS 6.4rc6. But now I cannot start grass anymore...
File /Applications/GRASS-6.4.app/Contents/MacOS/etc/wxpython/wxgui.py,
line 1819, in module
sys.exit(main())
File /Applications/GRASS-6.4.app/Contents/MacOS/etc/wxpython/wxgui.py,
line 1812, in main
app =
Now the
import wx
command works but the grass wxgui not anymore...
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/import-wx-tp5301729p5315627.html
Sent from the Grass - Users mailing list archive at Nabble.com.
___
For your task the use of lists and the split tool may help.
The different lines have are seperated by a '\n' (which is interpreted as a
new line). After splitting the string into a line list you can make a loop
each item of this list. Something like this:
tried to reinstalled GRASS (using the newest installer from
http://www.kyngchaos.com/software/grass)
Any idea what could be wrong and how to fix this?
Thanks,
Schorschli
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/GRASS-starting-problem-Mac-tp5506724p5506724.html
Sent
Problem fixed by reinstalling the system.
I had the correct GRASS package.
Thanks
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/GRASS-starting-problem-Mac-tp5506724p5514762.html
Sent from the Grass - Users mailing list archive at Nabble.com.
13 matches
Mail list logo