#1454 closed enhancement (fixed)
v.outlier manual page does not refer that the vector needs to be a 3D one
Reported by: | lutra | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | 6.4.2 |
Component: | Docs | Version: | 6.4.1 |
Keywords: | v.outlier | Cc: | |
CPU: | Unspecified | Platform: | Unspecified |
Description
Summary says it all
Change History (7)
follow-up: 2 comment:1 by , 13 years ago
follow-up: 5 comment:3 by , 13 years ago
So v.outlier
should complain if input is 2D vector data, right?
comment:4 by , 13 years ago
Keywords: | v.outlier added |
---|---|
Milestone: | → 6.4.2 |
follow-up: 6 comment:5 by , 13 years ago
Replying to martinl:
So
v.outlier
should complain if input is 2D vector data, right?
yes,
https://trac.osgeo.org/grass/browser/grass/trunk/vector/v.outlier/main.c#L377
Vect_is_3d() seems to be the test to use..
Hamish
follow-up: 7 comment:6 by , 13 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
Replying to hamish:
Replying to martinl:
So
v.outlier
should complain if input is 2D vector data, right?yes,
...
Vect_is_3d() seems to be the test to use..
You mean the test which *is* used:
/* Input vector must be 3D */ if (!Vect_is_3d(&In)) G_fatal_error(_("Input vector map <%s> is not 3D!"), in_opt->answer);
Manual fixed, closing.
comment:7 by , 13 years ago
Note:
See TracTickets
for help on using tickets.
I would suggest this modification:
Makes sense?