[
https://issues.apache.org/jira/browse/LUCENE-4208?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Smiley updated LUCENE-4208:
---------------------------------
Attachment:
LUCENE-4208_makeQuery_return_ConstantScoreQuery_and_remake_TwoDoublesStrategy.patch
This patch is the start of something I hope to finish tonight. makeValueSource
is makeDistanceValueSource to make abundantly clear. TwoDoubles is getting
overhauled to support the dateline and any query shape--should probably go into
another issue.
> Spatial distance relevancy should use score of 1/distance
> ---------------------------------------------------------
>
> Key: LUCENE-4208
> URL: https://issues.apache.org/jira/browse/LUCENE-4208
> Project: Lucene - Core
> Issue Type: New Feature
> Components: modules/spatial
> Reporter: David Smiley
> Fix For: 4.0
>
> Attachments:
> LUCENE-4208_makeQuery_return_ConstantScoreQuery_and_remake_TwoDoublesStrategy.patch
>
>
> The SpatialStrategy.makeQuery() at the moment uses the distance as the score
> (although some strategies -- TwoDoubles if I recall might not do anything
> which would be a bug). The distance is a poor value to use as the score
> because the score should be related to relevancy, and the distance itself is
> inversely related to that. A score of 1/distance would be nice. Another
> alternative is earthCircumference/2 - distance, although I like 1/distance
> better. Maybe use a different constant than 1.
> Credit: this is Chris Male's idea.
--
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]
