search

landam / grass-gis-git-migration-test

0 stars 0 forks source link

r.profile: accept lines vector map as profile #80

Open landam opened 5 years ago

landam commented 5 years ago

Reported by dericke on 18 Jan 2013 07:55 UTC r.profile should directly accept a lines vector map and optional selection query. For each line feature returned, an elevation profile is created that runs along all vertices of the line.

This would be great for profiling a complex river or road without the intermediate step of converting vertices to ASCII before they can be used in r.profile. It would also aid in quickly profiling multiple transects.

GRASS GIS version and provenance

svn-trunk

Migrated-From: https://trac.osgeo.org/grass/ticket/1852

landam commented 5 years ago

Modified by dericke on 12 Feb 2013 07:14 UTC

landam commented 5 years ago

Comment by hamish on 12 Feb 2013 08:23 UTC Hi,

it seems like a reasonable idea, probably waits for someone to work on it.

note that for the ASCII work-around that v.out.ascii has an option to output to stdout and r.profile can take input from stdin, so with a little UNIX powertool magic (grep, awk, or sed) you could do it all in one step, maybe with a small wrapper script or alias.

see also the v.drape module which may do some of what you want.

Hamish

landam commented 5 years ago

Comment by neteler on 4 Mar 2013 07:54 UTC The function which could be added to r.profile is sample_raster(), see

http://trac.osgeo.org/grass/browser/grass/trunk/vector/v.drape/main.c#L29

landam commented 5 years ago

Comment by neteler on 10 Mar 2016 17:11 UTC Given the fact that nor v.split or v.to.points are helpful to generate reasonable input for r.profile, this enhancement is quite useful. At time I don't see how to extract nodes from a vector line at defined distance.

landam commented 5 years ago

Comment by hellik on 10 Mar 2016 17:47 UTC Replying to [comment:4 neteler]:

Given the fact that nor v.split or v.to.points are helpful to generate reasonable input for r.profile, this enhancement is quite useful. At time I don't see how to extract nodes from a vector line at defined distance.

maybe some inspiration?:

https://grass.osgeo.org/grass70/manuals/addons/v.fixed.segmentpoints.html https://grass.osgeo.org/grass70/manuals/addons/v.transects.html

landam commented 5 years ago

Comment by neteler on 29 Apr 2016 13:06 UTC An alternative could be to enhance the GRASS add-on v.profile (at time it allows to profile vector maps). Might be the "natural" place...

https://grass.osgeo.org/grass70/manuals/addons/v.profile.html

landam commented 5 years ago

Comment by neteler on 5 May 2016 14:08 UTC Milestone renamed

landam commented 5 years ago

Comment by neteler on 28 Dec 2016 15:04 UTC Ticket retargeted after milestone closed

landam commented 5 years ago

Modified by @landam on 5 May 2017 20:40 UTC

landam commented 5 years ago

Comment by @landam on 1 Sep 2017 20:28 UTC All enhancement tickets should be assigned to 7.4 milestone.

landam commented 5 years ago

Comment by neteler on 26 Jan 2018 11:40 UTC Ticket retargeted after milestone closed

landam commented 5 years ago

Modified by neteler on 12 Jun 2018 20:48 UTC

landam commented 5 years ago

Comment by @landam on 25 Sep 2018 16:51 UTC All enhancement tickets should be assigned to 7.6 milestone.

landam commented 5 years ago

Comment by @landam on 25 Jan 2019 21:07 UTC Ticket retargeted after milestone closed