<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body>
Hi Jukka,<br>
I'm still very new to ElasticSearch (so take with plenty of salt!),
but if you want to keep the geom in _source and calculate on the
fly, I guess you could maybe try it with one of the scripting
languages:
<a class="moz-txt-link-freetext" href="https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-scripting.html">https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-scripting.html</a>
- Python's on there so then you'd have access to all of the py-geo
stuff.<br>
<br>
Of course, assuming it worked, the trade-off would be reduced
storage for (considerably?) increase processing usage and
complexity.<br>
<br>
The other option would be to store the native geometry as a "binary"
datatype -
<a class="moz-txt-link-freetext" href="https://www.elastic.co/guide/en/elasticsearch/reference/current/binary.html">https://www.elastic.co/guide/en/elasticsearch/reference/current/binary.html</a><br>
<br>
Cheers,<br>
Jonathan<br>
<br>
<br>
<div class="moz-cite-prefix">On 23/11/2016 15:41, Rahkonen Jukka
(MML) wrote:<br>
</div>
<blockquote
cite="mid:2c7004c5716e4cb9b02ce654a4a8dcea@C119S212VM022.msvyvi.vaha.local"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.Shkpostityyli17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 2.0cm 70.85pt 2.0cm;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal">Hi,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-US">What if somebody would
like to use ElasticSearch for queries but still somehow get
the native geometries included in the output? The geometry
must be re-projected into EPSG:4326 for creating either
geo_point or geo_shape, but can anybody suggest a clever way
for saving the native geometry? It is of course possible to
save it into a text field for example as WKT of JSON but
could it be possible to keep the original geometry in
“_source” and just create the geo_point or geo_shape
on-the-fly or the index?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">-Jukka Rahkonen-<o:p></o:p></span></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
gdal-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:gdal-dev@lists.osgeo.org">gdal-dev@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="http://lists.osgeo.org/mailman/listinfo/gdal-dev">http://lists.osgeo.org/mailman/listinfo/gdal-dev</a></pre>
</blockquote>
<br>
</body>
</html>