# Elasticsearch and new KD trees

**URL:** <https://discuss.elastic.co/t/elasticsearch-and-new-kd-trees/65289>\
**Category:** Elasticsearch\
**Created:** [November 8, 2016, 12:42am UTC](https://discuss.elastic.co/t/elasticsearch-and-new-kd-trees/65289 "2016-11-08T00:42:13Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![EuclideanSearch](https://avatars.discourse-cdn.com/v4/letter/e/c77e96/32.png) [@EuclideanSearch](https://discuss.elastic.co/u/EuclideanSearch)\
**Post date:** [November 8, 2016, 12:42am UTC](https://discuss.elastic.co/t/elasticsearch-and-new-kd-trees/65289/1 "2016-11-08T00:42:13Z")

</div>

Hi,

Per this article [https://www.elastic.co/blog/lucene-points-6.0](https://www.elastic.co/blog/lucene-points-6.0) I noticed 'Note that the dimensions need not all be spatial! One exciting potential use case is mixing geo-spatial dimensions with other dimensional values, such as median household income, into a single 3D dimensional index.' . So will it be possible in the future to tell ES to create a K-D tree from 2-3 fields? That would allow us to effectively create an index on multiple columns (in RDBMS). Does anyone know if that will be supported at all?

Cheers,  
EuclideanSearch

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 6, 2016, 12:42am UTC](https://discuss.elastic.co/t/elasticsearch-and-new-kd-trees/65289/2 "2016-12-06T00:42:41Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.