On Mon, Apr 1, 2019 at 5:32 AM David Smiley <david.w.smi...@gmail.com> wrote: > > Yup. And if you have the original lat/lon then you can forgo the > complexity of reverse-engineering it from postings.
It has been a long day. I did manage to reverse engineer it by reversing the stuff in geoCodedToPrefixCodedBytes - to discover that even the highest precision value indexed in postings wasn't precise enough to be acceptable. Then I discovered that doc values had more precision, but that didn't give me the same value I got with a LatLonPoint either. (By this point I had dug into a newer index to get out the exact values the new version of Lucene was putting in, and had my unit test asserting that the result was exactly the same.) So in the end I have ended up digging it back out of a stored field and parsing that. Which was actually harder to parse than the postings, mind you, but contained the full value, so that's fine. The only disappointing thing is that it's a little slower than using doc values or postings would have been. :( TX --------------------------------------------------------------------- To unsubscribe, e-mail: java-user-unsubscr...@lucene.apache.org For additional commands, e-mail: java-user-h...@lucene.apache.org
