nknize commented on PR #12162: URL: https://github.com/apache/lucene/pull/12162#issuecomment-1487302810
> what about storing the data with the same rounding that we enforce for the KD index and doc values Yes. Exactly what I'm saying w/ my comment `"...This way we could decide to store LatLonPoint as an efficient integer encoded XY long value"` > ideally I'd like it to not fiddle with formatting, which feels like it may be a can of worms? I agree it could be a can of worms but there are ISO standards (geojson, wkt, wkb, geoparquet) the geo industry uses for interoperability and I don't think supporting these standards is a "can of worms"? We can start w/ comma delimited (wait, `x,y` or `y,x` 🤦🏻♂️ lol) > add a Field.Store ctor option like KeywordField that stores the point the same way as doc values when enabled, and add a helper method org.apache.lucene.geo.Point decodeStoredValue(long storedValue) or something similar? +1 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org For additional commands, e-mail: issues-h...@lucene.apache.org
