You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "David Smiley (JIRA)" <ji...@apache.org> on 2016/02/01 06:15:39 UTC
[jira] [Commented] (LUCENE-6996) Deconflict GeoPointField and BKD
LatLonField Encoding, Decoding, and Tolerance
[ https://issues.apache.org/jira/browse/LUCENE-6996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15125766#comment-15125766 ]
David Smiley commented on LUCENE-6996:
--------------------------------------
Nick, if you would, please categorize your spatial issues as-such ("Component" in JIRA). It helps to find these issues within JIRA. I didn't bring this up until now because only recently did we decide to put these sandbox pieces into spatial-named modules. BTW I think you can do this in-bulk for the open ones.
> Deconflict GeoPointField and BKD LatLonField Encoding, Decoding, and Tolerance
> ------------------------------------------------------------------------------
>
> Key: LUCENE-6996
> URL: https://issues.apache.org/jira/browse/LUCENE-6996
> Project: Lucene - Core
> Issue Type: Improvement
> Reporter: Nicholas Knize
>
> Follow up to LUCENE-6956, BKD based {{LatLonField}} and postings based {{GeoPointField}} should use a consistent lat/lon encoding/decoding method to ensure consistent round-off error.
--
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