Opened 8 years ago

Last modified 18 months ago

#1852 new enhancement

r.profile: accept lines vector map as profile

Reported by: dericke Owned by: grass-dev@…
Priority: normal Milestone: 7.6.2
Component: Raster Version: svn-trunk
Keywords: r.profile, elevation Cc:
CPU: All Platform: All

Description

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.

Change History (15)

comment:1 Changed 8 years ago by dericke

CPU: UnspecifiedAll
Platform: UnspecifiedAll
Version: unspecifiedsvn-trunk

comment:2 Changed 8 years ago by hamish

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

comment:3 Changed 8 years ago by neteler

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

comment:4 Changed 5 years ago by neteler

Milestone: 7.0.07.1.0

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.

comment:5 in reply to:  4 Changed 5 years ago by hellik

Replying to 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

comment:6 Changed 4 years ago by neteler

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

comment:7 Changed 4 years ago by neteler

Milestone: 7.1.07.2.0

Milestone renamed

comment:8 Changed 4 years ago by neteler

Milestone: 7.2.07.2.1

Ticket retargeted after milestone closed

comment:9 Changed 3 years ago by martinl

Milestone: 7.2.17.2.2

comment:10 Changed 3 years ago by martinl

Milestone: 7.2.27.4.0

All enhancement tickets should be assigned to 7.4 milestone.

comment:11 Changed 3 years ago by neteler

Milestone: 7.4.07.4.1

Ticket retargeted after milestone closed

comment:12 Changed 2 years ago by neteler

Milestone: 7.4.17.4.2

comment:13 Changed 2 years ago by martinl

Milestone: 7.4.27.6.0

All enhancement tickets should be assigned to 7.6 milestone.

comment:14 Changed 20 months ago by martinl

Milestone: 7.6.07.6.1

Ticket retargeted after milestone closed

comment:15 Changed 18 months ago by martinl

Milestone: 7.6.17.6.2

Ticket retargeted after milestone closed

Note: See TracTickets for help on using tickets.