<html style="direction: ltr;">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<style type="text/css">body p { margin-bottom: 0cm; margin-top: 0pt; } </style>
</head>
<body bidimailui-charset-is-forced="true" style="direction: ltr;"
text="#000000" bgcolor="#FFFFFF">
<br>
<div class="moz-cite-prefix">On 15/03/2019 22:45, Martin Landa
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CA+Ei1OeO5fW-a9yhm+OM4ytujYm-tnZBWrGF8+ZHcBn2sTFDZQ@mail.gmail.com">
<pre class="moz-quote-pre" wrap="">Hi,
pá 15. 3. 2019 v 15:01 odesílatel Moritz Lennert
<a class="moz-txt-link-rfc2396E" href="mailto:mlennert@club.worldonline.be"><mlennert@club.worldonline.be></a> napsal:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">v.to.db with options start/end provides the coordinates of these points.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
thanks, I overlooked `v.to.db`. Anyway I would still need to hack
around since `v.to.db` does not create a new output vector map. So
it's still make sense to me to implement this functionality in
`v.to.points`.
Ma
</pre>
</blockquote>
<p>Whenever we get new Lidar data, I run a script to extract the
streamlines network, then obtain the upstream flow accumulation
area for both ends of each stream reach. The script uses a
combination of v.db.update to get the x,y coordinates of both ends
of each stream reach. Then these coordinates are extracted and
piped into v.in.ascii, creating a new points vector. Next I get
the upstream contributing area from the flow accumulation raster
(v.what.rast). Finally an sql expression is constructed for
db.execute to update the streams vector with upstream area for
each reach from the end points vector. </p>
<p><br>
</p>
<p>So, for me, an option in v.to.points to get the start and end
points would help to simplify this workflow.</p>
<p><br>
</p>
<p>Cheers, Micha<br>
</p>
<pre class="moz-signature" cols="72">--
Micha Silver
Ben Gurion Univ.
Sde Boker, Remote Sensing Lab
cell: +972-523-665918</pre>
</body>
</html>