[gdal-dev] Store also native geometry into Elastic Search?

[Jukka Rahkonen]

Hi,

What if somebody would like to put and deliver some official spatial data
(cadastral data) which are not in EPSG:4326 with Elastic Search? Could it be
possible to translate the geometries into EPSG:4326 and store and index them
as geo_shape, but also keep the native geometries and save them into another
field? Perhaps json does not like to have many geometry fields but how about
saving the native geometry as WKT? Indexing WKT field feels stupid but maybe
ES could be mapped to skip it. Reasoning is that conversion from native to
EPSG:4326 and back to native is not necessary accurate and coordinates may
change a bit.

Am I even right that the conversion into EPSG:4326 is necessary for using
the geo_shape query?

-Jukka Rahkonen-