[GRASS-user] Shortest Distance v.net.path

2010-09-03 Thread jfk02
Hello, I am working with v.net.path in Grass 6.4.0RC7. I am attempting to get the shortest distance between a point and numerous other points along a network of streets. I have point A going to 112 different point Bs. I created a text file that looks like this and is loaded into GRASS as the file

[GRASS-user] d.mon and monitor frames

2010-09-03 Thread Damian M
I am experimenting with a very simple Python script that uses frames in a PNG monitor. Does d.barscale at=xy describe the xy from top-left in percent distance from the monitor or the frame? The verbiage in the documentation uses "frame," but I can't seem to make it behave the way I would expect

Re: [GRASS-user] Using GRASS with GPS

2010-09-03 Thread Markus Neteler
On Fri, Sep 3, 2010 at 8:37 PM, PixelPusher wrote: > I need to query a GPS that is attached to my computer (by USB or Bluetooth) > for my current location and then query a road network database to find the > road segments within some arbitrary distance. Does GRASS support that kind > of operation?

[GRASS-user] Using GRASS with GPS

2010-09-03 Thread PixelPusher
I have what I thought was going to be an easy problem, but it is of course more complicated than I'd expected. I need to query a GPS that is attached to my computer (by USB or Bluetooth) for my current location and then query a road network database to find the road segments within some arbitr

Re: [GRASS-user] Adding options to grass.run_command

2010-09-03 Thread Glynn Clements
Martin Landa wrote: > > but this doesn't: > > - > > grass.run_command("r.in.xyz", --overwrite, input=directory+'/'+file, > > output=rainraster, fs=',', x=2, y=1) > > neither does this: > > - > > grass.run_command("r.in.xyz --overwrite", input=directory+'/'+file, > > output=rainraster, fs=

Re: [GRASS-user] Adding options to grass.run_command

2010-09-03 Thread Hanlie Pretorius
Thanks :-) 2010/9/3, Martin Landa : > 2010/9/3 Hanlie Pretorius : >> grass.run_command("r.in.xyz", input=directory+'/'+file, >> output=rainraster, fs=',', x=2, y=1) > > better `input = os.path.join(directory, file)` > >> but this doesn't: >> - >> grass.run_command("r.in.xyz", --overwrite, inpu

Re: [GRASS-user] Adding options to grass.run_command

2010-09-03 Thread Martin Landa
2010/9/3 Hanlie Pretorius : > grass.run_command("r.in.xyz", input=directory+'/'+file, > output=rainraster, fs=',', x=2, y=1) better `input = os.path.join(directory, file)` > but this doesn't: > - > grass.run_command("r.in.xyz", --overwrite, input=directory+'/'+file, > output=rainraster, fs=',

[GRASS-user] Adding options to grass.run_command

2010-09-03 Thread Hanlie Pretorius
Hi, I'm writing my first GRASS Python script and am having trouble adding options to commands that I want to run. For example, the following works: - grass.run_command("r.in.xyz", input=directory+'/'+file, output=rainraster, fs=',', x=2, y=1) - but this doesn't: - grass.run_command("

[GRASS-user] Re: v.surf.rst does not get past 0% from cli, throws error from python gui but not tcltk

2010-09-03 Thread Eric Hardin
That was exactly the problem. Sorry for the bother. I was trying to import data in units of feet into a meters location. So, I guess there were about 3x as many rows and cols as should have had. Oh, it's so embarrassing to have problems with region, units, and masks. Thanks for answering though.

Re: [GRASS-user] Using addon: r.seg

2010-09-03 Thread Markus Neteler
For the record: On Sun, Jun 13, 2010 at 7:16 PM, Nikos Alexandris wrote: > >> katrin eggert wrote: >> > Last week someone mentioned at this mailing list the r.seg segmentation >> > from here: http://www.ing.unitn.it/~grass/) It is now in GRASS-Addons. >> > I have contacted the author but he did

Re: [GRASS-user] Best format for exporting raster data

2010-09-03 Thread Rainer M Krug
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/09/10 21:21, Glynn Clements wrote: > > Rainer M Krug wrote: > >>> But GRASS doesn't generally read data from files per se, but from >>> either the GRASS "database" or from GDAL (and the former might >>> eventually go away if we can get "native"