[
https://issues.apache.org/jira/browse/LUCENE-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15315984#comment-15315984
]
Karl Wright commented on LUCENE-7316:
-------------------------------------
Here's the problem.
The shape in question involves two polygons. One polygon has the following
points:
{code}
final GeoPoint p1 = new GeoPoint(PlanetModel.WGS84, 0.0425265613312593,
0.0);
final GeoPoint p4 = new GeoPoint(PlanetModel.WGS84, 0.0,
-1.7156310907312492E-12);
final GeoPoint p5 = new GeoPoint(PlanetModel.WGS84, -0.7766317703682181,
3.141592653589793);
{code}
That polygon has two planes that are in fact coplanar:
{code}
[junit4] 1> Recording XYZBounds for plane [A=1.7156310907312492E-12,
B=1.0, C=-4.031825447240733E-11, D=0.0, side=1.0]
[junit4] 1> a >= minimum_resolution
[junit4] 1> Recording XYZBounds for plane [A=1.7156310907312492E-12,
B=1.0, C=-1.7458530603341764E-12, D=0.0, side=1.0]
[junit4] 1> a >= minimum_resolution
[junit4] 1> Recording XYZBounds for plane [A=5.543375111216114E-18,
B=-1.0, C=-1.3027230013345064E-16, D=0.0, side=1.0]
[junit4] 1> a >= minimum_resolution
{code}
Therefore, the ability to correctly detect point membership for this part of
the polygon is not going to work, so the points it says are within the polygon
in fact may not be within it.
The issue, then, is how we were allowed to construct such a polygon in the
first place. Looking at GeoPolygonFactory next...
> Geo3d test failure
> ------------------
>
> Key: LUCENE-7316
> URL: https://issues.apache.org/jira/browse/LUCENE-7316
> Project: Lucene - Core
> Issue Type: Bug
> Components: modules/spatial3d
> Affects Versions: master (7.0)
> Reporter: Karl Wright
> Assignee: Karl Wright
> Attachments: LUCENE-7316.patch
>
>
> Reproducible on master with:
> {code}
> ant test -Dtestcase=TestGeo3DPoint -Dtests.method=testGeo3DRelations
> -Dtests.seed=EEA08DD7FAE3C688 -Dtests.multiplier=2 -Dtests.slow=true
> -Dtests.directory=MMapDirectory -Dtests.locale=es
> -Dtests.timezone=America/Manaus -Dtests.asserts=true
> -Dtests.file.encoding=UTF-8
> {code}
> Note: I was initially unable to reproduce this, until I pulled up code that
> [~mikemccand] recently committed. It seems possible that encoding/decoding
> changes are triggering it. Of specific concern is the new way
> maximum/minimum decoded values are computed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
