Open landam opened 5 years ago
Modified by hellik on 7 Nov 2014 17:12 UTC
Modified by @landam on 7 Nov 2014 17:16 UTC
Comment by hellik on 7 Nov 2014 17:34 UTC Replying to [ticket:2485 hellik]:
v.segment - Creates points/segments from input vector lines and positions.
v.segment with an option for a fixed distance for points/segments (e.g. every 100m) would be nice.
the last segment may be shorter than the fixed distance.
to explain it a bit more: at the moment you can define points/segments by stdin input or a text file; that's nice.
the enhancement (two options: point or line, fixed distance) would be so that no stdin or a text file input is needed.
Comment by hellik on 8 Nov 2014 21:06 UTC Replying to [ticket:2485 hellik]:
v.segment - Creates points/segments from input vector lines and positions.
v.segment with an option for a fixed distance for points/segments (e.g. every 100m) would be nice.
the last segment may be shorter than the fixed distance.
as a workaround for points I've added a little addon:
http://trac.osgeo.org/grass/browser/grass-addons/grass7/vector/v.fixed.segmentpoints
Comment by pvanbosgeo on 9 Nov 2014 14:53 UTC Somebody must have read my mind.. I was just trying to figure out how to do this.v.to.points.
I only need points along straight lines, so using v.to.points (with use=vertex and dmax option set to a distance) seems to work too, although the results are slightly off from those created by the v.fixed.segmentpoints.
But +1 for me for adding this option to v.segment
Comment by mlennert on 11 Jun 2015 17:31 UTC Replying to [comment:3 hellik]:
Replying to [ticket:2485 hellik]:
v.segment - Creates points/segments from input vector lines and positions.
v.segment with an option for a fixed distance for points/segments (e.g. every 100m) would be nice.
the last segment may be shorter than the fixed distance.
to explain it a bit more: at the moment you can define points/segments by stdin input or a text file; that's nice.
the enhancement (two options: point or line, fixed distance) would be so that no stdin or a text file input is needed.
I just posted in https://trac.osgeo.org/grass/ticket/2231 a diff to v.split that implements a flag allowing to split lines according to a fixed distance. Combining this with v.to.points use=node should give you the points as well.
Modified by @landam on 12 May 2016 06:42 UTC
Modified by @landam on 25 Aug 2016 15:51 UTC
Comment by @landam on 27 Aug 2016 13:42 UTC Milestone renamed
Comment by @landam on 26 Jan 2018 08:47 UTC It's not clear what is status of this issue.
Comment by hellik on 26 Jan 2018 09:00 UTC Replying to [comment:10 martinl]:
It's not clear what is status of this issue.
never tried the v.split way mentioned in comment:6 if that's works.
v.segment enhancement as the original ticket is still open.
Comment by neteler on 26 Jan 2018 11:40 UTC Ticket retargeted after milestone closed
Modified by neteler on 12 Jun 2018 20:48 UTC
Comment by @landam on 25 Sep 2018 16:51 UTC All enhancement tickets should be assigned to 7.6 milestone.
Comment by @landam on 25 Jan 2019 21:07 UTC Ticket retargeted after milestone closed
Reported by hellik on 7 Nov 2014 17:09 UTC v.segment - Creates points/segments from input vector lines and positions.
v.segment with an option for a fixed distance for points/segments (e.g. every 100m) would be nice.
the last segment may be shorter than the fixed distance.
GRASS GIS version and provenance
svn-releasebranch70
Migrated-From: https://trac.osgeo.org/grass/ticket/2485