Changes between Initial Version and Version 1 of Ticket #2734, comment 2
- Timestamp:
- 03/25/16 06:22:28 (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2734, comment 2
initial v1 1 1 In r66459 I have added `Vect_point_in_box_2d()` function which is simply a 2D version of `Vect_point_in_box()` function which is 3D only. Alternative would be to add one function which would optionally consider ''z''. 2 2 3 Using `Vect_point_in_box_2d()` and existing `with_z` logic I have tried to fix this ticket and [https://lists.osgeo.org/pipermail/grass-user/2015-July/072809.html reported issue] in r66460 in ''v.d ecimate''. The test written for ''v.decimate'' would suggest that the change helped.3 Using `Vect_point_in_box_2d()` and existing `with_z` logic I have tried to fix this ticket and [https://lists.osgeo.org/pipermail/grass-user/2015-July/072809.html reported issue] in r66460 in ''v.distance''. The test written for ''v.distance'' would suggest that the change helped. 4 4 5 5 `Vect_point_in_box()` function is used a lot in the modules and very often with hardcoded `0.0` as ''z'' parameter (and there might be also cases when ''z'' is optionally zero). These should be replaced by the new function or its universal alternative.