[ 
https://issues.apache.org/jira/browse/LUCENE-4167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13402531#comment-13402531
 ] 

David Smiley commented on LUCENE-4167:
--------------------------------------

bq. I don't see the need to differentiate BBoxIntersects and Intersects. If the 
user wants to find those Documents related to the bounding box of a Shape, then 
they can call shape.getBoundingBox() and pass that into the Strategy. The 
Strategys shouldn't have to worry about the Shape (although TwoDoubles does but 
that needs to be re-thought separately). The Strategys should just take the 
Shape given and roll with it. Is that what you're suggesting?

The stategy shouldn't care about the bbox concept, I agree. I think the bbox 
capability should be decoupled from SpatialOperation.  It's not a simple matter 
of the client calling queryShape.getBoundingBox() since the expression of the 
query shape from client to server is a string.  So instead of 
"BBoxIntersects(Circle(3,5 d=10))" I propose supporting 
"INTERSECTS(BBOX(Circle(3,5 d=10)))".  The actual set of operations I want to 
support are [E]CQL spatial predicates: 
http://docs.geoserver.org/latest/en/user/filter/ecql_reference.html#spatial-predicate
 but that perhaps deserves its own issue.
                
> Remove the use of SpatialOperation
> ----------------------------------
>
>                 Key: LUCENE-4167
>                 URL: https://issues.apache.org/jira/browse/LUCENE-4167
>             Project: Lucene - Java
>          Issue Type: Bug
>          Components: modules/spatial
>            Reporter: Chris Male
>
> Looking at the code in TwoDoublesStrategy I noticed 
> SpatialOperations.BBoxWithin vs isWithin which confused me.  Looking over the 
> other Strategys I see that really only isWithin and Intersects is supported.  
> Only TwoDoublesStrategy supports IsDisjointTo.  The remainder of 
> SpatialOperations are not supported.
> I don't think we should use SpatialOperation as this stage since it is not 
> clear what Operations are supported by what Strategys, many Operations are 
> not supported, and the code for handling the Operations is usually the same.  
> We can spin off the code for TwoDoublesStrategy's IsDisjointTo support into a 
> different Strategy.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to