lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Smiley (JIRA)" <>
Subject [jira] [Updated] (LUCENE-4464) "Intersects" spatial query returns polygons it shouldn't
Date Tue, 16 Oct 2012 04:55:03 GMT


David Smiley updated LUCENE-4464:

    Attachment: LUCENE-4464_polygon_almost_touch_test.patch
                LUCENE-4464 google maps geohashes.png

I attached another screenshot of Google Earth with KML loaded for the 1st indexed polygon
and for the query shape.  It shows the lines almost touch but not quite -- showing ~28.4 meters
in-between.  The KML files were generated via the spatial-demo app, with 0.01 distErrPct.
 I was able to load the indexed polygon my adjusting the data near the self-intersection error.

I also attached a new test and I was not able to reproduce the problem you report, even with
the default 2.5% distErrPct.  I had to raise it to about 6% until I saw a false intersection.
 The fact that you see an intersection and I don't could very well be related to small improvements
in the interpretation of distErrPct / distErr / maxDistErr that were done a couple months

I'm going to commit this patch tomorrow.  It does an "assume" call to check if JTS is on the
classpath.  The test has no compile-time dependencies on JTS, just runtime.
> "Intersects" spatial query returns polygons it shouldn't
> --------------------------------------------------------
>                 Key: LUCENE-4464
>                 URL:
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: modules/spatial
>    Affects Versions: 3.6.1
>         Environment: linux and windows
>            Reporter: solr-user
>            Assignee: David Smiley
>            Priority: Critical
>              Labels: solr, spatial, spatialsearch
>         Attachments: LUCENE-4464 google maps geohashes.png, LUCENE-4464_polygon_almost_touch_test.patch,
LUCENE-4464 self intersect.png
> full description, including sample schema and data, can be found at

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message