You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Michael McCandless (JIRA)" <ji...@apache.org> on 2015/08/01 11:09:04 UTC
[jira] [Updated] (LUCENE-6710) GeoPointField should use full 64 bit
encoding
[ https://issues.apache.org/jira/browse/LUCENE-6710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael McCandless updated LUCENE-6710:
---------------------------------------
Attachment: LUCENE-6710.patch
As much as I love BigInteger, it's quite slow and I think that may matter here (it's called 2.8 M times when I run TestGeoPointQuery.testWholeMap).
How about this patch instead? I just special case the max shift case ...
> GeoPointField should use full 64 bit encoding
> ---------------------------------------------
>
> Key: LUCENE-6710
> URL: https://issues.apache.org/jira/browse/LUCENE-6710
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Nicholas Knize
> Attachments: LUCENE-6710.patch, LUCENE-6710.patch
>
>
> Current GeoPointField uses 31 bits for each lat and long, respectively. This causes a precision error for the maximum bounds for 2D mapping applications (e.g., instead of maximum of 180, 90 the max value handled is 179.999999, 89.999999).
> This issue improves precision for the full 2D map boundaries by using the full 32 bit range for lat/lon values, resulting in a morton hash using the full 64 bit range.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org