Currently geo_ponit doc values use quantisation when storing doc values. As a result, reconstructing documents in synthetic source using doc values results in accuracy loss and in the reconstructed document not matching the original source. We can fix the accuracy issue by using the WKB format and consider giving users a storage versus accuracy tradeoff by taking advantage of the store option.
The idea is to make store: true the default and using WKB for the stored field. When store is true we can reconstruct the document in synthetic source by using the stored field without accuracy loss. When store: false is used we can use the. quantized representation in doc values by trading accuracy for storage reduction.
Description
Currently
geo_ponit
doc values use quantisation when storing doc values. As a result, reconstructing documents in synthetic source using doc values results in accuracy loss and in the reconstructed document not matching the original source. We can fix the accuracy issue by using theWKB
format and consider giving users a storage versus accuracy tradeoff by taking advantage of thestore
option.The idea is to make
store: true
the default and usingWKB
for the stored field. Whenstore
istrue
we can reconstruct the document in synthetic source by using the stored field without accuracy loss. Whenstore: false
is used we can use the. quantized representation in doc values by trading accuracy for storage reduction.