based on roadmap published in ML [1] we are close to RC1. There are no
blockers registered [2], so it is seems that we can slowly start
preparing RC1. Any objections?
On Mon, Mar 27, 2017 at 7:03 PM, Martin Landa <landa.martin@gmail.com> wrote:
Hi all,
based on roadmap published in ML [1] we are close to RC1. There are no
blockers registered [2], so it is seems that we can slowly start
preparing RC1. Any objections?
based on roadmap published in ML [1] we are close to RC1. There are no
blockers registered [2], so it is seems that we can slowly start
preparing RC1. Any objections?
On Mon, Mar 27, 2017 at 7:03 PM, Martin Landa <
landa.martin@
> wrote:
Hi all,
based on roadmap published in ML [1] we are close to RC1. There are no
blockers registered [2], so it is seems that we can slowly start
preparing RC1. Any objections?
2017-03-27 21:39 GMT+02:00 Helmut Kudrnovsky <hellik@web.de>:
G7A:v.clip - very easy to use and expected GIS functionality without hassle
of complicated commmands
tested v.clip quite a lot in the last weeks; very nice module with expected
GIS functionality
please note that v.clip has one known issue, it breaks lines on
intersections, see attached screenshots. In this case input line
should not be broken I would say. Ma
G7A:v.clip - very easy to use and expected GIS functionality without
hassle
of complicated commmands
tested v.clip quite a lot in the last weeks; very nice module with
expected
GIS functionality
please note that v.clip has one known issue, it breaks lines on
intersections, see attached screenshots. In this case input line
should not be broken I would say. Ma
Maybe enough (best) to handle it in the manual?
Meaning, add that information to the notes?
Users can avoid that lines/boundaries are broken by running v.dissolve in advance if needed?