[
https://issues.apache.org/jira/browse/LUCENE-6647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14646732#comment-14646732
]
Nicholas Knize edited comment on LUCENE-6647 at 7/29/15 8:44 PM:
-----------------------------------------------------------------
Latest patch for LUCENE-6704 changes mortonEncoding to use full 32bit precision
for lat/lon values. This fixes the issue where the max lat/lon was not decoding
to the correct precision leading to the failure posted above. A patch will be
posted here that is compatible with the changes from LUCENE-6704.
was (Author: nknize):
Latest patch for LUCENE-6704 changes mortonEncoding to use full 32bit precision
for lat/lon values. This fixes an issue where the max lat/lon was not decoding
to the correct precision. A patch will be posted here that is compatible with
these changes.
> Add GeoHash String Utilities to core GeoUtils
> ---------------------------------------------
>
> Key: LUCENE-6647
> URL: https://issues.apache.org/jira/browse/LUCENE-6647
> Project: Lucene - Core
> Issue Type: New Feature
> Reporter: Nicholas Knize
> Attachments: LUCENE-6647.patch, LUCENE-6647.patch
>
>
> GeoPointField uses morton encoding to efficiently pack lat/lon values into a
> single long. GeoHashing effectively does the same thing but uses base 32
> encoding to represent this long value as a "human readable" string. Many
> user applications already use the string representation of the hash. This
> issue simply adds the base32 string representation of the already computed
> morton code.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
