[
https://issues.apache.org/jira/browse/LUCENE-4644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13543261#comment-13543261
]
David Smiley commented on LUCENE-4644:
--------------------------------------
bq. Is "some within" the CROSSES operation? "some but not all interior points
in common"
It's not. By the way I prefer [ESRI's
docs|http://edndoc.esri.com/arcsde/9.1/general_topics/understand_spatial_relations.htm#Cross]
which have bigger explainations with pictures.
bq. It sounds like your bigger question is how to treat multi-valued fields in
general.
Yes, that's the crux of it. However the spatial index (the prefix tree)
doesn't know the difference between your two examples; it'll wind up being the
same set of indexed terms. I'd put it to a user like this:
"If a document can have multiple shapes, whether by adding multiple (disjoint)
shapes or by passing a shape that is comprised of multiple disjoint parts (e.g.
MULTI*), then enable this option to treat each disjoint part separately as a
candidate to match the WITHIN predicate. If enabled and at least one part is
WITHIN, then the document matches. This is much faster than the default
setting which insists that the entirety of the spatial region covered by the
indexed shape(s) must be WITHIN the query shape."
> Implement spatial WITHIN query for RecursivePrefixTree
> ------------------------------------------------------
>
> Key: LUCENE-4644
> URL: https://issues.apache.org/jira/browse/LUCENE-4644
> Project: Lucene - Core
> Issue Type: New Feature
> Components: modules/spatial
> Reporter: David Smiley
> Assignee: David Smiley
>
--
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: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
