Yoann Rodière (
https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%...
) *commented* on HSEARCH-3275 (
https://hibernate.atlassian.net/browse/HSEARCH-3275?atlOrigin=eyJpIjoiMjN...
)
Re: Search 6 groundwork - Move to a stable implementation of Lucene spatial support (
https://hibernate.atlassian.net/browse/HSEARCH-3275?atlOrigin=eyJpIjoiMjN...
)
The context has changed and made most of this ticket obsolete.
First, LatLonPoint and related classes in Lucene are now in the core, not in the sandbox (
https://issues.apache.org/jira/browse/LUCENE-7314 ). They are thus supported to the same
extent as other core features.
Second, the precision of LatLonPoint seems largely sufficient for most use cases. From the
javadoc of org.apache.lucene.document.LatLonPoint :
Values are indexed with some loss of precision from the
original double values (4.190951585769653E-8 for the latitude component
and 8.381903171539307E-8 for longitude).
In the worst case, for latitude, this gives a precision near the equator of
40,075.017/360*8.381903171539307*10^-8 = 9.33 cm, or around 3.7 inches. I'd say this
is enough to find the location of a pizza joint or a rental bike, or for most use cases
we're likely to encounter.
So, let's just add some documentation about the precision, that should be enough.
(
https://hibernate.atlassian.net/browse/HSEARCH-3275#add-comment?atlOrigin...
) Add Comment (
https://hibernate.atlassian.net/browse/HSEARCH-3275#add-comment?atlOrigin...
)
Get Jira notifications on your phone! Download the Jira Cloud app for Android (
https://play.google.com/store/apps/details?id=com.atlassian.android.jira....
) or iOS (
https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em...
) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100126- sha1:dd08494 )