[
https://issues.apache.org/jira/browse/LUCENE-7186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15243351#comment-15243351
]
David Smiley commented on LUCENE-7186:
--------------------------------------
bq. Stepping back ... why are we adding this API to Lucene's core APIs now? If
I understand correctly, it's only GeoPointField (with its 31 bit encoding that
we want to move up to 32 bits, using the same encoding as LatLonPoint) that
needs to use it, now? Can this instead remain in the spatial module, and only
later, once we have a 1D points based morton encoded geo field, can we then
think about making these available in core?
+1!
> Add numerically stable morton encoding to GeoEncodingUtils
> ----------------------------------------------------------
>
> Key: LUCENE-7186
> URL: https://issues.apache.org/jira/browse/LUCENE-7186
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Nicholas Knize
> Attachments: LUCENE-7186.patch, LUCENE-7186.patch, LUCENE-7186.patch,
> LUCENE-7186.patch
>
>
> This is the follow on to LUCENE-7184. It adds a numerically stable morton
> encoding method to {{o.a.l.geo.GeoEncodingUtils}} that can be reused by
> {{GeoPointField}} and a new {{GeoPointField}} based on {{Point}} encoding.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
