I have two vector maps: one of a stream and its tributaries, the other of
project-specific points on or adjacent to that stream. I want to obtain the
stream length between two points.
In the GUI I load both layers: streams and proj_pts. I can also load the
attribute table for the streams (it contains only an id number and name),
but cannot select in the map those segments of interest.
I'm thinking that v.extract would be the way to go.
What is the most efficient way of calculating the distance between two
points on a stream network? I might have to specify the easting/northing of
each point or create a new map that places those points on the stream lines
themselves
I'm thinking that v.extract would be the way to go.
And the winner is (the envelop, please) ... d.path. It actually worked
more quickly from the terminal monitor because it hung while running in the
GUI.
And the winner is (the envelop, please) ... d.path.
It actually worked
more quickly from the terminal monitor because it hung
while running in the GUI.
- try updating svn to r41074
- tcltk module GUI: it seems to be hit or miss when the output buffer
will be flushed and you get to see the node+distance output. Maybe
it saves it all up until you exit.
- wx module GUI: no module output makes it to the Output tab of the module,
but if you know that left mouse button = set starting point; middle =
set end point, and right click = quit, the graphical part seems to work.
I've just added some on-screen help for that to d.path.sh in 6.5.
for some reason it does not bring up the UI for d.path.sh, but brings
one up for d.path. ?!
g.gisenv GRASS_GUI controls which flavour of module GUI you get, not
specifically if you are in gis.m or wxGUI.
actually via d.m is probably the most natural way to run this module.
(just add the vector lines layer to the display layer list first.
I downloaded and built whatever was available yesterday. Don't know the
build number.
- tcltk module GUI: it seems to be hit or miss when the output buffer
will be flushed and you get to see the node+distance output. Maybe
it saves it all up until you exit.
I was using wxPython widgets and GUI.
- wx module GUI: no module output makes it to the Output tab of the module,
but if you know that left mouse button = set starting point; middle =
set end point, and right click = quit, the graphical part seems to work.
I didn't know this until I ran the d.path module in the console monitor.