[
https://issues.apache.org/jira/browse/LUCENE-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15226590#comment-15226590
]
Nicholas Knize commented on LUCENE-7165:
----------------------------------------
bq. the subtraction in encode yes (and addition in decode). I don't understand
why we need those?
It creates the unsigned space for the morton curve mapping everything to full
unsigned 32 bits. Using LatLonPoint means we just push the hairy code to
handling the signed bit so -90, -180 still maps to {{0x0L}} and 90, 180 maps to
{{0xFFFFFFF....L}}
bq. Maybe we should just reuse the latlonpoint encoding but then interleave
those bits?
Still have to handle the sign bit
> Return GeoPointField Encoding to use full 64 bit space
> -------------------------------------------------------
>
> Key: LUCENE-7165
> URL: https://issues.apache.org/jira/browse/LUCENE-7165
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Nicholas Knize
> Attachments: LUCENE-6996.patch
>
>
> This was originally done in LUCENE-6710 but then reverted due to issues with
> GeoHash encoding (which has since been removed). This issue will revert the
> GeoPoint encoding back to full 64 bit space which will synchronize
> quantization TOLERANCE between {{LatLonPoint}} and {{GeoPointField}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
