Opened 10 years ago
Last modified 5 years ago
#2485 new enhancement
v.segment: add options for a fixed distance (enhacement)
| Reported by: | hellik | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | 7.6.2 |
| Component: | Vector | Version: | svn-releasebranch70 |
| Keywords: | v.segment | Cc: | |
| CPU: | Unspecified | Platform: | Unspecified |
Description
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.
Change History (16)
comment:1 by , 10 years ago
| Summary: | v.segment: add option for a fixed distance → v.segment: add option for a fixed distance (enhacement) |
|---|
comment:2 by , 10 years ago
| Keywords: | v.segment added |
|---|
follow-up: 6 comment:3 by , 10 years ago
| Summary: | v.segment: add option for a fixed distance (enhacement) → v.segment: add options for a fixed distance (enhacement) |
|---|
comment:4 by , 10 years ago
Replying to 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:5 by , 10 years ago
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:6 by , 9 years ago
Replying to hellik:
Replying to 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 #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.
comment:7 by , 8 years ago
| Milestone: | 7.0.0 → 7.0.5 |
|---|
comment:8 by , 8 years ago
| Milestone: | 7.0.5 → 7.3.0 |
|---|
comment:11 by , 7 years ago
comment:13 by , 6 years ago
| Milestone: | 7.4.1 → 7.4.2 |
|---|
comment:14 by , 6 years ago
| Milestone: | 7.4.2 → 7.6.0 |
|---|
All enhancement tickets should be assigned to 7.6 milestone.
Replying to hellik:
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.