[GRASS-dev] [GRASS GIS] #3361: v.select: very slow using GEOS operators
GRASS GIS
trac at osgeo.org
Fri May 25 07:47:17 PDT 2018
#3361: v.select: very slow using GEOS operators
--------------------------+---------------------------------------
Reporter: mlennert | Owner: grass-dev@…
Type: enhancement | Status: closed
Priority: normal | Milestone: 7.6.0
Component: Vector | Version: svn-trunk
Resolution: fixed | Keywords: v.select GEOS within slow
CPU: Unspecified | Platform: Unspecified
--------------------------+---------------------------------------
Comment (by mlennert):
Replying to [comment:5 mmetz]:
> Replying to [comment:4 mmetz]:
> > In [changeset:"72705" 72705]:
> > {{{
> > #!CommitTicketReference repository="" revision="72705"
> > v.select: re-organize code to select features from vector map A by
features from other vector map B (fixes #3361)
> > }}}
>
> Assuming that the result will be a subset of map A, selected by features
from map B, the code re-organization results in a substantial speed-up.
v.select is now nearly as fast as the alternative in the description.
>
> The results of `operator=overlap` and the GEOS-equivalent
`operator=intersects` are identical, but the speed difference based on the
example in the description
>
> {{{
> v.select ain=boundary_municp bin=rail5000 out=select
op=overlap/intersects
> }}}
>
> is astonishing, as of trunk r72705.
As reported on the [http://lists.osgeo.org/pipermail/grass-
user/2018-May/078255.html grass-users list], working with r72716, I
actually get different results depending on whether I use intersects or
overlap, when working with atype=areas and btype=lines. Don't know if this
result is expected. I can provide the data privately if useful.
--
Ticket URL: <https://trac.osgeo.org/grass/ticket/3361#comment:7>
GRASS GIS <https://grass.osgeo.org>
More information about the grass-dev
mailing list