[geos-devel] Correct use of setPrecision
mtnclimb at gmail.com
Wed Sep 6 09:12:40 PDT 2017
That is correct - the precision model is not used in relate and spatial
predicate evaluation. (It's used in a few more places than the overlay
functions, but that is its primary usage)
It is feasible to introduce a precision model into the spatial predicate
computation, but not easily in the current implementation. I have plans
for a better implementation which will make it straightforward to use the
precision model. No timeline on that, however.
On Wed, Sep 6, 2017 at 6:03 AM, Daniel Baston <dbaston at gmail.com> wrote:
> My understanding is that precision models are considered only in the
> overlay options (and not in the geometry predicates).
> On Mon, Sep 4, 2017 at 5:13 AM, Nyall Dawson <nyall.dawson at gmail.com>
>> On 4 September 2017 at 17:29, Sandro Santilli <strk at kbt.io> wrote:
>> > On Mon, Sep 04, 2017 at 04:28:32PM +1000, Nyall Dawson wrote:
>> >> However, after looking into this in more depth I think the original
>> >> python code is incorrectly used. It's being used by QGIS in order to
>> >> set a "tolerance" on a spatial join operation - i.e. to consider that
>> >> two geometries which are 100m distant actually do intersect.
>> > [...]
>> >> If this is correct, is there any other way in GEOS to handle this
>> > How about using GEOSDistance ?
>> Thanks - that's a good option for intersects tests. I'm not sure
>> offhand if it would be translatable to the other geometry predicates,
>> but then I'd say trying to do a 'touches' or 'contains' test with a
>> tolerance would be quite an edge case anyway.
>> geos-devel mailing list
>> geos-devel at lists.osgeo.org
> geos-devel mailing list
> geos-devel at lists.osgeo.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the geos-devel